Hello all,
I think I've found the "regression" in Belkin/Liebert USB HID support
which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was
actually caused by a bug fix: practically the only functional difference
per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from
Hi,
FYI: I'll be away from computers (and possibly internet) for a couple of
weeks.
As for the logs, they are not "the same": the first one (with NUT 2.8.x)
failed to connect to the device it liked -- "failed to claim USB device:
Resource busy" (probably another program holds it, maybe a
Thanks again.
So one more bit (other than indeed different libusb versions) that could
potentially come into play is bitness - armv7l builds are 32-bit, right?
One idea from here is to have you run the driver programs directly with
high debug verbosity, e.g. `usbhid-ups -DD -s Liebert`
Thanks.
Can you please also check (e.g. with ldd `which usbhid-ups`) which
`libusb` variant (1.0 or 0.1) was the 2.7.4 version of the driver running
with?
I wonder if the two generations of that library got something
differently?..
The commit I mentioned -
Hello,
For clarity: what changed with the move from NUT v2.7.4 to 2.8.0 - the
warnings "became reported", or the highlighted values became zeroes (and
were valid non-zero numbers with older NUT - so a regression)?
It seems the message is specific to the subdriver and comes from commit
Hello everyone
I'm using: Raspberry Pi 4 Model B Rev 1.5 8 GB "Debian GNU/Linux 12
(bookworm)"
It all started when I updated from version 2.7.4 to version 2.8.0 and the
consequences were the following:
pi@raspberrypi:~ $ sudo upsdrvctl start
Network UPS Tools - UPS driver controller 2.8.0
