Permanent reconnect UPS Powercom

L

lirtm

New Member
Nov 11, 2022
7
0
1
Good day. Only recently, Proxmox for home use has discovered for himself. Smart House based on HA and all that. But there was a problem with the connection of the UPS Powercom WOW-700U
I find a similar topic on the forum, but my problem is somewhat different.
Judging by the output of dmesg -w, the UPS is determined, but after USB it independently disconnected.
Because of this, it is impossible to configure any power monitoring system.

UPS is USB 1-1.
Dmesg:
Code: 
Nov 11 17:34:59 proxmox kernel: usb 1-1: new low-speed USB device number 118 using xhci_hcd
Nov 11 17:34:59 proxmox kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Nov 11 17:34:59 proxmox kernel: usb 1-1: New USB device found, idVendor=0d9f, idProduct=0004, bcdDevice= 0.02
Nov 11 17:34:59 proxmox kernel: usb 1-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Nov 11 17:34:59 proxmox kernel: usb 1-1: Product: HID UPS Battery
Nov 11 17:34:59 proxmox kernel: usb 1-1: Manufacturer: POWERCOM Co.,LTD
Nov 11 17:34:59 proxmox kernel: usb 1-1: SerialNumber: 004-0D9F-000
Nov 11 17:34:59 proxmox kernel: hid-generic 0003:0D9F:0004.0141: hiddev1,hidraw3: USB HID v1.00 Device [POWERCOM Co.,LTD HID UPS Battery] on usb-0000:00:14.0-1/input0
Nov 11 17:34:59 proxmox kernel: usb 1-8: USB disconnect, device number 117
Nov 11 17:35:02 proxmox systemd[1]: systemd-rfkill.service: Succeeded.
Nov 11 17:35:07 proxmox systemd[579694]: Stopped target Bluetooth.
Nov 11 17:35:07 proxmox kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Nov 11 17:35:07 proxmox systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 11 17:35:07 proxmox systemd[1]: Stopped target Bluetooth.
Nov 11 17:35:07 proxmox systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 11 17:35:07 proxmox kernel: usb 1-8: new full-speed USB device number 119 using xhci_hcd
Nov 11 17:35:08 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:08 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:08 proxmox kernel: usb 1-8: new full-speed USB device number 120 using xhci_hcd
Nov 11 17:35:08 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:08 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:08 proxmox kernel: usb usb1-port8: attempt power cycle
Nov 11 17:35:09 proxmox kernel: usb 1-8: new full-speed USB device number 121 using xhci_hcd
Nov 11 17:35:09 proxmox kernel: usb 1-8: New USB device found, idVendor=8087, idProduct=0a2a, bcdDevice= 0.01
Nov 11 17:35:09 proxmox kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 11 17:35:09 proxmox kernel: usb 1-1: USB disconnect, device number 118
Nov 11 17:35:09 proxmox systemd[579694]: Reached target Bluetooth.
Nov 11 17:35:09 proxmox systemd[1]: Reached target Bluetooth.
Nov 11 17:35:11 proxmox kernel: usb 1-8: USB disconnect, device number 121
Nov 11 17:35:11 proxmox kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Nov 11 17:35:14 proxmox systemd[1]: systemd-rfkill.service: Succeeded.
Nov 11 17:35:19 proxmox systemd[579694]: Stopped target Bluetooth.
Nov 11 17:35:19 proxmox kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Nov 11 17:35:19 proxmox systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 11 17:35:19 proxmox systemd[1]: Stopped target Bluetooth.
Nov 11 17:35:19 proxmox systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 11 17:35:20 proxmox kernel: usb 1-8: new full-speed USB device number 122 using xhci_hcd
Nov 11 17:35:20 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:20 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:20 proxmox kernel: usb 1-8: new full-speed USB device number 123 using xhci_hcd
Nov 11 17:35:20 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:21 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:21 proxmox kernel: usb usb1-port8: attempt power cycle
Nov 11 17:35:22 proxmox kernel: usb 1-8: new full-speed USB device number 124 using xhci_hcd
Nov 11 17:35:22 proxmox kernel: usb 1-8: New USB device found, idVendor=8087, idProduct=0a2a, bcdDevice= 0.01
Nov 11 17:35:22 proxmox kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 11 17:35:22 proxmox systemd[1]: Reached target Bluetooth.
Nov 11 17:35:22 proxmox systemd[579694]: Reached target Bluetooth.
Nov 11 17:35:24 proxmox kernel: usb 1-1: new low-speed USB device number 125 using xhci_hcd
Nov 11 17:35:24 proxmox kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Nov 11 17:35:24 proxmox kernel: usb 1-1: New USB device found, idVendor=0d9f, idProduct=0004, bcdDevice= 0.02
Nov 11 17:35:24 proxmox kernel: usb 1-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Nov 11 17:35:24 proxmox kernel: usb 1-1: Product: HID UPS Battery
Nov 11 17:35:24 proxmox kernel: usb 1-1: Manufacturer: POWERCOM Co.,LTD
Nov 11 17:35:24 proxmox kernel: usb 1-1: SerialNumber: 004-0D9F-000
Nov 11 17:35:24 proxmox kernel: hid-generic 0003:0D9F:0004.0142: hiddev1,hidraw3: USB HID v1.00 Device [POWERCOM Co.,LTD HID UPS Battery] on usb-0000:00:14.0-1/input0
Nov 11 17:35:24 proxmox kernel: usb 1-8: USB disconnect, device number 124
Nov 11 17:35:27 proxmox systemd[1]: systemd-rfkill.service: Succeeded.
Nov 11 17:35:32 proxmox systemd[579694]: Stopped target Bluetooth.
Nov 11 17:35:32 proxmox kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Nov 11 17:35:32 proxmox systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 11 17:35:32 proxmox systemd[1]: Stopped target Bluetooth.
Nov 11 17:35:32 proxmox systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 11 17:35:32 proxmox kernel: usb 1-8: new full-speed USB device number 126 using xhci_hcd
Nov 11 17:35:32 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:32 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:33 proxmox kernel: usb 1-8: new full-speed USB device number 127 using xhci_hcd
Nov 11 17:35:33 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:33 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:33 proxmox kernel: usb usb1-port8: attempt power cycle
Nov 11 17:35:34 proxmox kernel: usb 1-8: new full-speed USB device number 4 using xhci_hcd
Nov 11 17:35:34 proxmox kernel: usb 1-8: New USB device found, idVendor=8087, idProduct=0a2a, bcdDevice= 0.01
Nov 11 17:35:34 proxmox kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 11 17:35:34 proxmox kernel: usb 1-1: USB disconnect, device number 125

