deconz-rest-plugin: Conbee II - endless connecting/disconnecting loop on USB level
Not sure if this is the right place to report Conbee II specific issues which are not directly related to deCONZ itself, but I give it try…
In my case I’m running Hassio as VM within Proxmox on an Intel Nuc with an attached Conbee II USB stick. This setup runs over month w/o any problems. But out of nowhere since some days I discovered the following statements in the Syslog. The Conbee II stick seems to be have trouble on USB level and sticks into a endless connecting/disconnecting loop.
As I did no changes on hardware level (e.g. no firmware updates, no other USB devices, …) my first idea was the stick is somehow technically broken. But looking to the issue list (e.g. #1598, #3000) it seems others have similar problems.
Unfortunately I wasn’t able to find an answer on what causes the problem or how to fix it and would be appreciated for any help.
[...]
Jul 01 01:47:27 pve kernel: usb 1-3: USB disconnect, device number 74
Jul 01 01:47:27 pve kernel: usb 1-3: new full-speed USB device number 75 using xhci_hcd
Jul 01 01:47:32 pve kernel: usb 1-3: unable to read config index 0 descriptor/all
Jul 01 01:47:32 pve kernel: usb 1-3: can't read configurations, error -110
Jul 01 01:47:32 pve kernel: usb 1-3: new full-speed USB device number 76 using xhci_hcd
Jul 01 01:47:33 pve kernel: usb 1-3: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
Jul 01 01:47:33 pve kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 01 01:47:33 pve kernel: usb 1-3: Product: ConBee II
Jul 01 01:47:33 pve kernel: usb 1-3: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Jul 01 01:47:33 pve kernel: usb 1-3: SerialNumber: DE1964774
Jul 01 01:47:33 pve kernel: cdc_acm 1-3:1.0: ttyACM0: USB ACM device
Jul 01 01:47:54 pve kernel: usb 1-3: USB disconnect, device number 76
Jul 01 01:47:54 pve kernel: usb 1-3: new full-speed USB device number 77 using xhci_hcd
Jul 01 01:47:54 pve kernel: usb 1-3: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
Jul 01 01:47:54 pve kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 01 01:47:54 pve kernel: usb 1-3: Product: ConBee II
Jul 01 01:47:54 pve kernel: usb 1-3: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Jul 01 01:47:54 pve kernel: usb 1-3: SerialNumber: DE1964774
Jul 01 01:47:54 pve kernel: cdc_acm 1-3:1.0: ttyACM0: USB ACM device
[...]
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 48
I have same problem on Esxi, endless connect-disconnect.
I know this is an old issue, but since this is one of the top search results, I wanted to add that the method above worked perfectly for me.
I got my new Conbee II today. It worked fine, then I updated the firmware, then it got stuck in a connect-disconnect loop. The fw-update was done through the phoscon web app.
If I plugged it into a USB port on windows, I got the de-do-di (connected) and de-du-do (disconnected) every few seconds.
I opened device manager and saw that under
Ports, the COM5 was connecting/disconnecting.Then I downloaded the second-latest firmware from http://deconz.dresden-elektronik.de/deconz-firmware/?C=M;O=D.
Running
GCFFlasher -d COM5 -t 60 -f ./deCONZ_ConBeeII_0x26700700.bin.GCFworked. It waited a few seconds for the next connect, and then successfully flashed it.Important: You need to check which COM port number it is on your local computer and change the cli arguments to that.
Great - got a little nervous there. 😉
An update from my side: As i continued to see the reconnect-loop I googled a bit further and found a post over at Proxmox stating that others where having the same issue and that one resolution was to downgrade the Proxmox version.
I have now downgraded it (and all the vm’s are still running - phew), and now I have added the usb port to HA again and from the looks of things it works. There are no usb traces in the logs aside from the reset that happens when the vm boots, so fingers crossed that this issue is resolved. 😃
Thank you kindly for your insights and comments.
For continuity I am including the link to the proxmox forum where I found the solution for how to downgrade: https://forum.proxmox.com/threads/usb-drive-crashes-vm.70214/
Well, we are back to square one:
This is really not very good. How can we mitigate this?
@SwoopX I’m up to an experiment. Let’s try.
On Windows the stick initially shows the same behavior (continuous registering and deregister as COM device) but nevertheless deConz as well as GCFFlasher were able to pick up the device. This gave me the change to update to the latest firmware version (0x26580700) but with this deConz wasn’t able to establish a connection to Conbee anymore. So I started a 2nd try by using the previous firmware version (0x26570700) which does the trick and the stick now is back to life. I’ve still no idea what causes this problem, but as everything is now back to normal I will close this issue.