NUT server is setup and running, having issue with connecting clients. From log:
s6-rc: info: service base-app-banner: starting
-----------------------------------------------------------
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 18.2 (aarch64 / yellow)
Home Assistant Core: 2026.8.1
Home Assistant Supervisor: 2026.07.5
-----------------------------------------------------------
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
[13:01:55] INFO: Configuring timezone (America/New_York)...
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
[13:01:56] INFO: Setting mode to netserver...
[13:01:56] INFO: Generating /etc/nut/upsd.users...
[13:01:56] INFO: Configuring user: ADMUPSDS
[13:01:57] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[13:01:57] INFO: Configuring user: observer
[13:01:58] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[13:01:58] INFO: Configuring Device named SU1000XL...
[13:01:58] INFO: Registering supervised driver service for SU1000XL...
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 nut-driver-SU1000XL (no readiness notification)
services-up: info: copying legacy longrun upsd (no readiness notification)
services-up: info: copying legacy longrun upsmon (no readiness notification)
Network UPS Tools 2.8.5 release - Generic SNMP UPS driver 1.40
s6-rc: info: service legacy-services successfully started
Created directory: /var/lib/snmp/cert_indexes
No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.7'!
Please report it to NUT developers, with an 'upsc' output for your device.
Going back to the classic MIB detection method.
No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.7'!
Please report it to NUT developers, with an 'upsc' output for your device.
Going back to the classic MIB detection method.
No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.7'!
Please report it to NUT developers, with an 'upsc' output for your device.
Going back to the classic MIB detection method.
[13:01:58] INFO: Starting the UPS information server...
Only the IETF standard mapping was found as fallback. Please check https://www.networkupstools.org/historic/v2.8.5/docs/developer-guide.chunked/new-drivers.html#snmp-subdrivers for suggestions how you can help improve the driver to support vendor-specific mappings for your device better.
Detected Smart-UPS 1000 XL on host 192.168.1.16 (mib: apcc 1.61)
Network UPS Tools upsd 2.8.5 release
0.000000 fopen /var/state/ups/upsd.pid: No such file or directory
0.000029 [D1:upsd] Just failed to send signal, no daemon was running
0.000540 [D1:upsd] update_sysmaxconn: defaulting maxconn to sysmaxconn: 1024
0.001354 [D1:upsd] debug level is '1'
0.001675 listening on 0.0.0.0 port 3493
0.001947 [D1:upsd] setuptcp: SERVER listener [0.0.0.0:3493] on FD 3
0.002236 [D1:upsd] server_load: tried to set up 1 listening sockets, succeeded with 1
0.002611 [D1:upsd] Succeeded to become_user(root): now UID=0 GID=0
0.002708 [D1:upsd] chdired into statepath /var/state/ups for driver sockets
0.002777 WARNING: /var/state/ups is world readable (hope you don't have passwords there)
0.003189 Can't connect to UPS [SU1000XL] (/var/state/ups/snmp-ups-SU1000XL): No such file or directory
0.003485 [D1:upsd] poll_reload: (p)re-allocate 1024 entries for polling FDs and handlers
0.003706 Found 1 UPS defined in ups.conf
0.005884 WARNING: /etc/nut/upsd.users is world readable (hope you don't have passwords there)
0.006320 Running as foreground process, not saving a PID file
0.006581 [D1:upsd] upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it
0.006788 [D1:upsd] mainloop: UPS [SU1000XL] driver is not currently connected, trying to reconnect
0.006932 [D1:upsd] mainloop: UPS [SU1000XL] driver is still not connected (FD -1)
Listening on socket /var/state/ups/snmp-ups-SU1000XL
Running as foreground process, not saving a PID file
0.495409 [D1:upsd] mainloop: UPS [SU1000XL] driver is not currently connected, trying to reconnect
0.495650 Connected to UPS [SU1000XL]: snmp-ups-SU1000XL
0.495740 [D1:upsd] mainloop: UPS [SU1000XL] driver is now connected as FD 5
sock_connect: enabling asynchronous mode (auto)
[13:01:59] INFO: Starting the UPS monitor and shutdown controller...
Network UPS Tools upsmon 2.8.5 release
0.000429 [D1:libupsclient:init] upscli_init_default_connect_timeout: upscli_default_connect_timeout=10.000000 sec assigned from: default_secs
0.000611 fopen /var/state/ups/upsmon.pid: No such file or directory
0.000645 [D1:init] Just failed to send signal, no daemon was running
0.000758 [D1:init] loadconfig: Loading /etc/nut/upsmon.conf
0.001073 Using power down flag file /etc/killpower
0.001438 UPS: SU1000XL@localhost (primary) (power value 1)
0.001618 [D1:init] debug level is '1'
0.001708 [D1:init] will use a shutdown command (SHUTDOWNCMD): '/run/s6/basedir/bin/halt'
0.001761 [D1:init] will use custom notification command (NOTIFYCMD): '/usr/bin/notify'
0.001892 Warning: running as one big root process by request (upsmon -p)
0.002091 [D1:mono] Saving PID 385 into /run/upsmon.pid
0.010924 [D1:libupsclient:mono] upscli_init: completed
0.011100 [D1:mono] upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it
0.011118 [D1:mono] Trying to connect to UPS [SU1000XL@localhost]
0.534173 User [email protected] logged into UPS [SU1000XL]
0.013345 [D1:mono] Logged into UPS SU1000XL@localhost
It is setup to lisyen on 0.0.0.0:3493
When checked using telnet, I get this:
C:\WINDOWS\system32>telnet 192.168.2.254 3493
Connecting To 192.168.2.254…Could not open connection to the host, on port 3493: Connect failed
C:\WINDOWS\system32>telnet 192.168.2.254 3493
Connecting To 192.168.2.254…Could not open connection to the host, on port 3493: Connect failed
C:\WINDOWS\system32>
I’m trying to get WinNut Client to connect
This is running on HA - Yellow, I can’t even find the container for it like I can for NodeRed, ESPHome, SSH, etc
Any one have any ideas on what is wrong? I’m stumped