What's wrong with my NUT (Network UPS Tools)? No longer connects. Log included

Lakee911 · June 22, 2024, 5:42pm

Hello, I’ve been having trouble with NUT on Home Assistant. Can anyone help troubleshoot? Log is below.

This worked fine for quite a while and then one day I noticed data not coming in. It’s been offline now for months. Latest versions of everything didn’t help (at the time).

I assume the error is this “Can’t claim USB device [0764:0601]@0/0: Entity not found.”

Log:

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
[13:33:37] INFO: Setting mode to netserver...
[13:33:37] INFO: Connected USB devices:
Bus 002 Device 003: ID 0bda:0415 Realtek Semiconductor Corp. 2-Port USB 3.0 Hub
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0bda:5415 Realtek Semiconductor Corp. 2-Port USB 2.0 Hub
Bus 001 Device 016: ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS
Bus 001 Device 017: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 001 Device 021: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 004: ID 10c4:8a2a Silicon Labs HubZ Smart Home Controller
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[13:33:37] INFO: Generating /etc/nut/upsd.users...
[13:33:37] INFO: Configuring user: upsmon
[13:33:38] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[13:33:39] INFO: Configuring Device named networkups...
[13:33:39] INFO: Configuring Device named ps5ups...
[13:33:39] INFO: Starting the UPS drivers...
Using subdriver: CyberPower HID 0.6
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
Network UPS Tools - UPS driver controller 2.8.0
Can't claim USB device [0764:0601]@0/0: Entity not found
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
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.4  (amd64 / generic-x86-64)
 Home Assistant Core: 2024.4.3
 Home Assistant Supervisor: 2024.06.0
-----------------------------------------------------------
 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
[13:33:47] 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
[13:33:48] INFO: Setting mode to netserver...
[13:33:48] INFO: Connected USB devices:
Bus 002 Device 003: ID 0bda:0415 Realtek Semiconductor Corp. 2-Port USB 3.0 Hub
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0bda:5415 Realtek Semiconductor Corp. 2-Port USB 2.0 Hub
Bus 001 Device 016: ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS
Bus 001 Device 017: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 001 Device 021: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 004: ID 10c4:8a2a Silicon Labs HubZ Smart Home Controller
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[13:33:49] INFO: Generating /etc/nut/upsd.users...
[13:33:49] INFO: Configuring user: upsmon
[13:33:49] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[13:33:50] INFO: Configuring Device named networkups...
[13:33:51] INFO: Configuring Device named ps5ups...
[13:33:51] INFO: Starting the UPS drivers...
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
Using subdriver: CyberPower HID 0.6
Can't claim USB device [0764:0601]@0/0: Entity not found
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 - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
Network UPS Tools - UPS driver controller 2.8.0

Config:

- name: networkups
  driver: usbhid-ups
  port: auto
  config: []
  pollinterval: 15
  pollonly: enabled
- name: ps5ups
  driver: usbhid-ups
  port: auto
  config: []
  pollinterval: 15
  pollonly: enabled

What other information is needed here?

Thank you!

Sir_Goodenough · June 22, 2024, 8:00pm

Check with the add-on author, and that message seems to have good clues.

tom_l · June 22, 2024, 11:11pm

What sort of HA installation are you running (OS or supervised),what hardware, virtualised?

Did you update HA OS recently?

Have you tried this?

Stop the nut addon
Unplug the USB cable to the UPS
Wait a few seconds
Connect the USB cable to the UPS
Start the NUT addon.

Can you connect the UPS to a laptop running NUT or the UPS proprietary software?

If not, try shutting the UPS down, and restarting it. If it still does not connect to the laptop then it could be an issue with your UPS. This is the least likely scenario.

Another unlikely scenario but worth checking, replace the USB cable.

Lakee911 · June 23, 2024, 1:10pm

Thanks, Tom. I’m running HAOS. I have updated it since it stopped working, but that didn’t fix it. I’ve tried those five steps, many times. I didn’t try out the proprietary software, though. I have two units, which I’ve tried separately. Can’t believe both would be bad.

I found some good info based on the warning that Sir_G pointed out, but also a lot of folks with unresolved similar issues.

Lakee911 · June 23, 2024, 7:46pm

For some unknown (but surely dumb) reason, a lot of folks have luck resolving this with a shutdown of the host and then powering it up again. I want to try that when I’m able to. I’ll shut everything down, including the UPS units, and do all of my updates, too. Hopefully, I won’t be back.

Thanks for the help.

wmaker · June 23, 2024, 11:58pm

