Powercom WOW-500U, Proxmox and NUT add-on #299

lirtm · 2023-05-29T13:37:49Z

lirtm
May 29, 2023

Hello. A few days fiddled with the ability to monitor this UPS in these systems.
At first, the UPS in Proxmox just reconnected. Updating the Proxmox kernel to 6.2 and adding a line

# Powercom
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="0d9f", ATTR{idProduct}=="0004", MODE="0660", GROUP="nut"

in etc/udev/rules.d/90-nut-ups.rules
And the UPS is almost stably connected. I add it in Home Assistant via Add-USB in Proxmox and selected UPS there - I also have HAOS installed on Proxmox.
Next, I tried to set it up using this video — https://www.youtube.com/watch?v=bTwr26n60qs

In HA UPS added, in the equipment it looks like this:

BUSNUM: '002'
DEVNAME: /dev/bus/usb/002/005
DEVNUM: '005'
DEVPATH: /devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-2
DEVTYPE: usb_device
DRIVER: usb
ID_BUS: usb
ID_FOR_SEAT: usb-pci-0000_01_1b_0-usb-0_2
ID_MODEL: HID_UPS_Battery
ID_MODEL_ENC: HID\x20UPS\x20Battery
ID_MODEL_ID: '0004'
ID_PATH: pci-0000:01:1b.0-usb-0:2
ID_PATH_TAG: pci-0000_01_1b_0-usb-0_2
ID_REVISION: '0002'
ID_SERIAL: POWERCOM_Co._LTD_HID_UPS_Battery_004-0D9F-000
ID_SERIAL_SHORT: 004-0D9F-000
ID_USB_INTERFACES: ':030000:'
ID_USB_MODEL: HID_UPS_Battery
ID_USB_MODEL_ENC: HID\x20UPS\x20Battery
ID_USB_MODEL_ID: '0004'
ID_USB_REVISION: '0002'
ID_USB_SERIAL: POWERCOM_Co._LTD_HID_UPS_Battery_004-0D9F-000
ID_USB_SERIAL_SHORT: 004-0D9F-000
ID_USB_VENDOR: POWERCOM_Co._LTD
ID_USB_VENDOR_ENC: POWERCOM\x20Co.\x2cLTD
ID_USB_VENDOR_ID: 0d9f
ID_VENDOR: POWERCOM_Co._LTD
ID_VENDOR_ENC: POWERCOM\x20Co.\x2cLTD
ID_VENDOR_ID: 0d9f
MAJOR: '189'
MINOR: '132'
PRODUCT: d9f/4/2
SUBSYSTEM: usb
TAGS: ':seat:'
TYPE: 0/0/0
USEC_INITIALIZED: '8281192936'

In the addon I specify in the configuration like this:

users:
  - username: upsadmin
    password: UPSPASS
    instcmds:
      - all
    actions: []
devices:
  - name: nutdev1
    driver: usbhid-ups
    port: /devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-2
    config:
      - vendorid = "0D9F"
      - productid = "0004"
mode: netserver
shutdown_host: false
list_usb_devices: true

But in the logs I see the following:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/nut.sh
[16:32:31] INFO: Setting mode to netserver...
[16:32:31] INFO: Connected USB devices:
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 0d9f:0004 Powercom Co., Ltd HID UPS Battery
Bus 002 Device 002: ID 0bda:a725 Realtek Semiconductor Corp. Bluetooth 5.1 Radio
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
[16:32:31] INFO: Generating /etc/nut/upsd.users...
[16:32:31] INFO: Configuring user: upsadmin
[16:32:32] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[16:32:32] INFO: Configuring Device named nutdev1...
[16:32:32] INFO: Starting the UPS drivers...
No matching HID UPS found
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
Network UPS Tools - UPS driver controller 2.7.4
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 fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

