Conbee III unresponsive and not flashable

Advice
1

Hi,

since yesterday I’m facing a big problem with my Conbee III. After updating my docker from 2.31.2 to 2.32.5 the conbee III became completely unresponsive after the docker booted. No connection to any device.
So I downgrade to 2.31.2 again but the stick also did not responde.
I replugged it several times and also tried to flash the newest firmware again. The stick and the port is recognized but the firmware update fails everytime. I used GCFFlasher_Win_V4_09_00

GCFFlasher Error

------------------±------------±--------------
COM8 | DExxxxxxx | ConBee III

GCFFlasher -d COM8 -t 60 -f deCONZ_ConBeeIII_0x26550900.bin.GCF
read file success: deCONZ_ConBeeIII_0x26550900.bin.GCF (198814 bytes)
flash firmware
connect \.\COM8, baudrate 115200
command reset timeout
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8

Did anyone had the same Problems before and can give me an advice to fix this?
I tried my backup solution Conbee II i had laying around and after changing the usb path in my docker settings everything was back up.

2

Hello, can you make the try on a real hardware ? (not a docker)

3

i tried to flash it on windows 11 with my computer. the docker running on unraid in my homeserver.

4

So this request was on the PC with win 11 ? And I think deconz is not running on this machine, you have installed only the flasher ?

Your procedure is fine for me, can try that Update deCONZ manually · dresden-elektronik/deconz-rest-plugin Wiki · GitHub

5

That post of @manup from FEB 2024 did the trick for me.
I dont know why but the flasher is not able to start if the Stick is plugged in if you enter the command. it only starts if you put in the stick hit the command unplug the stick and put it back in.

Successful flash

Path | Serial | Type
------------------±------------±--------------
COM8 | DExxxxxxxx | ConBee III

D:\Downloads\GCFFlasher_Win_V4_09_00\GCFFlasher_Win_V4_09_00>GCFFlasher -d COM8 -t 60 -f deCONZ_ConBeeIII_0x26550900.bin.GCF
read file success: deCONZ_ConBeeIII_0x26550900.bin.GCF (198814 bytes)
flash firmware
connect \.\COM8, baudrate 115200
command reset timeout
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
retry connect bootloader COM8
connect \.\COM8, baudrate 115200
query bootloader id V3
query bootloader id V3
query bootloader failed
retry: 39 seconds left
read file success: deCONZ_ConBeeIII_0x26550900.bin.GCF (198814 bytes)
flash firmware
query bootloader id V3
bootloader version 0x00010004, app crc 0xB2D7753C

100% uploading #############################################################
done, wait (up to 20 seconds) for verification
app checksum 0xB2D7753C (OK)
finished

The Web updater for the firmware also doesn’t work for my conbee III. after selecting the device the adress in browser change to /#updatefailed with no percentage and nothing happening.

Updating

The firmware is now being programmed to the ConBee III.

% done.

could this be a general problem?

6

Good question, but another user have solved his issue with your method just today again.

1 Like
7

I just had the idea to put the flashed Conbee III Back into my system - but still no connection with any device.
I started looking at the advance phoscon gateway tab and noticed the zigbee channel was 11. I was pretty sure that i put it on 25 so it seems my stick had locked me out of my own network. I faced this issue before and were pretty sure that there was a Page where you could see and restore the last channel and Network-IDs i started to look it up and i luckly found this post again : Network lost issues · dresden-elektronik/deconz-rest-plugin Wiki that got my Conbee3 settings back working.

8

So the firmware flash have reset your zigbee setting ?

9

i think the firmware was never the problem. it was just my guess because the stick couldn’t be flashed how it was described in the how to. The stick did not connect to the network because the settings for ZIgbeechannel and the id changed after i upgraded the docker version. I don’t know what but something was the cause that this settings did reset.