Googling around some … seems the driver can’t talk to the physical UPS. One user reported that he resolved this by rebooting his UPS.

finix77 · September 21, 2024, 9:38am

Similar problem here:
libusb1: Could not open any HID devices: insufficient permissions on everything
No matching HID UPS found
Network UPS Tools - UPS driver controller 2.8.0
Driver failed to start (exit status=1)

Home Assistant OS 13.1
Supervisor 2024.09.1

I use the following configuration for APC smart UPS 1500i usb connected:

name: apcsmart
driver: usbhid-ups
port: auto
config:
- vendorid = 051d*
- productid = 0002*
- serial = AS0614322014

Last year this configuration was working. I don’t know exactly when it stopped to work

Rip · October 11, 2024, 1:18pm

Has anyone got the nut addon working?

I got the same issues, everything seems fine, but the addon or integration is not updating the data. Everything is stale

It was able to retrieve data the first time, after the addon it restarted, or rebooted

The integration seems fine but the data continues to be stale

Perhaps it’s time to uninstall

Running it on a raspberry pi 5

Tried adding pollonly and pollinterval neither helped

JAGS_77 · November 15, 2024, 10:40am

I Run Homeassistant OS in a VM in Proxmox and have the same issue. Before I had no problem with Hassio in a mi IPC dedicated but since I moved to Proxmox I cant start the addon
I get this Error: Can’t claim USB device [0463:ffff]@0/0: Other error. Driver failed to start (exit status=1)

askarr · December 8, 2024, 9:35am

In my case, NUT on Home Assistant is running on a Blue ODroid, and has become incredibly unstable in the past year. Very similar issues to this thread.

What I observe:

The NUT addon doesn’t detect any problems, it just quietly stops reporting information - so your only warning is that the sensors go stale
At some point the USB device drops off the reported list
Restarting the addon will then yield an actual driver error
Some hardware change will then restore working state, whether that’s a full restart, plugging & unplugging the USB connection, etc.

Reading this Github issue NUT#1983 and NUT#2447 suggests part of the problem is the NUT driver itself. 2.7.4 crashed and could be restarted, 2.8.0 seems to require literally a hardware reset (plugging & unplugging or a full restart).

The other end of the problem is often poorly designed USB chips in the UPSes that don’t necessarily play nice.

My own theory is that either the addon (plausibly the drivers loaded in it) or something in the Supervisor broke over the past couple of years, because when I first had this set up maybe four years ago, it was rock solid. More recently I discovered the UPS was regularly failing to connect. Of course I can’t totally rule out slowly degrading hardware in that four year period.

There is an interesting option linked from those Github issues, since restarting or plugging/unplugging hardware is a kludgy workaround for broken drivers. This USB resetter seems to have worked for people. Unfortunately, I have absolutely no idea how to wed this bit of Python script with HA, because undoubtedly it requires some appropriate permissions to the host.

ausfas · January 5, 2025, 12:37am

Not sure if you guys have the same issue

github.com/home-assistant/core

NUT integration is not picking up accurate and timley data from APC UPS

opened 07:27AM - 11 Sep 24 UTC

ausfas

integration: nut

