Hello, thanks for the details although I too am not sure about the "invalid
parameter" - got neither reasons nor solutions at the moment.
Regarding the "device: unknown", there was an issue in the USB matcher code
that did not let the driver "remember" the value it saw from libusb (and so
it
I think I have another lead:
For the Powervar, lsusb gives:
Bus 003 Device 002: ID 4234:0002 AMETEK-POWERVAR Corporation UPM UPS (v01.51,
Nov 3 2018)
When running usbhid-ups from the command line, I get:
0.035977 [D2] - Bus: 003
0.035989 [D2] - Device: unknown
So is it passing "unknown" as
Hello,
Thanks for your reply.
Both of the services you mentioned (nut-driver@PowervarUPS01.service and
nut-driver@APCUPS01.service) were running. They were spamming syslog with
messages like the following:
2024-02-07T14:29:27.704506-05:00 hostname nut-driver@PowervarUPS01[72162]:
Network UPS
Hello and welcome!
My guess would be that a nut-driver service unit (or instances thereof
since NUT v2.8.0, monolithic before) have started and captured the devices,
so your attempts with another copy of the driver started from CLI fail at
that. Normally drivers detect an older sibling running
I am working in Ubuntu Linux on a Raspberry Pi 5. Nut is unable to connect to
USB UPSs.
uname -srvmpio
Linux 6.5.0-1009-raspi #12-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 17 11:45:08 UTC
2024 aarch64 aarch64 aarch64 GNU/Linux
Current Installed version of nut is 2.8.0-7 installed with apt
apt-cache
