I am having a heck of a time figuring out what I need to do. I have a Debian server running HA in Docker. It's connected to a CyberPower UPS with a USB cable.

Now what? Do I have to install NUT on the server first, and then HA, or something else?

Hello.

I have a NUT server running on a pfSense router. The server all works great. I can telnet into port 3493 on pfSense from an unrelated Linux server and pfSense responds. The UPS connected to the router is an Eaton. pfSense responds correctly to UPS events so the server seems correctly configured.

I am running HA in a container on a Synology DS1522. I didn't do anything special when I added this container - just selected the available image and accepted all the defaults. HA seems to be running fine and I have several devices configured (including a couple running apcupsd, which is not available on Eaton UPS).

I am trying to add an integration into HA for the Eaton UPS. I click on Settings/Integrations/Add Integration, search for NUT. Network UPS Tools comes up, so I click on it and it gives me a dialog box "Connect to the NUT server."

No matter what I put in the fields of this dialog box it comes back "Failed to Connect." I found some posts that said the hostname should be a0d7b954-nut instead of something I'd expect, but that doesn't work either.

What is this dialog box looking for?

Hello,

I'm trying to figure out how to properly configure the Network UPS Tools addon. I'm running the server on my Raspberry Pi with RPI OS, which is connected via USB to my UPS. HAOS is running on a seperate RPI.

Server config:

ups.conf:

pollinterval = 1
maxretry = 3

[cyberpowerups]
    driver = usbhid-ups
    port = auto
    desc = "CP900EPFCLCD"
    vendorid = 0764
    productid = 0501

upsd.users:

[admin]
       password = xxx
       admin master
       instcmds = all
       actions = set
       actions = fsd

[testuser]
        password = xxx
        instcmds = test.battery.start
        instcmds = test.battery.stop
        instcmds = test.battery.start.quick
        instcmds = test.battery.start.deep

[observer]
        password = xxx
        upsmon secondary

nut.conf:

MODE=netserver

upsd.conf:

LISTEN 0.0.0.0 3493

upsmon.conf:

RUN_AS_USER root

MONITOR cyberpowerups@localhost 1 admin xxxmaster

HA config:

devices:
  - config: []
    driver: usbhid-ups
    name: cyberpowerups
    port: '3493'
mode: netclient
shutdown_host: 'false'
users:
  - actions: []
    instcmds:
      - all
    password: xxx
    username: upsmon
remote_ups_name: cyberpowerups
remote_ups_host: 192.168.178.36
remote_ups_user: upsmon
remote_ups_password: xxx
list_usb_devices: false
log_level: debug

Log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] nut: applying... 
[fix-attrs.d] nut: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Network UPS Tools
 Manage battery backup (UPS) devices
-----------------------------------------------------------
 Add-on version: 0.9.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 7.4  (aarch64 / raspberrypi3-64)
 Home Assistant Core: 2022.3.2
 Home Assistant Supervisor: 2022.01.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nut.sh: executing... 
[16:53:10] INFO: Setting mode to netclient...
[cont-init.d] nut.sh: exited 0.
[cont-init.d] nutclient.sh: executing... 
[cont-init.d] nutclient.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[16:53:16] INFO: Starting the UPS monitor and shutdown controller...
   0.000000	fopen /run/nut/upsmon.pid: No such file or directory
   0.001141	Using power down flag file /etc/killpower
   0.001711	UPS: cyberpowerups@192.168.178.36 (slave) (power value 1)
   0.002169	debug level is '1'
   0.002262	Warning: running as one big root process by request (upsmon -p)
   0.007702	Init SSL without certificate database
   0.048465	Trying to connect to UPS [cyberpowerups@192.168.178.36]
   0.054120	Login on UPS [cyberpowerups@192.168.178.36] failed - got [ERR ACCESS-DENIED]
{"message": "Event nut.ups_event fired."}Network UPS Tools upsmon 2.7.4

The passwords are correct, I always copy paste them and double checked. I setup the integration by providing the remote IP, upsmon and pass and it works. The addon doesn't seem to work properly (at least it's not able to connect). What do I have to do to fix this?

Hi Folks, I've been beating on this for hours, I hope you can help. I have an APC ES 550 plugged into my RPi 3 by USB, running Home Assistant installed from the Raspberry Pi Imager.

I have installed the Settings > Add-ons > Network UPS Tools. In Configuration I have added a username and password.

users:
  - username: nutuser
    password: nutpass
    instcmds:
      - all
    actions: []
devices:
  - name: myups
    driver: usbhid-ups
    port: auto
    config: []
mode: netserver
shutdown_host: "false"

When it starts, I get a Hostname: a0d7b954-nut. So far, so good.

I then add the integration Settings > Devices and Services > Network UPS Tools (NUT). It asks for 4 things which I enter:

Host: a0d7b954-nut
Port: 3493
Username: nutuser
Password: nutpass

From here, no matter how I fiddle with it, it always responds with: " Failed to connect ".

I have confirmed that the USB Device path /dev/bus/usb/001/005 can see the ID_USB_MODEL: Back-UPS_ES_550_FW:843.K1_.D_USB_FW:K1.

Everyone else talks about how easy this is to integrate, what am I doing wrong?

THANKS