After update to 0.16.0, server is repeatedly disconnecting

[Betacart]

As stated above, after I updated to 0.16.0, I am getting this in log:

105518.803322	Data for UPS [ups] is stale - check driver
105521.665240	Poll UPS [ups@localhost] failed - Data stale
{"message":"Event nut.ups_event fired."}Network UPS Tools upsmon 2.8.1
105526.665969	Poll UPS [ups@localhost] failed - Data stale
105531.666280	Poll UPS [ups@localhost] failed - Data stale
105536.666579	Poll UPS [ups@localhost] failed - Data stale
105541.666867	Poll UPS [ups@localhost] failed - Data stale
105546.667169	Poll UPS [ups@localhost] failed - Data stale
105551.667469	Poll UPS [ups@localhost] failed - Data stale
105556.667768	Poll UPS [ups@localhost] failed - Data stale
105561.668091	Poll UPS [ups@localhost] failed - Data stale

and so on...

Until now, it worked well for more than 1 year.
My UPS is Eaton 5E 850i

Here I am sharing my configuration:

Add-on version: 0.16.0
You are running the latest version of this add-on.
System: Home Assistant OS 16.2 (aarch64 / odroid-n2)
Home Assistant Core: 2025.9.4
Home Assistant Supervisor: 2025.09.0

To fix this issue for a one day, I need to restart addon. Then, connection works around that day. After that, I have same problem again (and same solution for fix).

If need anything more, let me know.

Thank you

[Pseudophryne]

Ditto exact same issue with update 0.16.0 my configuration.

Add-on version: 0.16.0
Installation method: Home Assistant OS
Core: 2025.9.4
Supervisor: 2025.09.0
Operating System: 16.2
Frontend: 20250903.5

[fnordpojk]

Exact same issue here as well after upgrading to 0.16.0, except mine runs for maybe 8-12 hours before declaring "data is stale". Running the same versions as the above posters with an Eaton 5E on a Home Assistant Green. Previously this has worked fine for multiple years.

It appears to be some kind of loss of contact with the USB device, because upon restart of the addon, I get this in the log:

[00:36:07] INFO: Starting the UPS drivers...
Network UPS Tools - Generic HID driver 0.52 (2.8.1)
USB communication driver (libusb 1.0) 0.46
libusb1: Could not open any HID devices: insufficient permissions on everything
No matching HID UPS found

When it then restarts by itself, everything starts working fine, for another 12 hours or so..

[github-actions]

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!

[Betacart]

Still not fixed, problem persist. Please, fix it.

[iamjoshk]

still an issue

[Robbe-B]

Same as reported here : home-assistant/core#152219
@PaulSD, would you happen to know more ?
Since the 0.16.0 release consists mainly out of your changes ?

[PaulSD]

The big change in 0.16.0 was upgrading from Debian 12 to Debian 13, which included upgrading from NUT 2.8.0 to NUT 2.8.1

That upgrade wasn't my change (it was handled by the renovate bot) ... After that upgrade, my change was simply adding the apc_modbus plugin to the addon (to make it available to users who want it - it should have no effect on existing users who don't reference that plugin in their config). After both the upgrade and my change, 0.16.0 was released.

So I'm guessing this is a bug in NUT 2.8.1 (or maybe something else in Debian 13, like libusb), and I'm pretty confident it isn't caused by my change specifically.

Note that the "Data stale" error isn't particularly helpful and apparently can be caused by various things (eg. #29 #418).

You might need to enable additional debugging to figure out what is going on here. (Be aware that there was a bug in bashio that broke log_level: trace in the 0.16.0 version of this addon, but a fixed version of bashio should be included in the 0.16.1 version of this addon. That fix is the only significant change between 0.16.0 and 0.16.1)

[Robbe-B]

The big change in 0.16.0 was upgrading from Debian 12 to Debian 13, which included upgrading from NUT 2.8.0 to NUT 2.8.1

That upgrade wasn't my change (it was handled by the renovate bot) ... After that upgrade, my change was simply adding the apc_modbus plugin to the addon (to make it available to users who want it - it should have no effect on existing users who don't reference that plugin in their config). After both the upgrade and my change, 0.16.0 was released.

So I'm guessing this is a bug in NUT 2.8.1 (or maybe something else in Debian 13, like libusb), and I'm pretty confident it isn't caused by my change specifically.

Note that the "Data stale" error isn't particularly helpful and apparently can be caused by various things (eg. #29 #418).

You might need to enable additional debugging to figure out what is going on here. (Be aware that there was a bug in bashio that broke log_level: trace in the 0.16.0 version of this addon, but a fixed version of bashio should be included in the 0.16.1 version of this addon. That fix is the only significant change between 0.16.0 and 0.16.1)

@PaulSD, Thanks for the detailed explanation !
Do note that, for me, it worked great for years up to the 0.16.0 update.
I'm currently on the latest and greatest (0.17.0) and the issue is still present.
I hope someone with enough knowledge about NUT itself can help to resolve this.

[Betacart]

Is there any steps, how to get more useful info for you? In fact, problem now not occurs day by day, but there are days with no issue and sometimes, it happen 2-3 times a day.

[HuisAutomatisering]

My "1425.072514 Poll UPS [EatonEllipsePRO@localhost] failed - Data stale" seems to be stable again after HA update and 0.17.0 Time will tell if we stay good :-)

