search for: monitoringtalk

...tiating UPS shutdown instcmd: command [shutdown.stop] failed instcmd: command [shutdown.stop] failed instcmd: command [shutdown.stop] failed Shutdown failed! This problem has already been addressed and supposedly corrected in latest builds, as seen in here: http://t38832.monitoring-nut-development.monitoringtalk.info/problems-with-blazer-usb-driver-will-not-shut-down-myups-t38832.html So, how can I solve this? Is there a way to tell BLAZER_USB to only send the command "SHUTDOWN.RETURN"? How can I get or build the latest version of BLAZER_USB for the windows port? Thank you so much!! -----------...

...l be running. I don't know how the Windows port of NUT handles exclusive access to USB devices, but it is possible that this is causing the failure. > This problem has already been addressed and supposedly corrected in latest builds, as seen in here: http://t38832.monitoring-nut-development.monitoringtalk.info/problems-with-blazer-usb-driver-will-not-shut-down-myups-t38832.html > > So, how can I solve this? Is there a way to tell BLAZER_USB to only send the command "SHUTDOWN.RETURN"? Rather than calling the driver with "-k", you can leave upsd and the driver running, and...