search for: busport

...;051D" productid = "0003" product = "Smart-UPS X 2200 FW:UPS 07.4 / ID=01003" serial = "AS2039254737" vendor = "American Power Conversion" # bus = "000" # device = "005" # busport = "004" I've added the details to /etc/nut/ups.conf But get the following error: # upsdrvctl start Network UPS Tools - UPS driver controller 2.8.2 Network UPS Tools - Generic HID driver 0.53 (2.8.2) USB communication driver (libusb 1.0) 0.47 libusb1: Could not open any HID devices:...

...= "0003" > product = "Smart-UPS X 2200 FW:UPS 07.4 / ID=01003" > serial = "AS2039254737" > vendor = "American Power Conversion" > # bus = "000" > # device = "005" > # busport = "004" > > I've added the details to /etc/nut/ups.conf > > But get the following error: > > # upsdrvctl start > Network UPS Tools - UPS driver controller 2.8.2 > Network UPS Tools - Generic HID driver 0.53 (2.8.2) > USB communication driver (libusb 1.0) 0.4...

...hose, you've locked out the daemons from some access. 2) Access to USB device filesystem nodes should be governed with udev on that platform, check if you have a file like /usr/lib/udev/rules.d/62-nut-usbups.rules and if it lists USB IDs of your device 051d:0002 3) Driver options bus, device, busport can depend on topology and enumeration of connected devices; it may be wise to comment them away. Later NUT versions already do not default to offering them in `nut-scanner` output, to minimize run-time surprises. 4) See if you already have a service instance `nut-driver at apcupskelder.service` d...

...s from > some access. > > 2) Access to USB device filesystem nodes should be governed with udev on > that platform, check if you have a file like > /usr/lib/udev/rules.d/62-nut-usbups.rules and if it lists USB IDs of your > device 051d:0002 > > 3) Driver options bus, device, busport can depend on topology and > enumeration of connected devices; it may be wise to comment them away. > Later NUT versions already do not default to offering them in `nut-scanner` > output, to minimize run-time surprises. > > 4) See if you already have a service instance > `nut-driv...

...tc/nut/ups.conf [Configuration of /etc/nut/ups.conf becomes:] [nutdev-usb1] driver = "usbhid-ups" port = "auto" vendorid = "0764" productid = "0501" product = "SL Series" vendor = "CPS" # bus = "001" # device = "049" # busport = "003" [Configuration of /etc/nut/nut.conf:] #MODE=netserver #2024-02-18 - too ambitious to start MODE=standalone #2024-02-18 ALLOW_NODEVICE=true #2024-02-18 export ALLOW_NO_DEVICE #2024-02-18 ALLOW_NOT_ALL_LISTENERS=true #2024-02-18 export ALLOW_NOT_ALL_LISTENERS #2024-02-18 [All seeme...

...t of *-devel packages. This was solved in NUT recently (maybe after 2.8.2 release already) by detecting and stashing the basename of realpath of the library present during build, so the exact *.so.X.Y.Z would be also tried. Also, nut-scanner now (in 2.8.2 IIRC) should not suggest the volatile bus/busport/device numbers by default. Jim On Sun, Nov 10, 2024 at 7:42?PM Bill Gee <bgee at campercaver.net> wrote: > Thanks for the tip, Jim. I just figured out what is going on. The > system is now working. ==> This one is on me. <== > > The root cause was the specification o...

...endorid = "051D" productid = "0002" product = "Back-UPS BX750MI FW:295202G -302202G" serial = "9B2416A22014" vendor = "American Power Conversion" bus = "001" device = "004" busport = "002" ###NOTMATCHED-YET###bcdDevice = "0106" ``` ``` erik at MinipcLG2:/etc/nut$ sudo usbhid-ups -a apcupskelder sudo: usbhid-ups: opdracht niet gevonden ``` This seems strange? But after some googling, I found the below alternative - although I would expect it to wor...

Thanks for the tip, Jim. I just figured out what is going on. The system is now working. ==> This one is on me. <== The root cause was the specification of the bus number in the ups.conf file. Here is what it looks like now: ============ [cyberpower] driver = "usbhid-ups" port = "auto" vendorid = "0764" productid =