Replies: 7 comments 6 replies
-
|
Same issue here with an APC Smart-UPS 750 - Running via docker with latest tag (AMD64) Setup detects the UPS correctly: Detected UPS Devices: Running the test configuration at the end of the wizard returns the error message: Configuration test failed: Output of lsusb: |__usb3 1d6b:0002:0510 09 2.00 480MBit/s 0mA 1IF (Linux 5.10.55+ xhci-hcd xHCI Host Controller 0000:00:14.0) hub |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here with Eaton 5E900UI... Anyone got any tips of how to work with that? |
Beta Was this translation helpful? Give feedback.
-
|
Pls try with latest beta @ #126 post nr. 4 dartsteven/nutify-internal-testing:0.2.0.Int.Testing.v.13-amd64 Not just recommended — mandatory (and yeah, I’m half joking… half). Run this instance in a clean environment |
Beta Was this translation helpful? Give feedback.
-
|
Try this : nano docker-compose.yaml and paste it : sudo docker compose up and show the log or in ./Nutify/logs:/app/nutify/logs |
Beta Was this translation helpful? Give feedback.
-
|
The “Can’t claim USB device” message means it can’t take ownership of that USB device. Are you sure you have access/permissions to it? Also, is it possible you already have another instance or process running that’s using the same USB port/device? |
Beta Was this translation helpful? Give feedback.
-
|
and pls can un do an : ps aux | egrep 'upsd|upsmon|nut-driver|usbhid|apcupsd' |
Beta Was this translation helpful? Give feedback.
-
|
Synology already has NUT under the hood for its UPS feature (it runs the USB driver like usbhid-ups and upsd). If Synology is the one handling the UPS over USB, a container trying to run its own NUT driver will often fail because the USB device is already claimed. So I think the cleanest setup is: let Synology own the UPS USB connection, and run Nutify as a network client (connect to upsd over the LAN, port 3493). That avoids any USB fighting and is usually the most stable on a NAS. If the Synology UPS service is disabled and he still gets the same error after a reboot, then either Synology (or something else) is still grabbing the UPS in the background, or the USB passthrough is flaky and the device keeps re-enumerating. In any case, netclient is the safest path unless he really wants Nutify to be the only NUT instance and fully disable everything else on the NAS.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello. I deployed Nutify in Docker and can't connect to UPS Ippon Back Black 850 euros. However, Synology sees the UPS.
Contents of docker compose file:
lsusb command output:
The hardware you are looking for is:
Nutify returns the following error:
Configuration test failed:
Failed to start NUT drivers: Can't claim USB device [0665:5161]@0/0/0: Entity not found
Driver failed to start (exit status=1)
Contents of the ups.conf file:
I changed the driver from driver = "nutdrv_qx" to driver = "blazer_usb", and vice versa. Didn't help. The error is the same.
Contents of the nut.conf file:
I would also like to note that Nutify generally sees the UPS, but cannot connect to it.

I will be grateful for any help.
Beta Was this translation helpful? Give feedback.
All reactions