UPS NUT with hub connected USB cable connection under HA OS 5.11

Configuration
1

I’m using a Pi4 and so have my zWave stick connected via a USB hub (its a PI4 thing). So the hub uses one of the USB ports on the Pi4. The other 3 are also in use (RFXTRX, Connbee II, serial port to my Alarm) so my UPS is also connected through the USB hub.

Following upgrade to the HA OS 5.11, NUT is ceasing to recognise the USB connection for UPS handling. Has anyone else experienced this? It looks from the logs like the Network UPS Tools - UPS driver controller 2.7.4 is failing to recognise the UPS USB connection through the hub (it did before HA OS 5.11

Any suggestions?

2

There were changes made in the latest Supervisor update that required some addons to be updated.
I use this one that now works.

https://github.com/hassio-addons/addon-nut

3

Logs from the nut addon would be helpful.

4

I’d uninstalled and re-installed the integration. That didn’t result in any change in status.

Here’s the logs I get;

[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.6.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 5.11  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2021.2.3
 Home Assistant Supervisor: 2021.02.6
-----------------------------------------------------------
 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... 
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nut.sh: executing... 
[15:25:06] INFO: Setting mode to netserver...
[15:25:06] INFO: Connected USB devices:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik 
Bus 001 Device 007: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Bus 001 Device 005: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[15:25:06] INFO: Generating /etc/nut/upsd.users...
[15:25:06] INFO: Configuring user: xxxxxxxxx
[15:25:06] DEBUG: Password SHA1: 8586C2F313210D6EC24298FDFD30B454693BEA21
[15:25:06] DEBUG: Requested API resource: https://api.pwnedpasswords.com/range/8586C
[15:25:06] DEBUG: API HTTP Response code: 200
[15:25:06] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[15:25:06] INFO: Configuring Device named myups...
[15:25:06] INFO: Starting the UPS drivers...
   0.000000	Starting UPS: myups
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
No matching HID UPS found
Network UPS Tools - UPS driver controller 2.7.4
   0.067778	Driver failed to start (exit status=1)
[cont-init.d] nut.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
5

Which one of the USB devices is your UPS?

6

I think that’s where the issue is. It’s not recognising the UPS because it’s connected to a hub rather than directly. Prior to OS5.11 it was recognised.

7

Configuration is as follows;

users:
  - username: xxxxxxxxx
    password: xxxxxxxx
    instcmds:
      - all
    actions: []
devices:
  - name: myups
    driver: usbhid-ups
    port: auto
    config: []
mode: netserver
shutdown_host: 'false'
log_level: debug
list_usb_devices: 'true'
8

Hi,
I have exactly the same problem as you described.
Did you found some kind of solution?

9

To be honest, no I didn’t or rather not directly. I figured it was some form of compatibility issue with the USB hub and when I thought about it the UPS installed in its current form wasn’t actually going to do what I wanted when power is cut, so I’ve actually attached it to another server I have and operate it from there where is forces the other server to shut down when there is a loss of power. What I need to do now is work out how to get it to shut down the HA server (Rasp pi 4) when there is a prolonged loss of power and then to shut the host server. Haven’t yet worked out the right commands but figure this is doable.