NUT server HA add-in unreachable from network clients

I successfully installed the NUT add-in in master mode and the NUT integration is working. I can see that TCP port 3493 is listening for connections. But I cannot connect to it from the NUT client on my Windows machine. Has anyone gotten this working or have any suggestions?

Home Assistant OS is running in a VM on an ESXi 7 host. The Windows client is running on Windows 10.

> users:
>   - username: admin
>     password: xxxxxxxxx
>     instcmds:
>       - all
>     actions: []
> devices:
>   - name: myups
>     driver: usbhid-ups
>     port: auto
>     config: []
> mode: netserver
> shutdown_host: false
> upsmon: master
> list_usb_devices: true
> log_level: debug> 
> 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.2  (amd64 / qemux86-64)
>  Home Assistant Core: 2023.6.2
>  Home Assistant Supervisor: 2023.06.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-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
> [03:57:08] INFO: Configuring timezone (America/New_York)...
> Log level is set to DEBUG
> 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
> [03:57:09] INFO: Setting mode to netserver...
> [03:57:09] INFO: Connected USB devices:
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 005: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
> Bus 002 Device 004: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
> Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
> Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> [03:57:09] INFO: Generating /etc/nut/upsd.users...
> [03:57:09] INFO: Configuring user: admin
> [03:57:10] DEBUG: Password SHA1: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> [03:57:10] DEBUG: Requested API resource: https://api.pwnedpasswords.com/range/26CDA
> [03:57:10] DEBUG: API HTTP Response code: 200
> [03:57:10] INFO: Password is NOT in the Have I Been Pwned database! Nice!
> [03:57:10] INFO: Configuring Device named myups...
> [03:57:10] INFO: Starting the UPS drivers...
>    0.000000	[D1] Starting UPS: myups
> 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
> 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
> [03:57:11] INFO: Starting the UPS information server...
>    0.000000	fopen /run/nut/upsd.pid: No such file or directory
>    0.000310	Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running!
>    0.001036	[D1] debug level is '1'
>    0.001277	listening on 0.0.0.0 port 3493
>    0.001769	Connected to UPS [myups]: usbhid-ups-myups
>    0.002625	Running as foreground process, not saving a PID file
> [03:57:11] INFO: Starting the UPS monitor and shutdown controller...
>    0.000000	fopen /run/nut/upsmon.pid: No such file or directory
>    0.000024	Could not find PID file to see if previous upsmon instance is already running!
>    0.000107	Using power down flag file /etc/killpower
>    0.000153	UPS: myups@localhost (primary) (power value 1)
>    0.000164	[D1] debug level is '1'
>    0.000179	[D1] debug level is '1'
>    0.000181	Warning: running as one big root process by request (upsmon -p)
>    0.000218	[D1] Saving PID 469 into /run/nut/upsmon.pid
> Init SSL without certificate database
>    0.081348	[D1] Trying to connect to UPS [myups@localhost]
>    0.551103	User [email protected] logged into UPS [myups]
>    0.082599	[D1] Logged into UPS myups@localhost

I had the same log errors. Go to your integrations and add the NUT tool. Under host add " a0d7b954-nut" then leave the port auto filled and add your credentials and it should work.

2 Likes

Thank you, that was the solution to the problem I had earlier, getting the integration to work. Using that host name in the NUT integration works just fine.

But now Iā€™m trying to get the client on my Windows desktop to connect to the NUT server Home Assistant add-on. No solution so far.

Did you ever find the solution to this?

I stopped looking for solutions for a Windows client and moved on to other stuff.