If I change the driver to "powercom", the log looks like this:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/nut.sh
[16:34:29] INFO: Setting mode to netserver...
[16:34:29] INFO: Connected USB devices:
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 0d9f:0004 Powercom Co., Ltd HID UPS Battery
Bus 002 Device 002: ID 0bda:a725 Realtek Semiconductor Corp. Bluetooth 5.1 Radio
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
[16:34:29] INFO: Generating /etc/nut/upsd.users...
[16:34:30] INFO: Configuring user: upsadmin
[16:34:30] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[16:34:30] INFO: Configuring Device named nutdev1...
[16:34:30] INFO: Starting the UPS drivers...
Network UPS Tools - PowerCom protocol UPS driver 0.17 (2.7.4)
Fatal error: 'vendorid' is not a valid variable name for this driver.
Look in the man page or call this driver with -h for a list of
valid variable names and flags.
Network UPS Tools - UPS driver controller 2.7.4
cont-init: info: /etc/cont-init.d/nut.sh exited 0
cont-init: info: running /etc/cont-init.d/nutclient.sh
cont-init: info: /etc/cont-init.d/nutclient.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun upsd (no readiness notification)
services-up: info: copying legacy longrun upsmon (no readiness notification)
[16:34:30] INFO: Starting the UPS information server...
   0.000000	fopen /run/nut/upsd.pid: No such file or directory
   0.001015	listening on 0.0.0.0 port 3493
s6-rc: info: service legacy-services successfully started
   0.002657	Can't connect to UPS [nutdev1] (powercom-nutdev1): No such file or directory
[16:34:31] INFO: Starting the UPS monitor and shutdown controller...
   0.000000	fopen /run/nut/upsmon.pid: No such file or directory
   0.000302	Using power down flag file /etc/killpower
   0.000390	UPS: nutdev1@localhost (master) (power value 1)
   0.000431	debug level is '1'
   0.000437	Warning: running as one big root process by request (upsmon -p)
   0.000624	Init SSL without certificate database
   0.002102	Trying to connect to UPS [nutdev1@localhost]
   0.512179	User [email protected] logged into UPS [nutdev1]
   0.003300	Logged into UPS nutdev1@localhost
   0.003552	Poll UPS [nutdev1@localhost] failed - Driver not connected
{"message":"Event nut.ups_event fired."}Network UPS Tools upsmon 2.7.4
   5.004187	Poll UPS [nutdev1@localhost] failed - Driver not connected
{"message":"Event nut.ups_event fired."}Network UPS Tools upsmon 2.7.4
  10.004777	Poll UPS [nutdev1@localhost] failed - Driver not connected
  15.005110	Poll UPS [nutdev1@localhost] failed - Driver not connected
  20.005742	Poll UPS [nutdev1@localhost] failed - Driver not connected
  25.006368	Poll UPS [nutdev1@localhost] failed - Driver not connected
  30.006977	Poll UPS [nutdev1@localhost] failed - Driver not connected

If I return the config section to the standard blank, then:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/nut.sh
[16:36:40] INFO: Setting mode to netserver...
[16:36:40] INFO: Connected USB devices:
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 0d9f:0004 Powercom Co., Ltd HID UPS Battery
Bus 002 Device 002: ID 0bda:a725 Realtek Semiconductor Corp. Bluetooth 5.1 Radio
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
[16:36:40] INFO: Generating /etc/nut/upsd.users...
[16:36:40] INFO: Configuring user: upsadmin
[16:36:40] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[16:36:41] INFO: Configuring Device named nutdev1...
[16:36:41] INFO: Starting the UPS drivers...
Fatal error: unusable configuration
Network UPS Tools - PowerCom protocol UPS driver 0.17 (2.7.4)
Unable to open /devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-2: No such file or directory
Things to try:
 - Check 'port=' in ups.conf
 - Check owner/permissions of all parts of path
Network UPS Tools - UPS driver controller 2.7.4
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 fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Can you tell me where I'm "going wrong"? It's like everything is right, but it's like everything is not right.

Big THANKS!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Powercom WOW-500U, Proxmox and NUT add-on #299

{{title}}

Replies: 0 comments

Select a reply

Powercom WOW-500U, Proxmox and NUT add-on #299

lirtm May 29, 2023

Replies: 0 comments

lirtm
May 29, 2023