Open chesteraser opened 2 years ago
Did not personally run NUT drivers from containers with such pass-through, so maybe there are further setup nuances to that? Does lsusb
find the device in container? Does no other program (e.g. udev or NUT in host OS) grab the device in a way that NUT in container can not overtake it?
If you can start the driver with bumped logging (e.g. -DDDDDD
argument on command line, or debug_min 6
ups.conf option since NUT 2.8.0), it might tell more about the issue - libusb device walk etc.
Hello, have you had any time to check if newer NUT (2.8.0 release or custom-build of yet newer master iterations) recognized the device?
Greetings, my UPS is this cat - https://www.cyberpowersystems.com/product/ups/pfc-sinewave/cp1350pfclcd/ - it is connected via USB to my Qnap NAS and is detected and monitored in the OS integration. It appears to not be listed on the NUT compatibility list, and so I was trying to get it running in a container. I tested it with the usbhid-ups driver:
Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 No matching HID UPS found Driver failed to start (exit status=1)
Container is configured to share the USB device /dev/bus/usb/003/005 to the same path in the container, also tried sharing /dev in privileged mode.
Any thoughts on troubleshooting or adding this model?