[Nut-upsuser] tripplite_usb driver failing with libusb_get_interrupt() returned 0 and ###NOTMATCHED-YET### bcdDevice = "000A"

[Jeff Hood]

Hi everyone,

I'm running Network UPS Tools (NUT) version *2.8.1* on a Debian system
(aarch64), trying to connect an older Tripp Lite UPS via the tripplite_usb
driver.

While nut-scanner -U successfully identifies the hardware, it flags the
device's firmware revision with a ###NOTMATCHED-YET### notice:
[nutdev1]

	driver = "tripplite_usb"
	port = "auto"
	vendorid = "09AE"
	productid = "0001"
	product = "TRIPP LITE UPS"
	vendor = "Tripp Lite"
	bus = "001"
	device = "003"
	busport = "003"
	###NOTMATCHED-YET###bcdDevice = "000A"

When the driver service attempts to start, it successfully claims the USB
endpoint but falls into an endless retry loop during the command handshake:
libusb_get_interrupt() returned 0 instead of 8 while sending 3a 55 aa 0d 00
00 00 00 '.U......'

It appears the device's specific bcdDevice firmware revision might be
falling outside the driver's current whitelist or handling the command
payload differently. Has anyone run into this zero-length return behavior
or a NOTMATCHED-YET bcdDevice variant on Tripp Lite hardware?

Thanks in advance for any guidance!

Best regards,

--Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20260921/a2356183/attachment.htm>