addon-nut: NUT fails to start: Can't claim USB device: Other error / Driver failed to start

`s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

-----------------------------------------------------------
 Add-on: Network UPS Tools
 Manage battery backup (UPS) devices
-----------------------------------------------------------
 Add-on version: 0.13.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.5  (amd64 / qemux86-64)
 Home Assistant Core: 2024.2.2
 Home Assistant Supervisor: 2024.01.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[20:40:00] INFO: Configuring timezone (Europe/Minsk)...
Log level is set to DEBUG
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/nut.sh
[20:40:09] INFO: Setting mode to netserver...
[20:40:10] INFO: Connected USB devices:
Bus 001 Device 005: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
**Bus 004 Device 003: ID 0d9f:0004 Powercom Co., Ltd HID UPS Battery**
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 1a86:55d4 QinHeng Electronics SONOFF Zigbee 3.0 USB Dongle Plus V2
Bus 002 Device 002: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[20:40:11] INFO: Generating /etc/nut/upsd.users...
[20:40:15] INFO: Configuring user: user1
[20:40:17] DEBUG: Password SHA1: F52D18BBAEC8E3C77D30C99E20ED0417A6E424D1
[20:40:17] DEBUG: Requested API resource: https://api.pwnedpasswords.com/range/F52D1
[20:40:17] DEBUG: API HTTP Response code: 200
[20:40:17] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[20:40:20] INFO: Configuring Device named powercom...
[20:40:21] INFO: Starting the UPS drivers...
   0.000000	[D1] Starting UPS: powercom
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication **driver (libusb 1.0) 0.43**
Can't claim USB device [0d9f:0004]@0/0: Other error
Network UPS Tools - UPS driver controller 2.8.0
   **0.092585	Driver failed to start (exit status=1)**
cont-init: info: /etc/cont-init.d/nut.sh exited 1
cont-init: info: running /etc/cont-init.d/nutclient.sh
cont-init: info: /etc/cont-init.d/nutclient.sh exited 0
cont-init: warning: some scripts exited nonzero
s6-rc: warning: unable to start service legacy-cont-init: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-timezone: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-timezone successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped`

POWERCOM Raptor RPT-1000AP: UPS is compactible: 2024-02-19_10-41-38

About this issue

  • Original URL
  • State: closed
  • Created 4 months ago
  • Comments: 21

Most upvoted comments

@wqrwefdgfv you closed this issue, but it is still present in the addon. You find a nice workaround but the problem has not been fixed.

As you wish)

@wqrwefdgfv you closed this issue, but it is still present in the addon. You find a nice workaround but the problem has not been fixed.

woah, it worked also with my Synology! Nice and easy, as it should. Thanks again @wqrwefdgfv you made my day!