New devices discovered, but I cant connect to server

[tomasenskede]

This is my log..

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
[16:31:19] INFO: Configuring timezone (Europe/Stockholm)...
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
[16:31:20] INFO: Setting mode to netserver...
[16:31:20] INFO: Generating /etc/nut/upsd.users...
[16:31:20] INFO: Configuring user: nutusername
[16:31:20] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[16:31:21] INFO: Configuring Device named PP100...
[16:31:21] INFO: Starting the UPS drivers...
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
[16:31:26] INFO: Starting the UPS information server...
   0.000000	fopen /run/nut/upsd.pid: No such file or directory
   0.000391	Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running!
   0.000885	[D1] debug level is '1'
   0.001261	listening on 0.0.0.0 port 3493
   0.001822	Connected to UPS [PP100]: richcomm_usb-PP100
   0.003543	Running as foreground process, not saving a PID file
[16:31:26] INFO: Starting the UPS monitor and shutdown controller...
   0.000000	fopen /run/nut/upsmon.pid: No such file or directory
   0.000427	Could not find PID file to see if previous upsmon instance is already running!
   0.000875	Using power down flag file /etc/killpower
   0.001397	UPS: PP100@localhost (primary) (power value 1)
   0.001671	[D1] debug level is '1'
   0.001970	[D1] debug level is '1'
   0.002199	Warning: running as one big root process by request (upsmon -p)
   0.002559	[D1] Saving PID 460 into /run/nut/upsmon.pid
Init SSL without certificate database
   0.005032	[D1] Trying to connect to UPS [PP100@localhost]
   0.017678	User [email protected] logged into UPS [PP100]
   0.006281	[D1] Logged into UPS PP100@localhost
{"message":"Event nut.ups_event fired."}Network UPS Tools upsmon 2.8.0  # I get alerts from UPS when power is cut and restored
{"message":"Event nut.ups_event fired."}Network UPS Tools upsmon 2.8.0
{"message":"Event nut.ups_event fired."}Network UPS Tools upsmon 2.8.0
{"message":"Event nut.ups_event fired."}Network UPS Tools upsmon 2.8.0

So whats wrong? Cant cant I connect to then servern

I am running both server and client within Home Assistant. Server as add-in and then the client is auto discovered... but cant conntect to server. any idea?

[Am0din]

Are you running your HomeAssistant on its own machine with a UPS connected via USB , or is it on something else like Proxmox? This makes a difference in how to set this up.