Proxmox works on a mini-PC Beelink on Pentium N5095U.


If you need any other information, I will provide.
 
Is your CPU load maybe too high (load >= CPU cores)? Got a similar problem here where NUT can't poll the UPS data in time when load spikes are hitting the CPU. And the only option to recover from that locked UPS state is to restart the UPS driver.
 
Dunuin said:
Is your CPU load maybe too high (load >= CPU cores)? Got a similar problem here where NUT can't poll the UPS data in time when load spikes are hitting the CPU. And the only option to recover from that locked UPS state is to restart the UPS driver.
Click to expand...
This happens even without NUT. I just interrogate through lsusb - and there is no UPS in the list.
CPU Load — absolutely not. The load at the time of the problem did not exceed 2%.
 

Attachments

  • 2022-11-11_222825.png
    2022-11-11_222825.png
    64.8 KB · Views: 4
lirtm said:
Good day. Only recently, Proxmox for home use has discovered for himself. Smart House based on HA and all that. But there was a problem with the connection of the UPS Powercom WOW-700U
I find a similar topic on the forum, but my problem is somewhat different.
Judging by the output of dmesg -w, the UPS is determined, but after USB it independently disconnected.
Because of this, it is impossible to configure any power monitoring system.

UPS is USB 1-1.
Dmesg:
Code: 
Nov 11 17:34:59 proxmox kernel: usb 1-1: new low-speed USB device number 118 using xhci_hcd
Nov 11 17:34:59 proxmox kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Nov 11 17:34:59 proxmox kernel: usb 1-1: New USB device found, idVendor=0d9f, idProduct=0004, bcdDevice= 0.02
Nov 11 17:34:59 proxmox kernel: usb 1-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Nov 11 17:34:59 proxmox kernel: usb 1-1: Product: HID UPS Battery
Nov 11 17:34:59 proxmox kernel: usb 1-1: Manufacturer: POWERCOM Co.,LTD
Nov 11 17:34:59 proxmox kernel: usb 1-1: SerialNumber: 004-0D9F-000
Nov 11 17:34:59 proxmox kernel: hid-generic 0003:0D9F:0004.0141: hiddev1,hidraw3: USB HID v1.00 Device [POWERCOM Co.,LTD HID UPS Battery] on usb-0000:00:14.0-1/input0
Nov 11 17:34:59 proxmox kernel: usb 1-8: USB disconnect, device number 117
Nov 11 17:35:02 proxmox systemd[1]: systemd-rfkill.service: Succeeded.
Nov 11 17:35:07 proxmox systemd[579694]: Stopped target Bluetooth.
Nov 11 17:35:07 proxmox kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Nov 11 17:35:07 proxmox systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 11 17:35:07 proxmox systemd[1]: Stopped target Bluetooth.
Nov 11 17:35:07 proxmox systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 11 17:35:07 proxmox kernel: usb 1-8: new full-speed USB device number 119 using xhci_hcd
Nov 11 17:35:08 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:08 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:08 proxmox kernel: usb 1-8: new full-speed USB device number 120 using xhci_hcd
Nov 11 17:35:08 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:08 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:08 proxmox kernel: usb usb1-port8: attempt power cycle
Nov 11 17:35:09 proxmox kernel: usb 1-8: new full-speed USB device number 121 using xhci_hcd
Nov 11 17:35:09 proxmox kernel: usb 1-8: New USB device found, idVendor=8087, idProduct=0a2a, bcdDevice= 0.01
Nov 11 17:35:09 proxmox kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 11 17:35:09 proxmox kernel: usb 1-1: USB disconnect, device number 118
Nov 11 17:35:09 proxmox systemd[579694]: Reached target Bluetooth.
Nov 11 17:35:09 proxmox systemd[1]: Reached target Bluetooth.
Nov 11 17:35:11 proxmox kernel: usb 1-8: USB disconnect, device number 121
Nov 11 17:35:11 proxmox kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Nov 11 17:35:14 proxmox systemd[1]: systemd-rfkill.service: Succeeded.
Nov 11 17:35:19 proxmox systemd[579694]: Stopped target Bluetooth.
Nov 11 17:35:19 proxmox kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Nov 11 17:35:19 proxmox systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 11 17:35:19 proxmox systemd[1]: Stopped target Bluetooth.
Nov 11 17:35:19 proxmox systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 11 17:35:20 proxmox kernel: usb 1-8: new full-speed USB device number 122 using xhci_hcd
Nov 11 17:35:20 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:20 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:20 proxmox kernel: usb 1-8: new full-speed USB device number 123 using xhci_hcd
Nov 11 17:35:20 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:21 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:21 proxmox kernel: usb usb1-port8: attempt power cycle
Nov 11 17:35:22 proxmox kernel: usb 1-8: new full-speed USB device number 124 using xhci_hcd
Nov 11 17:35:22 proxmox kernel: usb 1-8: New USB device found, idVendor=8087, idProduct=0a2a, bcdDevice= 0.01
Nov 11 17:35:22 proxmox kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 11 17:35:22 proxmox systemd[1]: Reached target Bluetooth.
Nov 11 17:35:22 proxmox systemd[579694]: Reached target Bluetooth.
Nov 11 17:35:24 proxmox kernel: usb 1-1: new low-speed USB device number 125 using xhci_hcd
Nov 11 17:35:24 proxmox kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Nov 11 17:35:24 proxmox kernel: usb 1-1: New USB device found, idVendor=0d9f, idProduct=0004, bcdDevice= 0.02
Nov 11 17:35:24 proxmox kernel: usb 1-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Nov 11 17:35:24 proxmox kernel: usb 1-1: Product: HID UPS Battery
Nov 11 17:35:24 proxmox kernel: usb 1-1: Manufacturer: POWERCOM Co.,LTD
Nov 11 17:35:24 proxmox kernel: usb 1-1: SerialNumber: 004-0D9F-000
Nov 11 17:35:24 proxmox kernel: hid-generic 0003:0D9F:0004.0142: hiddev1,hidraw3: USB HID v1.00 Device [POWERCOM Co.,LTD HID UPS Battery] on usb-0000:00:14.0-1/input0
Nov 11 17:35:24 proxmox kernel: usb 1-8: USB disconnect, device number 124
Nov 11 17:35:27 proxmox systemd[1]: systemd-rfkill.service: Succeeded.
Nov 11 17:35:32 proxmox systemd[579694]: Stopped target Bluetooth.
Nov 11 17:35:32 proxmox kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Nov 11 17:35:32 proxmox systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 11 17:35:32 proxmox systemd[1]: Stopped target Bluetooth.
Nov 11 17:35:32 proxmox systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 11 17:35:32 proxmox kernel: usb 1-8: new full-speed USB device number 126 using xhci_hcd
Nov 11 17:35:32 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:32 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:33 proxmox kernel: usb 1-8: new full-speed USB device number 127 using xhci_hcd
Nov 11 17:35:33 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:33 proxmox kernel: usb 1-8: device descriptor read/64, error -71
Nov 11 17:35:33 proxmox kernel: usb usb1-port8: attempt power cycle
Nov 11 17:35:34 proxmox kernel: usb 1-8: new full-speed USB device number 4 using xhci_hcd
Nov 11 17:35:34 proxmox kernel: usb 1-8: New USB device found, idVendor=8087, idProduct=0a2a, bcdDevice= 0.01
Nov 11 17:35:34 proxmox kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 11 17:35:34 proxmox kernel: usb 1-1: USB disconnect, device number 125

