deconz-rest-plugin: Conbee II stick crashing USB controller after a couple of hours
With a Conbee II on a Raspberry Pi 4, with no other USB peripherals, the Conbee II always crashes after a couple of hours (from a few minutes to 24+ hours) with the following error:
Feb 4 22:32:45 home kernel: [103786.097031] xhci_hcd 0000:01:00.0: xHCI host not responding to stop endpoint command.
Feb 4 22:32:45 home kernel: [103786.113071] xhci_hcd 0000:01:00.0: Host halt failed, -110
Feb 4 22:32:45 home kernel: [103786.113077] xhci_hcd 0000:01:00.0: xHCI host controller not responding, assume dead
Feb 4 22:32:45 home kernel: [103786.113130] xhci_hcd 0000:01:00.0: HC died; cleaning up
Feb 4 22:32:45 home kernel: [103786.113219] usb 1-1: USB disconnect, device number 2
Feb 4 22:32:45 home kernel: [103786.113227] usb 1-1.4: USB disconnect, device number 35
Feb 4 22:32:45 home kernel: [103786.113234] usb 1-1.4.1: USB disconnect, device number 37
Feb 4 22:32:45 home kernel: [103786.113379] cdc_acm 1-1.4.1:1.0: failed to set dtr/rts
The device disappears from the USB bus afterwards. Rebooting the RPi 4 puts it back online again. When this happens, no error is raised with power supply or throttling (vcgencmd get_throttled returns 0x0).
Conbee II info: Version Version: 2.05.72 / 12/12/2019 Firmware version: 264A0700. / “This version is up to date”
I have tried with multiple USB2.0 or USB3.0 extension cables, putting a USB2.0 hub on the RPi4 side, or at the end of the extension cable, same result everytime.
If this a known problem on this firmware version? Anything I could try to improve reliability?
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (2 by maintainers)
Small update on this, I’m currently digging in the ConBee II firmware usb code. One thing I’ve noticed is that Linux does send MTP probes and the Modem Manager might also dig into the serial communication when the device is plugged in and after an reboot.
This can be disabled by following udev rules (will be included and installed automatically in the next releases)
After creating this file the udev rules needs to be reloaded:
This is not a silver bullet for all issues but should help to prevent triggering unwanted states in the firmware.
Can you make a try with a windows machine ? There is some users with the same problem and on windows you can see the device making a connected/disconnect loop (with the sound)
@elafargue and others: I’ve got alerted that the latest firmware update should resolve the crashing. Are you able to update your devices? Follow this guide to do so 😃
Same on my side: Version Version: 2.05.72 / 12/12/2019 Firmware version: 264A0700
On win no errors accurs.