upsc gives 'Error: Driver not connected' but usbhid-ups shows the device fine

[crmason2]

I'm trying to connect to my APC UPS connected to my windows device using the latest release of NUT-for-Windows 2.8.4.433.

nut-scan shows the following

[nutdev-usb1]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "051D"
        productid = "0002"
        product = "Back-UPS NS1080G FW:914.L1   .D USB FW:L1"
        serial = "3B1315X24094"
        vendor = "American Power Conversion"
        # bus = "002"
        # device = "001"

which I've added to ups.conf as

[apc_ns1080_win]
driver = "usbhid-ups"
port = "auto"
vendorid = "051D"
productid = "0002"
product = "Back-UPS NS1080G FW:914.L1   .D USB FW:L1"
serial = "3B1315X24094"
vendor = "American Power Conversion"
# bus = "002"
# device = "001"
# busport = "002"

running usbhid-ups seems to give good details (i can provide full dump if needed)

$ ./usbhid-ups -DDDDDD -d2 -a apc_ns1080_win
...SNIP...
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.date: 2001/09/25
battery.mfr.date: 2013/04/14
battery.runtime: 1460
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.3
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Back-UPS NS1080G
device.serial: 3B1315X24094
device.type: ups
driver.debug: 6
driver.flag.allow_killpower: 0
driver.name: usbhid-ups
driver.parameter.interrupt_pipe_no_events_tolerance: -1
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 15
driver.parameter.port: auto
driver.parameter.product: Back-UPS NS1080G FW:914.L1   .D USB FW:L1
driver.parameter.productid: 0002
driver.parameter.serial: 3B1315X24094
driver.parameter.synchronous: auto
driver.parameter.vendor: American Power Conversion
driver.parameter.vendorid: 051D
driver.state: dumping
driver.version: 2.8.4
driver.version.data: APC HID 0.100
driver.version.internal: 0.67
driver.version.usb: libusb-1.0.27 (API: 0x0100010A)
input.sensitivity: medium
input.transfer.high: 142
input.transfer.low: 88
input.transfer.reason: input voltage out of range
input.voltage: 121.0
input.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 914.L1   .D
ups.firmware.aux: L1
ups.load: 32
ups.mfr: American Power Conversion
ups.mfr.date: 2013/04/14
ups.model: Back-UPS NS1080G
ups.productid: 0002
ups.realpower.nominal: 650
ups.serial: 3B1315X24094
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d

however upsc give a driver error

$ ./upsc apc_ns1080_win@127.0.0.1:3493
Error: Driver not connected

At this point I'm not sure what to do since the info is there in usbhid-ups

[crmason2]

Looks like I might have found the issue. The service was trying to execute \bin\upsdrvctl.exe start when the actual path is \sbin\upsdrvctl.exe I copied over the file to bin however the event log still gives the error give the error.

The description for Event ID 1 from source Network UPS Tools cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Can't create process C:\NUT\mingw64\bin\..\bin\upsdrvctl.exe start : 5

The message resource is present but the message was not found in the message table

However the file is present

PS C:\NUT\mingw64\bin> C:\NUT\mingw64\bin\..\bin\upsdrvctl.exe start
Network UPS Tools upsdrvctl.exe - UPS driver controller 2.8.4 release
Network UPS Tools 2.8.4 release - Generic HID driver 0.67
USB communication driver (libusb 1.0) 0.50
Using subdriver: APC HID 0.100
Listening on named pipe \\.\pipe\usbhid-ups-apc_ns1080_win

And after manual execution of upsdrvctl start upsc now works.

$ ./upsc apc_ns1080_win@127.0.0.1:3493
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.date: 2001/09/25
battery.mfr.date: 2013/04/14
battery.runtime: 1756
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.3
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Back-UPS NS1080G
device.serial: 3B1315X24094
device.type: ups
driver.debug: 0
driver.flag.allow_killpower: 0
driver.name: usbhid-ups
driver.parameter.interrupt_pipe_no_events_tolerance: -1
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 15
driver.parameter.port: auto
driver.parameter.product: Back-UPS NS1080G FW:914.L1   .D USB FW:L1
driver.parameter.productid: 0002
driver.parameter.serial: 3B1315X24094
driver.parameter.synchronous: auto
driver.parameter.vendor: American Power Conversion
driver.parameter.vendorid: 051D
driver.state: quiet
driver.version: 2.8.4
driver.version.data: APC HID 0.100
driver.version.internal: 0.67
driver.version.usb: libusb-1.0.27 (API: 0x0100010A)
input.sensitivity: medium
input.transfer.high: 142
input.transfer.low: 88
input.transfer.reason: input voltage out of range
input.voltage: 121.0
input.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 914.L1   .D
ups.firmware.aux: L1
ups.load: 24
ups.mfr: American Power Conversion
ups.mfr.date: 2013/04/14
ups.model: Back-UPS NS1080G
ups.productid: 0002
ups.realpower.nominal: 650
ups.serial: 3B1315X24094
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d

[crmason2]

Ok so I was able to fix it so the service seems to run fine now. When I copied the file I think it was in an admin powershell and it ended up adding permissions to deny the SYSTEM account execution so the service running as SYSTEM couldn't execute it.

[jimklimov]

Thanks for the report! FWIW, any old release is "set in stone" once cut with all its bugs remaining in place, and current development may have better behaving code (as well as new bugs :D).

This one was probably fixed as part of #3207 and/or #3305 (and maybe other tickets, there were a few related to this subject).

[crmason2]

#3207 probably fixed it from the looks of it didn't show up in my initial issue search cause I didn't know it was upsdrvctl.exe at the time :)

BTW do you know if it's possible to run PoweChute and NUT side by side or does the libusb drivers prevent that? Was mainly looking to use NUT for power metering for Home Assistant for the time being until I moving my gaming rig over to Linux.

[jimklimov]

Not really sure, I last used PowerChute 25 years ago or so, in the days of serial ports which were exclusive to one program or another. I largely became a NUT user because the JVM used to run PowerChute used like half of the small server memory we had :) No idea how it is made nowadays.

As an educated guess, USB access would also be exclusive to any one program (e.g. we do have to tell the OS to not attach the "HID Battery" driver).

Is there something significant in PowerChute that you need and miss in NUT? Note that "Network" UPS Tools in the name means you can arrange shut-downs of many systems powered by the same UPS and monitored by one that has the cable to it. It should work with a NUT for Windows server too (settings and firewalls permitting).

[crmason2]

No NUT would provide all the functionality I need for the Windows box and more. PowerChute was just already set up. I use NUT in my home lab to orchestrate shutdown of non critical VMs in Proxmox and routers etc with perl scripts already. Just less familiar with windows cli and I want to put my box to sleep instead of shutdown since it'll go hours that way on the battery and I just need time to get the generator running. Guess it's research time. I also need to see if some of my Back UPS Network 40s might actually be able to connect to NUT since they have a USB-B control ports.