Network UPS server failed after update HA OS 17.3

Configuration
1

Hello,

After upgrading my HA OS to version 17.3, the Network UPS Tools server failed to start

My Logs :


-----------------------------------------------------------
 App: Network UPS Tools
 Manage battery backup (UPS) devices
-----------------------------------------------------------
 App version: 0.18.0
 You are running the latest version of this app.
 System: Home Assistant OS 17.3  (amd64 / generic-x86-64)
 Home Assistant Core: 2026.5.0
 Home Assistant Supervisor: 2026.04.2
-----------------------------------------------------------
 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-app-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-app-timezone: starting
s6-rc: info: service base-app-log-level: starting
s6-rc: info: service fix-attrs successfully started
[20:01:39] INFO: Configuring timezone (Europe/Paris)...
s6-rc: info: service base-app-log-level successfully started
s6-rc: info: service base-app-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/nut.sh
[20:01:39] INFO: Setting mode to netserver...
[20:01:39] INFO: Connected USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux 6.12.85-haos xhci-hcd xHCI Host Controller
Bus 001 Device 002: ID 0463:ffff EATON Ellipse ECO
Bus 001 Device 003: ID 2109:2813 VIA Labs, Inc. USB2.0 Hub
Bus 001 Device 004: ID 8087:0aaa  
Bus 001 Device 005: ID 0658:0200  
Bus 001 Device 006: ID 1cf1:0030 dresden elektronik ingenieurtechnik GmbH ConBee II
Bus 001 Device 007: ID 10c4:ea60 Nabu Casa Home Assistant Connect ZBT-1
Bus 002 Device 001: ID 1d6b:0003 Linux 6.12.85-haos xhci-hcd xHCI Host Controller
Bus 002 Device 002: ID 2109:0813 VIA Labs, Inc. USB3.0 Hub
[20:01:39] INFO: Generating /etc/nut/upsd.users...
[20:01:39] INFO: Configuring user: nut
[20:01:39] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[20:01:39] INFO: Configuring Device named myups...
[20:01:39] INFO: Registering supervised driver service for myups...
unable to initialize usb speccont-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 nut-driver-myups (no readiness notification)
services-up: info: copying legacy longrun upsd (no readiness notification)
services-up: info: copying legacy longrun upsmon (no readiness notification)
[20:01:39] INFO: Starting the UPS information server...
Network UPS Tools 2.8.5 release - Generic HID driver 0.71
USB communication driver (libusb 1.0) 0.53
   0.000000	fopen /var/state/ups/upsd.pid: No such file or directory
   0.000010	[D1:upsd] Just failed to send signal, no daemon was running
