Persistent usbhid-ups[7209]: nut_libusb_get_report: Input/Output Error

[grainsoflight]

NUT persistently output 'usbhid-ups[7209]: nut_libusb_get_report: Input/Output Error' though it appears to be running fine.

nut-debug-20250318181700.zip

[jimklimov]

Looking at logs, you seem to be running NUT v2.8.0 variant. Can you please try recent versions, or master-branch builds? Maybe @desertwitch can help about that, as it seems you're running UNRAID...

[grainsoflight]

I get more errors on 2.8.2

Mar 19 00:44:56 cloud usbhid-ups[6819]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Mar 19 00:44:56 cloud usbhid-ups[6819]: nut_libusb_get_string: Input/Output Error

[grainsoflight]

Using on latest (nut-2.8.2-x86_64-7master.ssl31) gives the same errors

[jimklimov]

And did you set pollonly in config as it recommends? Does it have any good/bad effect?

[grainsoflight]

What syntax would I use to add that to the ups.conf

[jimklimov]

Reading man pages and other docs generally helps :)
https://networkupstools.org/docs/man/usbhid-ups.html

In the section for the device config, add pollonly as a standalone line (it is a flag, so presence means enabled).

[grainsoflight]

Then no, it doesnt work

[grainsoflight]

Nevermind, it was not saving the flag because a setting needed to be changed, now it appears to be working

[grainsoflight]

Spoke too soon Mar 19 19:03:29 cloud usbhid-ups[270750]: nut_libusb_get_report: Input/Output Error

[jimklimov]

Can you also add debug_min=6 for a while, to collect details about how it initializes the device driver and at what point it complains? (Later disable the logging, so it would not thrash your storage)

I wonder if this is related to fixes in master after 2.8.2, like #2604 (so the error is not so much of communications as of interpreting the data as usable).

[grainsoflight]

Of course now that debugging is is on I dont get the error