On Wed, Sep 23, 2026 at 10:44 AM Jim Klimov wrote: > Just in case, did you try with other USB-capable drivers to check if their > protocols are supported by the device (primarily usbhid-ups)?
The Tripp-Lite models with USB productID 0001 will not work with usbhid-ups: they use a proprietary protocol over USB HID, but not HID PDC. On Sep 21, 2026, at 11:01 PM, Jeff Hood wrote: > > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 55 aa 0d 00 > 00 00 00 '.U......' However, this command (55 -> 'U'; get unit ID) should be optional. (At first reading, I was thinking it was the initial command to get the protocol ID, which also has a lot of zeroes.) per https://github.com/networkupstools/nut/blob/3154ca01cd6f1a67f0b15350ce436eee14da29a3/drivers/tripplite_usb.c#L356-L360 Also, send_cmd() should try 10x, not forever. I'd have to see a debug log to better understand what is going on there. This might be the place to start for that? https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity#nut-v2-8-1-and-newer - Charles _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
