Cannot get Network UPS Tools Current version: 0.13.2. working on RPi5/HAOS

Configuration
1

I am trying to add monitoring for a second UPS to my Rpi5/HAOS installation
I already am running the ‘Network UPS Tools’ integration which connects to a Synology NAS and obtains its UPS monitoring info from that. This works fine

I now have a second UPS (BR900MI), which I connect directly to the USB port on the Rpi

For this, I added the 0.13.2 Network UPS Tools Add-on, but when I start this I get errors

Network UPS Tools - UPS driver controller 2.8.0
cont-init: info: /etc/cont-init.d/nut.sh exited 1
cont-init: info: running /etc/cont-init.d/nutclient.sh
cont-init: info: /etc/cont-init.d/nutclient.sh exited 0
cont-init: warning: some scripts exited nonzero
s6-rc: warning: unable to start service legacy-cont-init: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-timezone: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-timezone successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
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.13.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.1  (aarch64 / raspberrypi5-64)
 Home Assistant Core: 2024.10.2
 Home Assistant Supervisor: 2024.10.0
-----------------------------------------------------------
 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
[21:30:41] INFO: Configuring timezone (Asia/Singapore)...
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
[21:30:41] INFO: Setting mode to netserver...
[21:30:42] INFO: Generating /etc/nut/upsd.users...
[21:30:42] INFO: Configuring user: upsadmin
[21:30:42] DEBUG: Password SHA1: 3B...A1
[21:30:42] DEBUG: Requested API resource: https://api.pwnedpasswords.com/range/3B300
[21:30:42] DEBUG: API HTTP Response code: 200
[21:30:42] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[21:30:42] INFO: Configuring Device named ups-living...
[21:30:42] INFO: Starting the UPS drivers...
   0.000000	[D1] Starting UPS: ups-living
Fatal error: unusable configuration
Network UPS Tools - APC Smart protocol driver 3.2 (2.8.0)
APC command table version 3.1

Unable to open auto: No such file or directory

Things to try:

 - Check 'port=' in ups.conf

 - Check owner/permissions of all parts of path

   0.004326	Driver failed to start (exit status=1)
Network UPS Tools - UPS driver controller 2.8.0
cont-init: info: /etc/cont-init.d/nut.sh exited 1
cont-init: info: running /etc/cont-init.d/nutclient.sh
cont-init: info: /etc/cont-init.d/nutclient.sh exited 0
cont-init: warning: some scripts exited nonzero
s6-rc: warning: unable to start service legacy-cont-init: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-timezone: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-timezone successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

The configuration:

- username: upsadmin
  password: X+ajsG].gyUFanSmZCT]-/
  instcmds:
    - all
  actions: []

and

- name: ups-living
  driver: apcsmart
  port: auto
  config: []

I have seen many similar posts that also quote a upsd.conf etc, but I cannot find that file at all.

Believing the issue to be with the USB ports, i checked:

$ lsusb
Bus 003 Device 001: ID 1d6b:0002
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 10c4:ea60
Bus 004 Device 001: ID 1d6b:0003
Bus 002 Device 001: ID 1d6b:0003
Bus 003 Device 002: ID 10c4:ea60

but i don’t see the UPS being connected/recognized yet:

# dmesg
...
[    0.933156] usb 3-1: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[    0.933168] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    0.933173] usb 3-1: Product: CP2102 USB to UART Bridge Controller
[    0.933179] usb 3-1: Manufacturer: Silicon Labs
[    0.933183] usb 3-1: SerialNumber: 0001
[    0.933628] usb 1-1: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[    0.933637] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    0.933642] usb 1-1: Product: Sonoff Zigbee 3.0 USB Dongle Plus
[    0.933647] usb 1-1: Manufacturer: ITead
[    0.933651] usb 1-1: SerialNumber: 3a5d3d831dafed118008374e71c9e8b5
...
[    1.418995] cp210x 3-1:1.0: cp210x converter detected
[    1.421800] usb 3-1: cp210x converter now attached to ttyUSB0
[    1.421889] cp210x 1-1:1.0: cp210x converter detected
[    1.423479] usb 1-1: cp210x converter now attached to ttyUSB1
2

See addon-nut/nut/DOCS.md at cad232c051e89244feb645e02fd29e72e4211e4b · hassio-addons/addon-nut · GitHub for examples…

3

that wasn’t very helpful

4

Check my thread in the social section. I posted a video on how to set up the nut add on.

5

Was 't it? Don’t you see your configuration is wrong by looking at working examples?

6

Thanks. I assume you mean the ‘https://www.youtube.com/watch?v=VMavnNyt4kM’ video

I did exactly that, and the config look exactly like that.

My config looks exactly like yours:

No, i didn’t see anything wrong in the config.

Yet, for me the Add-on did not even start. (@5:49) so returning to settings. As i wrote, i already have the related integration working and talking to another Synology-NAS operated NUT.

What ultimately made this work was completely disconnecting the USB cable between the UPS and the Hassio Rpi, restarting the Rpi and then reconnecting it. No change in config, so your pointer to working configs w/o any suggestion what might have been wrong was not helpful. It’s just ‘RTFM’, which I had

7

No, I meant the actual doc that I linked.
Good for you that it worked anyway, although I don’t understand how with the config you posted…

8

Sorry. seems i pasted the wrong link (which was the video from another response)

The link you pointed to shows as config:

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

and I fail to see how that is different from what i posted (albeit in separate sections for ‘users’ and ‘devices’ as it is shown in the ‘configuration’ tab. (and i didn’t show the mode and shutdown_host, as they are represented as graphic toggles and not in the yaml in the HA GUI)

So if you think my config (which is not changed from the default, modulo the driver used (apcsmart vs usbhid-ups) should not work, can you point out what you think is wrong? because to me they look the same

9

Ah, looks like you pasted bits and pieces of your configuration, rather than the whole file, hence the confusion.

Avoid doing this in the future. As you can see, it leads to confusion and irrelevant responses.