NUT with Cyberpower LE850G

nlatman · December 27, 2025, 9:41pm

I am having a combination of issues. When I plug UPS USB in it works for about 15 minutes before data going stale. I am able to add the device, it is recognized, and I am able to create automations based on its status. Unfortunately, once UPS reads as stale I can’t simply restart Network UPS Tools because I get the libusb1: Could not open any HID devices: insufficient permissions on everything error. At that point I can unplug\replug the USB into the UPS and it works for 15 minutes or so. I’ve tried changing the poll interval but nothing works.

Below are the logs when I try to restart NUT

Network UPS Tools

Bus 001 Device 013: ID 248a:8327 Maxxter Wireless Receiver

Bus 001 Device 016: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

[16:07:41] INFO: Generating /etc/nut/upsd.users…

[16:07:41] INFO: Configuring user: nutty

[16:07:41] INFO: Password is NOT in the Have I Been Pwned database! Nice!

[16:07:41] INFO: Configuring Device named myups…

[16:07:41] INFO: Starting the UPS drivers…

libusb1: Could not open any HID devices: insufficient permissions on everything

No matching HID UPS found

upsnotify: notify about state 4 with libsystemd: was requested, but not running as a service unit now, will not spam more about it

upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it

Network UPS Tools - Generic HID driver 0.52 (2.8.1)

USB communication driver (libusb 1.0) 0.46

Network UPS Tools - UPS driver controller 2.8.1

Driver failed to start (exit status=1)

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.17.0

You are running the latest version of this add-on.

System: Home Assistant OS 16.3 (amd64 / generic-x86-64)

Home Assistant Core: 2025.12.4

Home Assistant Supervisor: 2025.12.3

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:07:45] INFO: Configuring timezone (America/New_York)…

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:07:45] INFO: Setting mode to netserver…

[16:07:45] INFO: Connected USB devices:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 002: ID 10c4:ea70 Silicon Labs CP2105 Dual UART Bridge

Bus 001 Device 004: ID 10c4:ea60 Silicon Labs CP210x UART Bridge

Bus 001 Device 005: ID 0573:1573 Zoran Co. Personal Media Division (Nogatech) USB Audio and HID

Bus 001 Device 006: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio

Bus 001 Device 013: ID 248a:8327 Maxxter Wireless Receiver

Bus 001 Device 016: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

[16:07:45] INFO: Generating /etc/nut/upsd.users…

[16:07:45] INFO: Configuring user: nutty

[16:07:45] INFO: Password is NOT in the Have I Been Pwned database! Nice!

[16:07:45] INFO: Configuring Device named myups…

[16:07:45] INFO: Starting the UPS drivers…

Network UPS Tools - Generic HID driver 0.52 (2.8.1)

USB communication driver (libusb 1.0) 0.46

libusb1: Could not open any HID devices: insufficient permissions on everything

No matching HID UPS found

upsnotify: notify about state 4 with libsystemd: was requested, but not running as a service unit now, will not spam more about it

upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it

Driver failed to start (exit status=1)

Network UPS Tools - UPS driver controller 2.8.1

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 base-addon-timezone successfully stopped

s6-rc: info: service fix-attrs 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

lordwizzard · December 27, 2025, 9:51pm

First restart of the server then reload the integration

alias: NUT Restart
description: Nut Restart for System Test Date
triggers:
  - trigger: time
    at: "20:50:00"
    weekday:
      - tue
conditions: []
actions:
  - action: hassio.addon_restart
    data:
      addon: a0d7b954_nut
  - delay:
      hours: 0
      minutes: 1
      seconds: 0
      milliseconds: 0
  - action: homeassistant.reload_config_entry
    metadata: {}
    data:
      entry_id: 96b7eadc33773445e65024aa623475bc
mode: single

You may have to change the entity_id to match your own

nlatman · December 27, 2025, 11:00pm

I don’t think this helps in my situation. Even when I reboot the server the UPS isn’t recognized. The only thing that seems to “wake it up” is when I unplug the USB from the UPS itself. I’m starting to think it’s an issue with the UPS itself, may test with another UPS.

lordwizzard · December 27, 2025, 11:37pm

That is a good idea, but it could be a USB driver problem on either end. As always make sure the USB driver firmware is up to date.