Ich habe HA mit den Network UPS Tools auf einem Proxmox 8.2.4 als VM installiert. Angeschlossen ist eine Digitus DN-170041 per USB.
lsusb ergibt:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:0329 Realtek Semiconductor Corp. USB3.0-CRW
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 046a:b090 CHERRY Keyboard
Bus 002 Device 002: ID 0424:2660 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005 ist der entsprechende Anschluss der auch zur VM durchgereicht ist:
USB-Gerät (usb0) host=0665:5161
Die config im HA unter devices
- name: DN-170042
driver: blazer_usb
port: auto
config:
- vendor = "DIGITUS.*"
Laut Network UPS Tools Hardware Compatibility List ist dies der richtige Treiber. Alternativ gibt es noch den nutdrv_qx
Im Protokoll erscheint:
-----------------------------------------------------------
Add-on: Network UPS Tools
Manage battery backup (UPS) devices
-----------------------------------------------------------
Add-on version: 0.13.1
You are running the latest version of this add-on.
System: Home Assistant OS 13.1 (amd64 / qemux86-64)
Home Assistant Core: 2024.9.2
Home Assistant Supervisor: 2024.09.1
-----------------------------------------------------------
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
[10:56:19] INFO: Configuring timezone (Europe/Berlin)...
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
[10:56:19] INFO: Setting mode to netserver...
[10:56:19] INFO: Connected USB devices:
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0665:5161 Cypress Semiconductor USB to Serial
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[10:56:19] INFO: Generating /etc/nut/upsd.users...
[10:56:19] INFO: Configuring user: mkelm
[10:56:19] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[10:56:20] INFO: Configuring Device named DN-170042...
[10:56:20] INFO: Starting the UPS drivers...
libusb1: Could not open any HID devices: insufficient permissions on everything
No supported devices found. Please check your device availability with 'lsusb'
and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'subdriver', 'vendorid' and 'productid'
options specified. Please refer to the man page for details about these options
(man 8 blazer_usb).
Network UPS Tools - Megatec/Q1 protocol USB driver 0.14 (2.8.0)
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
Network UPS Tools - UPS driver controller 2.8.0
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
Vielleicht hat hier jemand einen Tip für mich. Wäre sehr dankbar.
by HarryP: Code-/Logzeilen formatiert (bitte immer in </> einbinden)