[PaulSD]

how to get more useful info

Settings -> Add-ons -> Network UPS Tools -> Configuration (tab) -> Edit icon next to the relevant device
-> In the "config" field, add debug_min = 6 and LIBUSB_DEBUG = 4 -> Save -> Save -> Restart

For reference, those config settings are documented here. Of course, if levels 6 and 4 cause it to generate too many logs then you can set those values lower.

You should also check the Linux kernel logs in HA OS, as any low-level driver messages may only show up there (and won't show up in the NUT add-on logs). As far as I am aware, the kernel logs do NOT appear anywhere under Settings -> System -> Logs. However, if you have a Terminal add-on installed, you should be able to see the kernel logs by running dmesg in a terminal.

Note that the add-on log_level (Settings -> Add-ons -> Network UPS Tools -> Configuration (tab) -> Show unused optional configuration options -> log_level) primarily controls logging within the add-on's control scripts (which aren't relevant to your problem here), and doesn't control the logging behavior of NUT itself. So you probably don't need to touch that setting.

Be aware that I myself don't know much about the internals of NUT, and I am not seeing any issues with my UPSs, so I am unlikely to be able to help much with troubleshooting this. If you have trouble interpreting the debug logs or need further assistance in troubleshooting this, you may want to open an issue here.

[Betacart]

Hi, thank you for sharing, how to get more info. Luckily, before I read this info, NUT has problem again (after week of work). I set logging, but as you can see in log, there is a problem with LIBUSB_DEBUG.
Anyway, now, normal procedure to make NUT working again (restart add-on) not helping and it is still not available completely.

Below is part of log:
[08:44:23] INFO: Configuring Device named ups... [08:44:23] INFO: Starting the UPS drivers... upsnotify: notify about state 4 with libsystemd: was requested, but not running as a service unit now, will not spam more about it upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it Network UPS Tools - Generic HID driver 0.52 (2.8.1) USB communication driver (libusb 1.0) 0.46 **Fatal error: 'LIBUSB_DEBUG' is not a valid variable name for this driver.** Look in the man page or call this driver with -h for a list of valid variable names and flags. Network UPS Tools - UPS driver controller 2.8.1 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 [08:44:23] INFO: Starting the UPS information server... 0.000001 fopen /run/nut/upsd.pid: No such file or directory 0.000034 Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running! 0.000450 [D1] debug level is '1' 0.000603 listening on 0.0.0.0 port 3493 0.000788 [D1] Succeeded to become_user(root): now UID=0 GID=0 0.000824 [D1] chdired into statepath /run/nut for driver sockets 0.001001 Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory 0.001045 Found 1 UPS defined in ups.conf 0.001960 Running as foreground process, not saving a PID file 0.001998 upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more about it 0.002023 upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it 0.002099 upsnotify: logged the systemd watchdog situation once, will not spam more about it 0.002122 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 0.002156 [D1] mainloop: UPS [ups] is still not connected (FD -1) 0.014005 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 0.014107 [D1] mainloop: UPS [ups] is still not connected (FD -1) 0.014206 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 0.014247 [D1] mainloop: UPS [ups] is still not connected (FD -1) 0.014302 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 0.014333 [D1] mainloop: UPS [ups] is still not connected (FD -1) [08:44:23] INFO: Starting the UPS monitor and shutdown controller... 0.000001 fopen /run/nut/upsmon.pid: No such file or directory 0.000034 Could not find PID file to see if previous upsmon instance is already running! 0.000312 Using power down flag file /etc/killpower 0.000467 UPS: ups@localhost (primary) (power value 1) 0.000502 [D1] debug level is '1' 0.000573 Warning: running as one big root process by request (upsmon -p) 0.000774 [D1] Saving PID 319 into /run/nut/upsmon.pid Init SSL without certificate database 0.004296 upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more about it 0.004326 upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it 0.004330 upsnotify: logged the systemd watchdog situation once, will not spam more about it 0.004334 [D1] Trying to connect to UPS [ups@localhost] 0.034603 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 0.034727 [D1] mainloop: UPS [ups] is still not connected (FD -1) 0.034844 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 0.034901 [D1] mainloop: UPS [ups] is still not connected (FD -1) 0.035119 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 0.035260 [D1] mainloop: UPS [ups] is still not connected (FD -1) 0.035342 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 0.035454 [D1] mainloop: UPS [ups] is still not connected (FD -1) 0.035572 User upsmonmaster@127.0.0.1 logged into UPS [ups] 0.035685 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 0.006240 [D1] Logged into UPS ups@localhost 0.035786 [D1] mainloop: UPS [ups] is still not connected (FD -1) 0.035852 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 0.035893 [D1] mainloop: UPS [ups] is still not connected (FD -1) 0.006614 Poll UPS [ups@localhost] failed - Driver not connected 0.036592 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 0.036723 [D1] mainloop: UPS [ups] is still not connected (FD -1) {"message":"Event nut.ups_event fired."}Network UPS Tools upsmon 2.8.1 1.101428 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 1.101560 [D1] mainloop: UPS [ups] is still not connected (FD -1) 1.101722 [D1] mainloop: UPS [ups] is not currently connected, trying to reconnect 1.101769 [D1] mainloop: UPS [ups] is still not connected (FD -1)