Network UPS Tools upsd 2.8.5 release
   0.000190	[D1:upsd] update_sysmaxconn: defaulting maxconn to sysmaxconn: 1024
   0.000328	[D1:upsd] debug level is '1'
   0.000373	listening on 0.0.0.0 port 3493
   0.000390	[D1:upsd] setuptcp: SERVER listener [0.0.0.0:3493] on FD 3
   0.000404	[D1:upsd] server_load: tried to set up 1 listening sockets, succeeded with 1
   0.000489	[D1:upsd] Succeeded to become_user(root): now UID=0 GID=0
   0.000506	[D1:upsd] chdired into statepath /var/state/ups for driver sockets
   0.000524	WARNING: /var/state/ups is world readable (hope you don't have passwords there)
   0.000657	Can't connect to UPS [myups] (/var/state/ups/usbhid-ups-myups): No such file or directory
   0.000671	[D1:upsd] poll_reload: (p)re-allocate 1024 entries for polling FDs and handlers
   0.000693	Found 1 UPS defined in ups.conf
   0.001736	WARNING: /etc/nut/upsd.users is world readable (hope you don't have passwords there)
   0.001785	Running as foreground process, not saving a PID file
   0.001804	[D1:upsd] upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it
   0.001820	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.001846	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   0.007363	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.007391	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   0.007625	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.007646	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   0.007661	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.007674	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
[20:01:40] INFO: Starting the UPS monitor and shutdown controller...
   0.000086	[D1:libupsclient:init] upscli_init_default_connect_timeout: upscli_default_connect_timeout=10.000000 sec assigned from: default_secs
   0.000119	fopen /var/state/ups/upsmon.pid: No such file or directory
   0.000122	[D1:init] Just failed to send signal, no daemon was running
   0.000140	[D1:init] loadconfig: Loading /etc/nut/upsmon.conf
Network UPS Tools upsmon 2.8.5 release
   0.000366	Using power down flag file /etc/killpower
   0.000556	UPS: myups@localhost (primary) (power value 1)
   0.000574	[D1:init] debug level is '1'
   0.000578	[D1:init] will use a shutdown command (SHUTDOWNCMD): '/run/s6/basedir/bin/halt'
   0.000581	[D1:init] will use custom notification command (NOTIFYCMD): '/usr/bin/notify'
   0.000616	Warning: running as one big root process by request (upsmon -p)
   0.000667	[D1:mono] Saving PID 336 into /run/upsmon.pid
   0.004085	[D1:libupsclient:mono] upscli_init: completed
   0.004110	[D1:mono] upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it
   0.004114	[D1:mono] Trying to connect to UPS [myups@localhost]
   0.015526	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.015563	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   0.015606	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.015632	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   0.015700	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.015771	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   0.015824	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.015850	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   0.015894	User [email protected] logged into UPS [myups]
   0.004845	[D1:mono] Logged into UPS myups@localhost
   0.015951	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.015977	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   0.016008	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.016033	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   0.016069	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.016089	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   0.016114	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.016136	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   0.016159	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   0.005086	Poll UPS [myups@localhost] failed - Driver not connected
   0.016179	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
s6-rc: info: service legacy-services successfully started
   2.018411	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   2.018545	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
Using subdriver: MGE HID 1.58
   4.020883	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   4.021178	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   5.017094	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   5.017373	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   5.017660	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   5.017909	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
   5.018317	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   5.007369	Poll UPS [myups@localhost] failed - Driver not connected
   5.018460	[D1:upsd] mainloop: UPS [myups] driver is still not connected (FD -1)
Listening on socket /var/state/ups/usbhid-ups-myups
Running as foreground process, not saving a PID file
   7.020833	[D1:upsd] mainloop: UPS [myups] driver is not currently connected, trying to reconnect
   7.021228	Connected to UPS [myups]: usbhid-ups-myups
sock_connect: enabling asynchronous mode (auto)
   7.021454	[D1:upsd] mainloop: UPS [myups] driver is now connected as FD 5

Can you help me

Regards,

2

That release was a security fix only: Release Home Assistant OS 17.3 · home-assistant/operating-system · GitHub

Though it does say:

Fixing this CVE only meaningfully improves the security posture for apps (formerly add-ons) that intentionally drop privileges (apps running as a non-root user).

Try running the NUT add-on with protection mode disabled.

3

Hi,

Thank you for your help.
I have enabled Advanced Mode in my profile,
but I can’t find the Advanced Mode Google switch or anything like that in the NUT add-on.

Regards

4

Not Advanced mode, but never mind. That is not available for that add-on.

5

I'm seeing the same issue on my end after update to 17.3.
Edit: I was able to get mine working by going into the integration's Reconfigure menu, and changing the host from 'localhost' to 'a0d7b954-nut'. @Fred14320, see if that does it for you.

6

This worked for me. Where did you find the "a0d7b954-nut" name?

7

It's well hidden. In the setup docs on the github page for the NUT addon, sorry, app, it tells you to look in the info page for your newly installed Network UPS Tools and find "hostname" to get the value. But it seems to always be "a0d7b954-nut" in every instance, so I don't know why the docs don't just say that instead.

That same hex string appears in other HA topics, too, and I think it really means "Simon says: 'localhost'".

8

Hi,

I solved changing the integration configuration from localhost to 127.0.0.1.

1 Like
9

Hello,

I solved it by changing the integration configuration from localhost to 127.0.0.1.
I tried changing it to my local IP and it worked too.

Thank you for your help
best regards