-
@dennypage said in NUT Package (2.8.1 and above):
Just FYI, HA may miss the power outage completely if it is shorter than the polling interval.
That's true yes. I set up a delay of some seconds because I only need a notification if it's a real / longer power outage, otherwise my UPS will just kick in and since it has the capacity to provide power for almost an hour, it's okay to get the norification a bit delayed.
-
@endy66 Cool. Just wanted to make sure you were aware.
-
This post is deleted! -
I dunno what happened. I just updated to 2.8.2_1 and now my tripplite USB connection isn't working.
[nutdev1]
driver = "tripplite_usb"
port = "auto"
vendorid = "09AE"
productid = "0001"
product = "TRIPP LITE SMART500RT1U"
vendor = "Tripp Lite"
bus = "000"
device = "002"
busport = "005"
###NOTMATCHED-YET###bcdDevice = "000A" -
@incith I just did the package upgrade and although the service appeared to be working, it wasn't.
I went to Services -> UPS and UPS Status brought up errors, but then I went to the "UPS Settings" tab and everything looked fine so just pressed Save at the bottom and service is running fine. Maybe try pressing the Save button from the settings page and see if this works for you?
-
NUT Package (2.8.1 and above)
and now its
NUT Package (2.8.1 and above - and back again)
as I received a message from my pfSense :
Notifications in this message: 1 ================================ 13:01:10 The following updates are available and can be installed using System > Package Manager: nut: 2.8.2_1 ==> 2.8.2 (downgrade)So the update is a downgrade ?
Or is 2.8.2 a more recent as 2.8.2_1 because the name (numbering) changed ?
-
Hello all,
it seems i have new/old issues with nut 2.8.2_1 on 2.7.2-RELEASE (amd64)
I need to reload service to get it up again. Its on serial connection.
Can i do something about this?Feb 9 22:20:41 upsmon 80900 UPS RielloSEP2200: on bypass (powered, not protecting) Feb 9 22:20:41 upsmon 80900 Communications with UPS RielloSEP2200 established Feb 9 22:20:38 upsd 73072 Connected to UPS [RielloSEP2200]: riello_ser-RielloSEP2200 Feb 9 22:20:37 riello_ser 66770 Startup successful Feb 9 22:20:36 upsmon 80900 Poll UPS [RielloSEP2200] failed - Driver not connected Feb 9 22:20:31 upsmon 80900 Poll UPS [RielloSEP2200] failed - Driver not connected Feb 9 22:20:26 upsmon 80900 UPS RielloSEP2200 is unavailable Feb 9 22:20:26 upsmon 80900 Poll UPS [RielloSEP2200] failed - Driver not connected Feb 9 22:20:21 upsmon 80900 Communications with UPS RielloSEP2200 lost Feb 9 22:20:21 upsmon 80900 Poll UPS [RielloSEP2200] failed - Driver not connected Feb 9 22:20:21 upsd 73072 User local-monitor@127.0.0.1 logged into UPS [RielloSEP2200] Feb 9 22:20:21 upsmon 80419 Startup successful Feb 9 22:20:20 upsd 73072 Startup successful Feb 9 22:20:20 upsd 72610 Found 1 UPS defined in ups.conf Feb 9 22:20:20 upsd 72610 Can't connect to UPS [RielloSEP2200] (riello_ser-RielloSEP2200): Connection refused Feb 9 22:20:20 upsd 72610 listening on ::1 port 3493 Feb 9 22:20:20 upsd 72610 listening on 127.0.0.1 port 3493 Feb 9 22:20:20 upsmon 58399 Signal 15: exiting Feb 9 22:20:20 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:20:15 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:20:09 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:20:07 php-fpm 95968 /pfblockerng/pfblockerng_update.php: Successful login for user 'admin' from: 192.168.1.210 (Local Database) Feb 9 22:20:04 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:59 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:54 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:49 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:44 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:39 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:34 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:29 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:24 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:19 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:14 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:09 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:19:04 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:59 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:54 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:49 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:44 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:39 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:34 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:29 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:24 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:19 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:14 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:09 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:18:04 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:59 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:54 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:49 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:44 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:39 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:34 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:29 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:24 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:19 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:14 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:09 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:17:04 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:59 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:54 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:49 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:44 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:39 upsmon 58399 UPS RielloSEP2200 is unavailable Feb 9 22:16:39 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:34 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:29 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:23 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:18 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:13 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:08 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:16:03 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:58 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:53 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:48 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:43 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:38 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:33 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:28 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:23 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:18 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:13 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:08 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused Feb 9 22:15:03 upsmon 58399 UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused -
Not sure if this is a reasonable forum to post this in, but maybe somebody has a helpful idea.
I have NUT 2.8.2.1 installed on pfSense+ (Netgate 8200).
I have three Synology units in my network. Two DS120j and one DS1522. Both of the DS120j can see the NUT server and configure it. The DS1522 just reports "No UPS is connected." Settings are identical in all Synology. I have tried disabling the firewall in the DS1522 (although the DS120j are happy with firewall enabled).
Any suggestions on what to look for?
-
Hey all,
Sorry, but I am out of the loop with whatever change just happened. I tried to get the update locked in before my trip, but it didn’t happen. I won’t be able to work on an update until the week of the 19th.
In the interim, if you have an outstanding issue I suggest looking earlier in this thread for executables that I posted several weeks ago.
Again, sorry for the upheaval.
Denny
-
@dennypage when I try to service nut onestart..
I tried chmod everything to 0777
Network UPS Tools - UPS driver controller 2.8.1.1
Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.35 (2.8.1.1)
Warning: This is an experimental driver.
Some features may not function correctly.libusb1: Could not open any HID devices: insufficient permissions on everything
No matching USB/HID UPS found
upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it
Driver failed to start (exit status=1)
/usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut -
Quick note: Based on a notice I just received from my own firewall, it might be worthwhile to thy
pkg upgradefrom the command line and then re-save the config.
-
@hspindel said in NUT Package (2.8.1 and above):
Not sure if this is a reasonable forum to post this in, but maybe somebody has a helpful idea.
I have NUT 2.8.2.1 installed on pfSense+ (Netgate 8200).
I have three Synology units in my network. Two DS120j and one DS1522. Both of the DS120j can see the NUT server and configure it. The DS1522 just reports "No UPS is connected." Settings are identical in all Synology. I have tried disabling the firewall in the DS1522 (although the DS120j are happy with firewall enabled).
Any suggestions on what to look for?
I have some additional clues:
upsc NUTIP returns Connection Refused on DS1522, returns correct status on other Synologies.
telnet NUTIP 3493 returns Connection Refused on DS1522, connects to NUT server from any other computer on the network.
It appears to me that this is not an issue with pfSense (on which the NUT server is running) since it works for every device except the DS1522. I tried adding a special firewall rule to pfSense, but it made no difference. My guess is something is wrong with the DS1522's request.
-
curl -O https://pkg01-atx.netgate.com/pfSense_v2_7_1_amd64-pfSense_v2_7_1/All/pfSense-pkg-nut-2.8.2.pkg curl -O https://pkg01-atx.netgate.com/pfSense_v2_7_1_amd64-pfSense_v2_7_1/All/nut-devel-2023.10.07_1.pkg pkg install -f ./nut-devel-2023.10.07_1.pkg pkg install -f ./pfSense-pkg-nut-2.8.2.pkgYou may just need nut-devel...I did both. UPS is back online.
-
@incith said in NUT Package (2.8.1 and above):
curl -O https://pkg01-atx.netgate.com/pfSense_v2_7_1_amd64-pfSense_v2_7_1/All/pfSense-pkg-nut-2.8.2.pkg curl -O https://pkg01-atx.netgate.com/pfSense_v2_7_1_amd64-pfSense_v2_7_1/All/nut-devel-2023.10.07_1.pkg pkg install -f ./nut-devel-2023.10.07_1.pkg pkg install -f ./pfSense-pkg-nut-2.8.2.pkgYou may just need nut-devel...I did both. UPS is back online.
Update/Edit: noticing that nut is not listed in my Package manager after this. May need to just do a pkg remove pfSense-pkg-nut nut-devel in a few weeks once a fix is posted. Not sure honestly.
-
@incith, @LanterIT, @ha11oga11o
If you are still having a problem with the current package, can you post your configs please?
Also, can you please confirm that you performed the
pkg upgradestep mentioned above?
-
@incith said in NUT Package (2.8.1 and above):
libusb1: Could not open any HID devices: insufficient permissions on everything
No matching USB/HID UPS foundThis indicates that the USB device could not be opened.
Did you say if you are running as root?
Also, have you checked to see if there is a quirk registered for your UPS? -
@dennypage I have the same symptoms with the tripplite_usb driver.
I have a quirk registered and "user=root" in the config file.it worked without issue with version 2.8.2 and stopped working with 2.8.2_1 (as previously reported by others)
I've tried unplugging the UPS' USB cable and plugging it back in. I've tried manually loading the driver as the root user, the netgate (in my case the 4100) recognizes that the UPS is connected and on ugen0.2
I haven't attempted a downgrade yet to get it working again, I've just stopped the NUT daemon for now but I would like for this to be working again.
-
@apremselaar said in NUT Package (2.8.1 and above):
I have the same symptoms with the tripplite_usb driver.
I have a quirk registered and "user=root" in the config file.Thank you for letting me know. I do appreciate it.
Can you please let me know what UPS model you have?
Also, can you let me know the output from "usbconfig -v" please? Thanks
-
@dennypage Sure. I have a Tripp Lite Smart500RT1U
here's the output of usbconfig -v:
ugen0.1: <Intel XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.1.0: uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0300 bDeviceClass = 0x0009 <HUB> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0003 bMaxPacketSize0 = 0x0009 idVendor = 0x0000 idProduct = 0x0000 bcdDevice = 0x0100 iManufacturer = 0x0001 <Intel> iProduct = 0x0002 <XHCI root HUB> iSerialNumber = 0x0000 <no string> bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x001f bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 <no string> bmAttributes = 0x0040 bMaxPower = 0x0000 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0009 <HUB> bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0000 <no string> Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 <IN> bmAttributes = 0x0003 <INTERRUPT> wMaxPacketSize = 0x0002 bInterval = 0x00ff bRefresh = 0x0000 bSynchAddress = 0x0000 Additional Descriptor bLength = 0x06 bDescriptorType = 0x30 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x06, 0x30, 0x00, 0x00, 0x00, 0x00 ugen0.2: <Tripp Lite TRIPP LITE SMART500RT1U> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (0mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x0000 <Probed by interface class> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x09ae idProduct = 0x0001 bcdDevice = 0x000a iManufacturer = 0x0001 <Tripp Lite > iProduct = 0x0002 <TRIPP LITE SMART500RT1U > iSerialNumber = 0x0000 <no string> bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0022 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 <no string> bmAttributes = 0x00c0 bMaxPower = 0x0000 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 <HID device> bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0000 <no string> Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x10 RAW dump: 0x00 | 0x09, 0x21, 0x10, 0x01, 0x00, 0x01, 0x22, 0x34, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 <IN> bmAttributes = 0x0003 <INTERRUPT> wMaxPacketSize = 0x0008 bInterval = 0x000a bRefresh = 0x0000 bSynchAddress = 0x0000Thanks.
-
@apremselaar said in NUT Package (2.8.1 and above):
ugen0.1: <Intel XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
ugen0.1.0: uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1>bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0300
bDeviceClass = 0x0009 <HUB>
bDeviceSubClass = 0x0000
bDeviceProtocol = 0x0003
bMaxPacketSize0 = 0x0009
idVendor = 0x0000
idProduct = 0x0000
bcdDevice = 0x0100
iManufacturer = 0x0001 <Intel>
iProduct = 0x0002 <XHCI root HUB>
iSerialNumber = 0x0000 <no string>
bNumConfigurations = 0x0001That's just the main USB on board concentrator (see this as a USB switch).
Typically, you would see the connected devices, like mouse, keyboard, and in my case : an UPS :
[23.09.1-RELEASE][root@pfSense.bhf.tld]/root: usbconfig -v ugen0.1: <Intel XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.1.0: uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0300 bDeviceClass = 0x0009 <HUB> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0003 bMaxPacketSize0 = 0x0009 idVendor = 0x0000 idProduct = 0x0000 bcdDevice = 0x0100 iManufacturer = 0x0001 <Intel> iProduct = 0x0002 <XHCI root HUB> iSerialNumber = 0x0000 <no string> bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x001f bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 <no string> bmAttributes = 0x0040 bMaxPower = 0x0000 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0009 <HUB> bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0000 <no string> Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 <IN> bmAttributes = 0x0003 <INTERRUPT> wMaxPacketSize = 0x0002 bInterval = 0x00ff bRefresh = 0x0000 bSynchAddress = 0x0000 Additional Descriptor bLength = 0x06 bDescriptorType = 0x30 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x06, 0x30, 0x00, 0x00, 0x00, 0x00 ugen0.2: <American Power Conversion Back-UPS XS 700U FW:924.Z5 .I USB FW:Z5> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (24mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x0000 <Probed by interface class> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x051d idProduct = 0x0002 bcdDevice = 0x0106 iManufacturer = 0x0003 <American Power Conversion> iProduct = 0x0001 <Back-UPS XS 700U FW:924.Z5 .I USB FW:Z5 > iSerialNumber = 0x0002 <3B1926X61525 > bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0022 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 <no string> bmAttributes = 0x00e0 bMaxPower = 0x000c Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 <HID device> bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0000 <no string> Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x10 RAW dump: 0x00 | 0x09, 0x21, 0x10, 0x01, 0x21, 0x01, 0x22, 0x05, 0x08 | 0x04 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 <IN> bmAttributes = 0x0003 <INTERRUPT> wMaxPacketSize = 0x0006 bInterval = 0x000a bRefresh = 0x0000 bSynchAddress = 0x0000I tend to say : on a low level, USB didn't notice that there was a device (your UPS) connected.
NUT wouldn't see t neither then ...