### The problem The integration data is delayed and doesn't update after a ce…rtain point. In this situation, the charge level is stuck at 99% while I unplugged the USB and attached the PC with Power Chute personal edition and got it as 100%. Then reconnecting is back to RPi it shows 100%.Turn off the input to UPS so it dropped to 95-96% and after a while it again stuck at 99% showing charging as not 100% despite it being 100% (confirmed from Power Chute) but the integration doesn't pick it up. Also any changes are displayed with a delay of 1-2 mins. Not sure why it reports up to 99% fine and not after that. Yesterday it got stuck at 95% then did the same process of connecting to Power Chute and back. The Add-on always have log entries of can't write to PID fopen issues so not sure if that is the root cause or not as others have the same PID fopen error but have not reported this data stale issue. ### What version of Home Assistant Core has the issue? core-2024.9.1 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Network UPS Tools (NUT) ### Link to integration documentation on our website https://www.home-assistant.io/integrations/nut ### Diagnostics information [config_entry-nut-01J7B47B5DFGPVR5C9BG9X03BZ.json](https://github.com/user-attachments/files/16959462/config_entry-nut-01J7B47B5DFGPVR5C9BG9X03BZ.json) ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt Logs from the UPS NUT Add-on Using subdriver: APC HID 0.98 Network UPS Tools - UPS driver controller 2.8.0 cont-init: info: /etc/cont-init.d/nut.sh exited 0 cont-init: info: running /etc/cont-init.d/nutclient.sh cont-init: info: /etc/cont-init.d/nutclient.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun upsd (no readiness notification) services-up: info: copying legacy longrun upsmon (no readiness notification) s6-rc: info: service legacy-services successfully started [17:05:25] INFO: Starting the UPS information server... 0.000000 fopen /run/nut/upsd.pid: No such file or directory 0.000023 Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running! 0.000239 [D1] debug level is '1' 0.000321 listening on 0.0.0.0 port 3493 0.000490 Connected to UPS [APC]: usbhid-ups-APC 0.001020 Running as foreground process, not saving a PID file [17:05:26] INFO: Starting the UPS monitor and shutdown controller... 0.000000 fopen /run/nut/upsmon.pid: No such file or directory 0.000023 Could not find PID file to see if previous upsmon instance is already running! 0.000253 Using power down flag file /etc/killpower 0.000387 UPS: APC@localhost (primary) (power value 1) 0.000401 [D1] debug level is '1' 0.000427 [D1] debug level is '1' 0.000432 Warning: running as one big root process by request (upsmon -p) 0.000489 [D1] Saving PID 451 into /run/nut/upsmon.pid Init SSL without certificate database 0.002375 [D1] Trying to connect to UPS [APC@localhost] 0.509793 User [email protected] logged into UPS [APC] 0.003079 [D1] Logged into UPS APC@localhost ``` ### Additional information ![image](https://github.com/user-attachments/assets/9818cf79-be00-4496-bd1f-3d79e8f78710) ![image](https://github.com/user-attachments/assets/50f7fa7a-096e-4898-af79-41a0f1c30933)

No resolution yet

haybolat · January 26, 2025, 6:52am

Hello, I have HA installed on Raspberry Pi 5. I installed the NUT plugin, I start it, when I enter NUT from the plugins again, I see that it stops. Why? I see that many users have problems with these issues, but support is weak, I was using OpenHab before.

[09:39:22] INFO: Setting mode to netserver...
[09:39:22] INFO: Generating /etc/nut/upsd.users...
[09:39:22] INFO: Configuring user: nutuser
[09:39:23] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[09:39:23] INFO: Configuring Device named Emerson...
[09:39:23] 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
Network UPS Tools - UPS driver controller 2.8.0
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
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

Configurasyon

users:
  - username: nutuser
    password: Nutuser321
    instcmds:
      - all
    actions: []
devices:
  - name: Emerson
    driver: usbhid-ups
    port: auto
    config: []
mode: netserver
shutdown_host: true
list_usb_devices: false

dbarnes · February 5, 2025, 9:21pm

No expert here, just trying to get mine fixed as well. One issue I had with one of my UPS (1 of5) was it reporting ‘Stale Data’. Really old thread suggested adding MAXAGE to your upsd.conf file. Worked for me.

... 
MAXAGE 20
LISTEN 0.0.0.0 3493

Hman · February 11, 2025, 10:09am

Not working for me either (HAOS on RPi, but I found the following:

After a complete system restart, and the NUT addon disabled, the USB port appears in the list of devices (/dev) as /dev/hidraw0 and /dev/usb/hiddev0.
If the NUT addon is started, these ports immediately disappear. This is also reported in the supervisor log:

2025-02-10 21:03:01.269 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on Package nut/aarch64 · GitHub with version 0.14.0
2025-02-10 21:03:06.494 INFO (MainThread) [supervisor.hardware.monitor] Detecting remove hardware /dev/usb/hiddev0 - None
2025-02-10 21:03:06.495 INFO (MainThread) [supervisor.hardware.monitor] Detecting remove hardware /dev/hidraw0 - None

So is this an addon, HAOS or Supervisor issue? My knowledge is too limited to tell, but I would think the above is a clue.

wmaker · February 11, 2025, 5:16pm

I don’t know the answer, but I have a couple of Ubuntu systems running NUT (no problem) with APC UPSs using USB, and I see the kernel drivers for these systems coming up and registering the APCs for hidrawX and hidevX but when I go looking, there are not any /dev/hidrawX nor /dev/usb/hiddevX files.

I’m kinda guessing that what is happening is that the /dev/XX files are present until the NUT Server comes up and registers with the OS to use usbhid, at which point the OS may be determining that the /dev/X files are not needed and removes them. In short, what you are seeing maybe normal behavior, but like I said earlier, I don’t see these /dev/XX files in my system either with NUT running.