deconz-rest-plugin: ConBee II cannot connect to deCONZ after its firmware updated
Describe the bug
(originally submitted as #4945, rejected due to non-standard format)
Just purchased a new ConBee II dongle and managed to connect it with latest deCONZ in real linux.
But then tried to upgrade to latest firmware with GCFFlasher_internal from my terminal (debian buster), to resolve issues with some devices, but then it started failling to connect to deCONZ.
I tried the steps described below with and without an extension USB cable.
In all cases, whenver deCONZ tries to connect, i get one line for each “connect” push-button in dmesg:
[ 3739.493704] cdc_acm 1-1:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed
[ 3745.028227] cdc_acm 1-1:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed
...
Occasionally it manages to connect (out of tens of efforts), while fiddling with inserting the dongle and re-connecting, switching off all wireless interfaces (airplane blutooth & wifi), and seems more probable when downgraded to oldest firmware 0x264a0700 (Apr 2019).
Steps to reproduce the behavior
I upgraded with the commands & dmesgs logs are interspersed in time, to explain what happened:
dmesg: plug dongle
[ 2882.716937] usb 1-1: new full-speed USB device number 41 using xhci_hcd
[ 2882.866815] usb 1-1: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[ 2882.866822] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2882.866826] usb 1-1: Product: ConBee II
[ 2882.866829] usb 1-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[ 2882.866832] usb 1-1: SerialNumber: DE2436973
[ 2882.870251] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
console: issue upgrade command
$ sudo GCFFlasher_internal -t 60 -d /dev/ttyACM0 -x 3 -f deCONZ_ConBeeII_0x266b0700.bin.GCF
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
05:15:52:215 using firmware file: deCONZ_ConBeeII_0x266b0700.bin.GCF
05:15:52:253 ls dev: /dev/ttyACM0 (0x1CF1/0x0030) sn: DE2436973
05:15:52:253 pin serialno: DE2436973
05:15:52:253 search FTDI device: no.0
Reboot device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2436973-if00 (ConBee II)
05:15:52:259 query bootloader v1 ID after 5 ms
05:15:52:269 RX 60 bytes ASCII
R21B18 Bootloader
Vers: 2.07
build: Jun 17 2019
, 08:48:53
after 15 ms
05:15:52:269 bootloader start after 15 ms
R21B18 Bootloader
Vers: 2.07
build: Jun 17 2019
05:15:52:270 GCF_ResetDeviceDone
05:15:52:272 bootloader v1 update firmware
flashing 164377 bytes: |==============================|
verify: .
SUCCESS
Wait 10 seconds until application starts
dmesg: issue upgrade command
[ 2893.748615] usb 1-1: USB disconnect, device number 41
[ 2894.136850] usb 1-1: new full-speed USB device number 42 using xhci_hcd
[ 2894.287254] usb 1-1: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[ 2894.287261] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2894.287264] usb 1-1: Product: ConBee II
[ 2894.287267] usb 1-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[ 2894.287270] usb 1-1: SerialNumber: DE2436973
[ 2894.289381] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 2897.683480] usb 1-1: USB disconnect, device number 42
[ 2898.068881] usb 1-1: new full-speed USB device number 43 using xhci_hcd
[ 2898.219125] usb 1-1: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[ 2898.219132] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2898.219136] usb 1-1: Product: ConBee II
[ 2898.219139] usb 1-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[ 2898.219141] usb 1-1: SerialNumber: DE2436973
[ 2898.224274] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
console: Timeout errors begin in upgrade console
Wait 10 seconds until application starts
05:16:10:775 verify application is running
05:16:10:896 failed to query application
05:16:10:896 retry, elapsed 18 seconds
05:16:10:992 parse commands: /usr/bin/GCFFlasher_internal.bin -t 60 -d /dev/ttyACM0 -x 3 -f deCONZ_ConBeeII_0x266b0700.bin.GCF
05:16:10:992 using firmware file: deCONZ_ConBeeII_0x266b0700.bin.GCF
05:16:11:038 ls dev: /dev/ttyACM0 (0x1CF1/0x0030) sn: DE2436973
05:16:11:038 search FTDI device: no.0
Reboot device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2436973-if00 (ConBee II)
05:16:11:039 retry, elapsed 18 seconds
05:16:11:144 parse commands: /usr/bin/GCFFlasher_internal.bin -t 60 -d /dev/ttyACM0 -x 3 -f deCONZ_ConBeeII_0x266b0700.bin.GCF
dmesg: Timeout errors begin in upgrade console
[ 2903.244027] cdc_acm 1-1:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed
[ 2903.396466] cdc_acm 1-1:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed
[ 2903.526440] cdc_acm 1-1:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed
[ 2903.677336] cdc_acm 1-1:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed
[ 2903.820626] cdc_acm 1-1:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed
[ 2903.961555] cdc_acm 1-1:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed
And while the dongle is recognised by the fw-updater:
$ sudo GCFFlasher_internal -l
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Path | Vendor | Product | Serial | Type
-----------------+--------+---------+------------+-------
/dev/ttyACM0 | 0x1CF1 | 0x0030 | DE2436973 | ConBee II
But deCONZ cannot start it, with the same cdc_acm 1-1:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed error.
I then tried to downgrade fw:
dmesg: re-plug to prepare for downgrade
[ 3430.044672] usb 1-1: USB disconnect, device number 43 # unplug
[ 3533.387213] usb 1-1: new full-speed USB device number 44 using xhci_hcd
[ 3533.537066] usb 1-1: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[ 3533.537073] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3533.537077] usb 1-1: Product: ConBee II
[ 3533.537080] usb 1-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[ 3533.537082] usb 1-1: SerialNumber: DE2436973
[ 3533.539259] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
console:
sudo GCFFlasher_internal -t 60 -d /dev/ttyACM0 -x 3 -f /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26680700.bin.GCF
$ sudo GCFFlasher_internal -t 60 -d /dev/ttyACM0 -x 3 -f /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26680700.bin.GCF
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
05:26:42:737 using firmware file: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26680700.bin.GCF
05:26:42:777 ls dev: /dev/ttyACM0 (0x1CF1/0x0030) sn: DE2436973
05:26:42:777 pin serialno: DE2436973
05:26:42:777 search FTDI device: no.0
Reboot device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2436973-if00 (ConBee II)
05:26:42:783 query bootloader v1 ID after 5 ms
05:26:42:794 RX 60 bytes ASCII
R21B18 Bootloader
Vers: 2.07
build: Jun 17 2019
, 08:48:53
after 16 ms
05:26:42:794 bootloader start after 16 ms
R21B18 Bootloader
Vers: 2.07
build: Jun 17 2019
05:26:42:796 GCF_ResetDeviceDone
05:26:42:797 bootloader v1 update firmware
flashing 164373 bytes: |==============================|
verify: .
SUCCESS
Wait 10 seconds until application starts
dmesg:
[ 3544.409071] usb 1-1: USB disconnect, device number 44
[ 3544.799125] usb 1-1: new full-speed USB device number 45 using xhci_hcd
[ 3544.949153] usb 1-1: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[ 3544.949160] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3544.949164] usb 1-1: Product: ConBee II
[ 3544.949167] usb 1-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[ 3544.949169] usb 1-1: SerialNumber: DE2436973
[ 3544.951578] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
# break while upgrading & before rebooting...
[ 3548.340870] usb 1-1: USB disconnect, device number 45
[ 3548.767033] usb 1-1: new full-speed USB device number 46 using xhci_hcd
[ 3548.916954] usb 1-1: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[ 3548.916961] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3548.916965] usb 1-1: Product: ConBee II
[ 3548.916968] usb 1-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[ 3548.916971] usb 1-1: SerialNumber: DE2436973
[ 3548.919176] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
I tried to reset the device, but still the same error on deCONZ connection comes up in dmesg.
Expected behavior
Continue working as before, e.g. connect with deCONZ.
Screenshots
Nope
Environment
- Host system: Debian buster amd64 - deCONZ: 2.11.5
$ uname -a
Linux hostname 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 (2021-04-09) x86_64 GNU/Linux
- Running method: debian buster
- Firmware version:
- don’t remember the original version the dongle came with, listing the versions i tried in the steps to reproduce.
- 0x266b0700
- 0x26680700
- 0x264a0700
- deCONZ version: 2.11.5
- Device:ConBee II
- Do you use an USB extension cable: both yes & no
- Is there any other USB or serial devices connected to the host system? If so: Which?
$ lsusb
Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated Camera (1280x720@30)
Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 003: ID 04f2:b613 Chicony Electronics Co., Ltd Integrated IR Camera
Bus 001 Device 002: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 001 Device 006: ID 2386:432f Raydium Corporation Touch System
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- no zigbee nodes conteccted/resent in the building
deCONZ Logs
see the logs of fw-updater, above, included in the “steps to reproduce”.
lsusb
$ sudo lsusb -vs 46
Bus 001 Device 046: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.01
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1cf1 Dresden Elektronik
idProduct 0x0030 ZigBee gateway [ConBee II]
bcdDevice 1.00
iManufacturer 1 dresden elektronik ingenieurtechnik GmbH
iProduct 2 ConBee II
iSerial 3 DE2436973
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0043
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 0
CDC Header:
bcdCDC 1.10
CDC ACM:
bmCapabilities 0x02
line coding and serial state
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Call Management:
bmCapabilities 0x03
call management
use DataInterface
bDataInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 16
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x000c
bNumDeviceCaps 1
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
HIRD Link Power Management (LPM) Supported
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)
Additional context
Flashing happened in airplane mode, in a desparate effort to stabilize the hw.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 26 (3 by maintainers)
The strangest fact is that ZHA detects its with no problem…
@Mimiix , i wouldn’t classify this issue as a User Question, this is a typical bug report - falling to connect is buggy behavior