Proxmox works on a mini-PC Beelink on Pentium N5095U.


If you need any other information, I will provide.
Click to expand...
hello. were you able to defeat it? absoluttelly same with WOW 500U


1678469192996.png
 
smokepeng said:
You need to create a new rule for UDEV, then reconnect the USB from the UPS, restart the nut server, or restart the computer altogether. I have already provided links to the solution of this problem. It worked for me on several different POWERCOM UPSs.

https://serverfault.com/questions/9...ups-repeatedly-disconnecting-and-reconnecting
https://alioth-lists.debian.net/pipermail/nut-upsuser/2019-June/011451.html
Click to expand...
It's true... I didn't recognize the solution from the links at the time.
Now it's okay, just yesterday I was looking hard for a solution. And it's been here for a long time.

In general, now there are no dumps, set up on the Proxmox server and connected to it in the Home Assistant.
 
lirtm said:
but U can?
Click to expand...
Fixed after i edit /etc/nut/ups.conf:
Code: 
pollinterval = 10
maxretry = 3

[powercom]
driver = usbhid-ups
port = auto
pollonly
vendorid = 0d9f
productid = 0004
serial = 004-0D9F-000
desc = "Powercom WOW-500U"
ignorelb
override.battery.charge.low = 25
last two not neccessary

All info aquired by nut-scanner -U. Don't forget to reboot PVE.
 
Last edited:
  • Like
Reactions: lirtm
Nuke said:
Fixed after i edit /etc/nut/ups.conf:
Code: 
pollinterval = 10
maxretry = 3

[powercom]
driver = usbhid-ups
port = auto
pollonly
vendorid = 0d9f
productid = 0004
serial = 004-0D9F-000
desc = "Powercom WOW-500U"
ignorelb
override.battery.charge.low = 25
last two not neccessary

All info aquired by nut-scanner -U. Don't forget to reboot PVE.
Click to expand...
Thanks!!!

But I already did. Just the problem was in udev and the old kernel (most likely in udev). I did the rest of the setup and everything is fine, in Home Assistant everything is flashed through the integration.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back