Closed Railnolds closed 1 year ago
gouthamravee
commented
1 year ago Same problem here, I believe it was working before 2023.6 supervisor update but no hard proof unfortunately.
I know in other cases I could fix this by doing a chmod on the usb devices /dev/bus/usb/... path but even with the ssh terminal tool that's not possible with HASS OS as the underlying OS is read only it seems.
Railnolds
commented
1 year ago doing a chmod on the usb devices /dev/bus/usb/... path Could you explain how to do it? Which is full path should be?
gouthamravee
commented
1 year ago It depends on your USB setup, before starting the NUTS addon in HA, go into the config and enable the "list usb devices" option. Then check the logs for an output of your USB devices. It should look something like this
[10:11:18] INFO: Connected USB devices:
Bus 009 Device 005: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 009 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 009 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 009 Device 006: ID 05ac:8281 Apple, Inc. Bluetooth Host Controller
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[10:11:18] INFO: Generating /etc/nut/upsd.users...The number after bus and device is what you need, it should translate to /dev/bus/usb/009/005 for the first cyber power systems device. You can verify this with the SSH addon, you should be able to find something up to the /dev/bus/usb/009 path and then the devices within should be the end of the path. So in my case using the command ls /dev/bus/usb/009/ I see the devices 005, 004, 003, 006, and 001.
gouthamravee
commented
1 year ago As of HA version 2023.7.0 the NUTS addon is working again. I also rebooted the VM HASS is running on, even though I tried that earlier with no luck.
Here's my NUTS config for HA in case
- config:
- serial = "4B1737P03171"
- desc = "Network UPS 1"
- vendorid = 051d*
driver: usbhid-ups
name: networkUPS1
port: auto
pollinterval: 1
- config:
- serial = "4B1810P09778"
- desc = "Network UPS 2"
- vendorid = 051d*
driver: usbhid-ups
name: networkUPS2
port: auto
pollinterval: 1
- config:
- serial = "CTHGY2005146"
- desc = "Server UPS"
- vendorid = 0764*
driver: usbhid-ups
name: serverUPS
port: auto
pollinterval: 1
war4peace
commented
1 year ago First time NUT user here, I am experiencing the same issue. Log below:
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.12.0
You are running the latest version of this add-on.
System: Home Assistant OS 10.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.8.0
Home Assistant Supervisor: 2023.07.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
[17:46:52] INFO: Configuring timezone (Europe/Bucharest)...
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
[17:46:53] INFO: Setting mode to netserver...
[17:46:54] INFO: Connected USB devices:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[17:46:54] INFO: Generating /etc/nut/upsd.users...
[17:46:54] INFO: Configuring user: war
[17:46:55] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[17:46:56] INFO: Configuring Device named NJoy1500...
[17:46:56] INFO: Starting the UPS drivers...
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
libusb1: Could not open any HID devices: insufficient permissions on everything
No matching HID UPS found
Driver failed to start (exit status=1)
Network UPS Tools - UPS driver controller 2.8.0
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 base-addon-timezone successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service fix-attrs 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
mattague
commented
1 year ago I am also having trouble with getting the addon to run. It was working ealrier today, but I noticed that one of the two ups weren't being recognized by the integration, so I went to the addon config to adjust it, and after saving, the addon started crashing. I reverted to the old config hoping I could just get the addon running again but to no avail.
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.12.0
You are running the latest version of this add-on.
System: Home Assistant OS 10.4 (amd64 / qemux86-64)
Home Assistant Core: 2023.8.1
Home Assistant Supervisor: 2023.08.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
[19:56:07] INFO: Configuring timezone (America/New_York)...
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
[19:56:08] INFO: Setting mode to netserver...
[19:56:08] INFO: Connected USB devices:
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 111: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 002 Device 110: ID 09ae:2012 Tripp Lite Tripp Lite UPS
Bus 002 Device 002: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[19:56:08] INFO: Generating /etc/nut/upsd.users...
[19:56:08] INFO: Configuring user: mattague
[19:56:09] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[19:56:09] INFO: Configuring Device named small-ups...
[19:56:09] INFO: Configuring Device named rack-ups...
[19:56:10] INFO: Starting the UPS drivers...
Using subdriver: APC HID 0.98
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
Can't claim USB device [09ae:2012]@0/0: No such device (it may have been disconnected)
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
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
Network UPS Tools - UPS driver controller 2.8.0
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 stoppedJust FYI, I abandoned this idea and connected the UPS to my Unraid server, works perfectly.
github-actions[bot]
commented
1 year ago There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
Hi.
I used NUT addon some time. And one day I found that it is not working. I tried to reinstall it and now I get the error in log:
How can this problem fixed?