deconz-rest-plugin: Conbee II not connected with after firmware update with deCONZ_ConBeeII_0x26490700.bin.GCF

Hi! I am new to Conbee and i think, something went wrong when I updated the firmware.

I am running debian stretch (proxmox vm) and have successfully installed deCONZ/phoscon (minimal/headless) and was able to add some lights, switches and sensors.

I then found the “Manual update Instructions”-Site for the manual firmware update procedure and I couldn’t resist to try updating the stick. I followed the instructions with the firmware version mentioned in the topic (GCFFlasher_internal -d /dev/ttyAMC0 -f deCONZ_ConBeeII_0x26490700.bin.GCF). The GCFFlasher-Tool ended with “success”. But: Since then the stick appears to be not connected in the phoscon app. I cannot switch lights (they disappeared) and my sensors are shown as not being reachable. This is what I have tried to get things better: I unplugged the stick and plugged it in again. I powered off the whole machine and restartet it (with stick plugged in during boot up and without). No luck. I set up a new vm with ubuntu and installed deCONZ. On the start screen of deCONZ the stick is beeing displayed but I cannot connect.

Unfortunately I also get some weird output of dmesg: [ 12.045167] usb 4-1: New USB device found, idVendor=1cf1, idProduct=0030 [ 12.045169] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 12.045171] usb 4-1: Product: ConBee II [ 12.045172] usb 4-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH [ 12.045173] usb 4-1: SerialNumber: DE1964192 [ 12.054672] cdc_acm 4-1:1.0: ttyACM0: USB ACM device [ 12.056991] usbcore: registered new interface driver cdc_acm [ 12.056992] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 20.590858] Bluetooth: Core ver 2.22 [ 20.590875] NET: Registered protocol family 31 [ 20.590876] Bluetooth: HCI device and connection manager initialized [ 20.590880] Bluetooth: HCI socket layer initialized [ 20.590882] Bluetooth: L2CAP socket layer initialized [ 20.590891] Bluetooth: SCO socket layer initialized [ 39.627194] cdc_acm 4-1:1.0: failed to set dtr/rts [ 39.641753] cdc_acm 4-1:1.0: failed to set dtr/rts [ 39.803951] usb 4-1: USB disconnect, device number 3 [ 39.804919] cdc_acm 4-1:1.0: failed to set dtr/rts [ 42.559674] usb 4-1: new full-speed USB device number 4 using uhci_hcd [ 43.007901] usb 4-1: New USB device found, idVendor=1cf1, idProduct=0030 [ 43.007903] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 43.007904] usb 4-1: Product: ConBee II [ 43.007905] usb 4-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH [ 43.007906] usb 4-1: SerialNumber: DE1964192 [ 43.010383] cdc_acm 4-1:1.0: ttyACM1: USB ACM device [ 68.507696] cdc_acm 4-1:1.0: failed to set dtr/rts [ 68.572214] usb 4-1: USB disconnect, device number 4 [ 71.432066] usb 4-1: new full-speed USB device number 5 using uhci_hcd [ 71.881510] usb 4-1: New USB device found, idVendor=1cf1, idProduct=0030 [ 71.881512] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 71.881513] usb 4-1: Product: ConBee II [ 71.881514] usb 4-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH [ 71.881515] usb 4-1: SerialNumber: DE1964192 [ 71.883992] cdc_acm 4-1:1.0: ttyACM0: USB ACM device [ 91.503889] cdc_acm 4-1:1.0: failed to set dtr/rts [ 91.636292] usb 4-1: USB disconnect, device number 5

showing me, that the stick is initially recognized but somehow disconnects again.

GCFFlasher_internal -l first gives me: GCFFlasher V3_03 (c) dresden elektronik ingenieurtechnik gmbh Path | Vendor | Product | Serial | Type -----------------+--------+---------+------------+------- /dev/ttyACM0 | 0x1CF1 | 0x0030 | DE1964192 | ConBee II

But after some time the stick disappears: GCFFlasher V3_03 (c) dresden elektronik ingenieurtechnik gmbh Path | Vendor | Product | Serial | Type -----------------+--------+---------+------------+-------

I guess I did not flash a wrong firmware since the file name indicates to be right (“deCONZ_ConBeeII_xxx”) and since the GCFFlasher told me that the update was successful, I believe the update process didn’t went wrong.

Is there anything else I can try?

Thanks in advance!