Sonoff Zigbee Bridge Pro, Problems with Firmwareupgrade on Berry Console

[Patrix2911]

Hello. First of all, I hope I’m posting in the correct forum. I purchased a Sonoff Zigbee Pro Bridge and flashed it according to this guide (https://notenoughtech.com/home-automation/tasmota-on-sonoff-zb-bridge-pro/#google_vignette). The installed Version is tasmota 14.5.0 I’ve reached the ‘cc.flash’ point in the Berry console, but I’m getting the following error:

FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
stack traceback:
: in function flash
: in function main

I’ve tried with the file ‘SonoffZBPro_coord_20220219.hex’ and also with ‘SonoffZBPro_coord_20240710.hex’. Unfortunately, I keep getting the same error. I’m not very experienced with this, so could someone please help me?

Thank you very much, Patrick.

[s-hadinger]

Can you please provide the full log, not just the error?

[sidorovit]

00:00:00.002 HDW: ESP32-D0WD-V3 v3.1 (PSRAM)
00:00:00.081 UFS: FlashFS mounted with 800 kB free
00:00:00.098 CFG: Loaded from File, Count 12
00:00:00.106 QPC: Count 1
00:00:00.110 I2C: Bus1 using GPIO26(SCL) and GPIO25(SDA)
00:00:00.163 BRY: Berry initialized, RAM used 3516 bytes
00:00:00.204 Project tasmota - Tasmota Version 14.5.0(release-zbbrdgpro)-3_1_1(2025-02-18T14:37:02)
00:00:00.205 ZIG: Loading Zigbee data
00:00:00.211 ZIG: No Zigbee device information
00:00:00.215 ZIG: No Zigbee device data
00:00:00.216 ZIG: ZbLoad '<internal_plugin>' loaded successfully
00:00:01.135 WIF: Connecting to AP1 Dachniki-2 Channel 1 BSSId 2C:C8:1B:4B:97:61 in mode 11g as tasmota-6BB3CC-5068...
00:00:03.712 WIF: Connected
10:07:59.012 HTP: Web server active on tasmota-6BB3CC-5068 with IP address 192.168.0.121
10:07:59.808 RSL: INFO1 = {"Info1":{"Module":"Sonoff Zigbee Pro","Version":"14.5.0(release-zbbrdgpro)","FallbackTopic":"cmnd/DVES_6BB3CC_fb/","GroupTopic":"cmnd/tasmotas/"}}
10:08:00.011 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-6BB3CC-5068","IPAddress":"192.168.0.121","IP6Global":"","IP6Local":"fe80::8a13:bfff:fe6b:b3cc%st1"}}
10:08:00.023 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":4}}
10:08:02.903 QPC: Reset
10:08:04.885 RSL: STATE = {"Time":"2025-03-02T10:08:04","Uptime":"0T00:00:09","UptimeSec":9,"Heap":173,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":45},"Wifi":{"AP":1,"SSId":"Dachniki-2","BSSId":"2C:C8:1B:4B:97:61","Channel":1,"Mode":"11g","RSSI":94,"Signal":-53,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:08:10.601 ZIG: rebooting ZNP device
10:08:12.404 RSL: RESULT = {"ZbState":{"Status":1,"Message":"CCxxxx ZNP booted","RestartReason":"Power-up","MajorRel":2,"MinorRel":7}}
10:08:12.616 RSL: RESULT = {"ZbState":{"Status":50,"MajorRel":2,"MinorRel":7,"MaintRel":19,"Revision":0}}
10:08:12.953 RSL: RESULT = {"ZbState":{"Status":2,"Message":"Resetting configuration"}}
10:08:16.003 RSL: RESULT = {"ZbState":{"Status":99,"Message":"Abort"}}
10:08:16.005 ZIG: Abort
10:08:16.005 ZIG: Stopping (99)
10:08:28.216 FLH: Starting verification of HEX file
10:08:48.844 FLH: Verification of HEX file OK
10:10:21.481 FLH: cc2652_flasher rx=23 tx=19 rst=15 bsl=22
10:10:21.499 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
10:10:21.620 stack traceback:
10:10:21.621 : in function flash
10:10:21.621 : in function main
10:10:21.622 BRY: stack[1] = type='function' ()
10:10:21.633 BRY: stack[2] = type='string' (protocol_error)
10:10:21.634 BRY: stack[3] = type='nil' ()
10:13:24.902 RSL: STATE = {"Time":"2025-03-02T10:13:24","Uptime":"0T00:05:29","UptimeSec":329,"Heap":171,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":16,"Objects":279},"Wifi":{"AP":1,"SSId":"Dachniki-2","BSSId":"2C:C8:1B:4B:97:61","Channel":1,"Mode":"11g","RSSI":100,"Signal":-46,"LinkCount":1,"Downtime":"0T00:00:03"}}

[pterhu]

Hello
Same situation with me!
I'm using the 14.5.0.2 version of tasmota and also tried the above mentioned hex files.

23:28:54.281 FLH: Starting verification of HEX file
23:29:14.211 FLH: Verification of HEX file OK
23:29:52.776 FLH: cc2652_flasher rx=23 tx=19 rst=15 bsl=22
23:29:52.800 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
23:29:52.913 stack traceback:
23:29:52.914 : in function flash
23:29:52.915 : in function main
23:29:52.916 BRY: stack[1] = type='function' ()
23:29:52.916 BRY: stack[2] = type='string' (protocol_error)
23:29:52.917 BRY: stack[3] = type='nil' ()

[s-hadinger]

I will try later this week on my side. Can you confirm that you didn't flash any other firmware on the CC2652P ? It still contains the factory firmware from Sonoff?

[pterhu]

I can confirm, yes. I tried but it didn't work.

[s-hadinger]

Ok. When did you buy it? Do you have a picture of the PCB ?

Is it the same revision as this one?

[pterhu]

I bought it few days/weeks ago.

[s-hadinger]

Thanks. I will add some logging, until then I have no clue why it's not working anymore

[s-hadinger]

I just tried with my Sonoff ZbBridge Pro:

• reset the device
• used Auto Configuration to configure the template
• downloaded files: cc2652_flasher.be, intelhex.be, sonoff_zb_pro_flasher.be
• downloaded file: SonoffZBPro_coord_20240710.hex

In Berry console:

import sonoff_zb_pro_flasher as cc
cc.load("SonoffZBPro_coord_20240710.hex")
cc.check()

FLH: Starting verification of HEX file
FLH: Verification of HEX file OK

cc.flash()

It took 8 minutes and the flashing was complete:

23:31:57.038 FLH: cc2652_flasher rx=23 tx=19 rst=15 bsl=22
23:31:57.054 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
23:39:47.383 FLH: Flashing completed: OK
23:39:47.490 FLH: Flash crc32 0x000000 - 0x2FFFF = bytes('D0D7B0AA')

[kgooris]

having the same problem, what exactly did you do to fix this? I did try the reset procedure, but without succes.
Whatever I try to do in berry Scripting, its seems always to fail. Except the cc.check()
Also saving the existing data is failing. Seems somehow I don't have proper ready/write permissions to the cc2652..

[s-hadinger]

The error reported is 'protocol error' which means that Tasmota failed to recognize BSL (Bootloader Serial Link) mode needed for flashing.
Since the hardware hasn't changed, I suspect that Sonoff change the bootloader version and makes the BSL detection fail.

I will add logging next week to see what is actually returned.

Stay tuned

[kgooris]

Thx for helping out already, Maybe also something interesting, but not sure they are related, is the fact that I don't see the buttons "Zigbee Permit Join" and "Zigbee Map"

[kgooris]

it looks a bit the same then this issue #17321
but then again, I'm not sure what I'm doing wrong... I don't have the sonoff firmware as backup eather....

[kgooris]

I'm unable to reproduce the issue/fix. I will probably need to order a new sonoff zigbee bridge pro, as now the flashing works all the time.

[s-hadinger]

I updated the scripts cc2652_flasher.be and cc2652_flasher.be

Please download them again in the file system and try again:

import sonoff_zb_pro_flasher as cc
cc.load("SonoffZBPro_coord_20240710.hex")
cc.check()
# wait 1-2 minutes for confirmation
cc.flash()
# wait 9 minutes and check the console

See #23136

[pterhu]

Thank you for your work!
I also tried to flash with same result: protocol error.

20:52:47.808 FLH: Starting verification of HEX file
20:53:07.311 FLH: Verification of HEX file OK
20:53:48.597 FLH: cc2652_flasher rx=23 tx=19 rst=15 bsl=22
20:53:48.609 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
20:53:48.723 FLH: Exception raised 'protocol_error' - 'received 'bytes('5555')''
20:54:00.392 FLH: Starting verification of HEX file
20:54:20.559 FLH: Verification of HEX file OK
20:54:20.645 FLH: Starting verification of HEX file
20:54:40.790 FLH: Verification of HEX file OK
20:54:40.923 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
20:54:41.037 FLH: Exception raised 'protocol_error' - 'received 'bytes('5555')''

Now I'll keep trying.

update:
I also reflashed the tasmota, uploaded the new files and still get protocol error message.
Here is the full log after booting and flashing:

00:00:00.002 HDW: ESP32-D0WD-V3 v3.1 (PSRAM)
00:00:00.059 UFS: FlashFS mounted with 804 kB free
00:00:00.073 CFG: Loaded from File, Count 15
00:00:00.081 QPC: Count 1
00:00:00.085 I2C: Bus1 using GPIO26(SCL) and GPIO25(SDA)
00:00:00.127 BRY: Berry initialized, RAM used 3516 bytes
00:00:00.153 Project tasmota - Tasmota Version 14.5.0(release-zbbrdgpro)-3_1_1(2025-02-18T14:37:02)
00:00:00.154 ZIG: Loading Zigbee data
00:00:00.159 ZIG: No Zigbee device information
00:00:00.162 ZIG: No Zigbee device data
00:00:00.162 ZIG: ZbLoad '<internal_plugin>' loaded successfully
00:00:01.065 WIF: Connecting to AP1 AP-Net Channel 6 BSSId .......... in mode HT40 as tasmota-F3EC14-3092...
00:00:03.692 WIF: Connected
00:00:03.949 HTP: Web server active on tasmota-F3EC14-3092 with IP address 192.168.0.194
23:24:19.899 RSL: INFO1 = {"Info1":{"Module":"Sonoff Zigbee Pro","Version":"14.5.0(release-zbbrdgpro)","FallbackTopic":"cmnd/DVES_F3EC14_fb/","GroupTopic":"cmnd/tasmotas/"}}
23:24:19.912 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-F3EC14-3092","IPAddress":"192.168.0.194","IP6Global":"","IP6Local":"fe80::ea6b:eaff:fef3:ec14%st1"}}
23:24:19.925 RSL: INFO3 = {"Info3":{"RestartReason":"Vbat power on reset","BootCount":4}}
23:24:22.926 QPC: Reset
23:24:23.924 RSL: STATE = {"Time":"2025-03-12T23:24:23","Uptime":"0T00:00:08","UptimeSec":8,"Heap":172,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":45},"Wifi":{"AP":1,"SSId":"AP-Net","BSSId":"1......E","Channel":6,"Mode":"HT40","RSSI":100,"Signal":-44,"LinkCount":1,"Downtime":"0T00:00:03"}}
23:24:30.614 ZIG: rebooting ZNP device
23:24:32.541 RSL: RESULT = {"ZbState":{"Status":1,"Message":"CCxxxx ZNP booted","RestartReason":"Power-up","MajorRel":2,"MinorRel":7}}
23:24:32.717 RSL: RESULT = {"ZbState":{"Status":50,"MajorRel":2,"MinorRel":7,"MaintRel":19,"Revision":0}}
23:24:33.066 RSL: RESULT = {"ZbState":{"Status":2,"Message":"Resetting configuration"}}
23:24:36.017 RSL: RESULT = {"ZbState":{"Status":99,"Message":"Abort"}}
23:24:36.019 ZIG: Abort
23:24:36.019 ZIG: Stopping (99)
23:24:55.426 FLH: Starting verification of HEX file
23:25:15.620 FLH: Verification of HEX file OK
23:25:24.426 FLH: cc2652_flasher rx=23 tx=19 rst=15 bsl=22
23:25:24.443 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
23:25:24.558 FLH: Exception raised 'protocol_error' - 'received 'bytes('5555')''

update2:
now I get different bytes back
18:08:30.730 FLH: Starting verification of HEX file
18:08:50.949 FLH: Verification of HEX file OK
18:10:02.561 FLH: cc2652_flasher rx=23 tx=19 rst=15 bsl=22
18:10:02.587 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
18:10:02.701 FLH: Exception raised 'protocol_error' - 'received 'bytes('F5')''

5 minutes later..
18:15:16.616 FLH: Starting verification of HEX file
18:15:37.487 FLH: Verification of HEX file OK
18:16:09.676 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
18:24:27.266 FLH: Flashing completed: OK
18:24:27.374 FLH: Flash crc32 0x000000 - 0x2FFFF = bytes('D0D7B0AA')

I didn't change anything, there was no restart..

[pterhu]

after retrying a few times, it seems to have worked...

00:18:35.745 FLH: Starting verification of HEX file
00:18:56.972 FLH: Verification of HEX file OK
00:19:11.468 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
00:27:35.671 FLH: Flashing completed: OK
00:27:35.779 FLH: Flash crc32 0x000000 - 0x2FFFF = bytes('D0D7B0AA')

if you want me to help you further, to make this work better, no problem, love to help and reflash the device.

Did you do something "special" during the tryouts?

[kgooris]

I will try to reproduce my steps, and add some feedback here

[rodionos]

I had a similar protocol error issue with the 2022 hex file on a bridge that I purchased on March 10, 2025.

Replacing the files, flushing, restarting the bridge, and disconnecting the power supply fixed it.

[kgooris]

tried that with me, and it did not work, I played around with the libraries and tried things myself, until the bootloader responded with the correct ID. And then it got working. Some initialization steps maybe missing I don't know. Thats why I'm trying to reproduce it ;)

[amerlini]

I'm trying to flash the firmware on a brand new Zigbee Bridge Pro and I'm facing the protocol error issue.

As I'm new to Tasmota I'm reporting all the step done, pardon my simplicity:

• Flashed tasmota32-zbbrdgpro.factory.bin using the webinstaller
• Checked the filesystem and template
• Flashed with embedded files and got error
• Uploaded new files (SonoffZBPro_coord_20240710.hex , cc2652_flasher.be and sonoff_zb_pro_flasher.be)
• Tried multiple times to flash the fw, without succes. Console reports various protocol errors
• Reboot and retry: no success
• Removed all files, uploaded fresh one with the new version: no success
• Tasmota factory reset: no luck

Here's the output of today's attemtps:
I started with a dump test:

import sonoff_zb_pro_flasher as cc
cc.dump_to_file("SonoffZBPro_dump.bin")

09:15:32.222 FLH: cc2652_flasher rx=23 tx=19 rst=15 bsl=22
09:15:32.225 FLH: Dump started (takes 3 minutes during which Tasmota is unresponsive)
09:16:28.141 BRY: Exception> 'serial_error' - buffer too small
09:16:28.142 stack traceback:
09:16:28.142 	<unknown source>: in function `flash_dump_to_file`
09:16:28.153 	<unknown source>: in function `dump_to_file`
09:16:28.153 	<unknown source>: in function `main`

try again the dump

09:17:27.207 BRY: Exception> 'protocol_error' - received 'bytes('FF005555')'
09:17:27.207 stack traceback:
09:17:27.208 	<unknown source>: in function `reset_bsl`
09:17:27.219 	<unknown source>: in function `start`
09:17:27.219 	<unknown source>: in function `dump_to_file`
09:17:27.230 	<unknown source>: in function `main`

now the flash

import sonoff_zb_pro_flasher as cc
cc.load("SonoffZBPro_coord_20240710.hex")
cc.check()

09:18:34.219 FLH: Starting verification of HEX file
09:18:54.327 FLH: Verification of HEX file OK

cc.flash()
09:19:18.933 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
09:19:19.047 FLH: Exception raised 'protocol_error' - 'received 'bytes('F807FF00')''

Second try

cc.check()
09:19:36.046 FLH: Starting verification of HEX file
09:19:56.138 FLH: Verification of HEX file OK

cc.flash()
09:20:28.253 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
09:20:28.367 FLH: Exception raised 'protocol_error' - 'received 'bytes('FFFF00FFDDFAFF5555')''

Is there anything I'm missing? any advice?

Thanks,
Andrea

[Jason2866]

No, please use the provided bundled verified working coordinator firmware.

[s-hadinger]

While it is generally better to use the latest SonoffZBPro_coord_20240710.hex, I haven't seen any difference between both versions. You can keep SonoffZBPro_coord_20220219.hex.

[valdus2]

Having a working Bridge Pro (with 20240710.hex) and wanting to update to latest Tasmota, do we have to make all the procedure from the start (through Berry), or just firmware update from the web ui as all other esp's is enough?

[sfromis]

Just the regular Tasmota firmware upgrade, without touching the Zigbee parts, should be fine.

[valdus2]

Thank you.

[richardfyeo]

Hi, faced similar problems with a new sonoff pro yesterday/today, but I have just managed to get it working (I think..).

Not really sure what the trick is, but the process I followed (after several failed attempts, misdirections and reloads) is below . I initially saw some odd import errors, and failures to find main() etc. Some of this may have been when I managed to download the hex as ascii.

My config process for board marked ZBBridge-P v1.1, dated 2021.11.12

1. Opened up the pro bridge and connected to the board to allow me to flash the esp32 - Do check your USB to serial adaptor voltages first, my initial cable had 3.3v logic, but a 5v supply!
2. Flashed the latest sonoff pro firmware via the tasmota online flasher - No need to use the esptool as mentioned in several guides
3. Removed the flashing cables and rebooted to get to the wed console via wifi
4. Copied the latest 3 scripts from https://github.com/arendst/Tasmota/tree/development/tasmota/berry/zigbee
5. Uploaded the latest hex for the bridge from https://github.com/arendst/Tasmota/tree/development/tools/fw_SonoffZigbeeBridgePro_cc2652 - As mentioned before, make sure you download the hex code as raw hex (~400kb) using the download link at the top right, not as an ascii file..
6. Power cycled the bridge
7. Connected to the berry console and ran these commands - I needed to try this a few times, as the console often gave no response

import sonoff_zb_pro_flasher as cc
cc.load("SonoffZBPro_coord_20240710.hex")
cc.check()

8. Once I saw the code run (3-4th attempt, us). I ran cc.check() - At this point I saw no response from the berry console, and the webpage would not reload, also no lights on the board
9. Waited until the webpage could be reloaded after 5-8 mins - This may the critical step. I suspect the console had failed to show the flashing hex.. message, and before in my impatience I had power cycled again before it had finished flashing, as I assumed it had frozen
10. Power cycled again and looked for the zigbee controls (permit join and map). If you see these, and they stay visible (confusingly they did appear for a few secs before it was working), you may have succeeded. The zigbee buttons take perhaps 30-50s to turn from grey to blue as the zigbee processes start up.

I have just paired a test sensor to the bridge, and all is looking great, so hopefully this info helps someone else who is stuck in the same loop..

Good luck, Richard

[Araforn]

Hi All. Im driven mental trying to get this coordinator to flash.

Summary of steps.

1. Flash the latest - tasmota32-zbbrdgpro.factory.bin.
2. I note all neccessay files are already present.
3. In Berry console, i run the check on the Hex file. Its all good.
4. Whenever i run the cc.flash() I get these errors.

cc.flash()
FLH: cc2652_flasher rx=-1 tx=-1 rst=-1 bsl=-1
BRY: Exception> 'value_error' - cc2652_flasher unspecified GPIOs
stack traceback:
: in function init
: in function loader
: in function flash' <unknown source>: in function main'

I've tried to normally upgrade tasmota without the factory.bin and also manually copy the files but always end up with the same error.
I'm at my wits end if any body has any idea?.

[sfromis]

Well, as the message says "cc2652_flasher unspecified GPIOs" means that you need to configure the gpios before it is able to know what pins to use.
FLH: cc2652_flasher rx=-1 tx=-1 rst=-1 bsl=-1 indicates that you did not.

It should work if you first apply the template from https://templates.blakadder.com/sonoff_ZBBridge-P.html
(See the how-to link in the left column)

[ItsCheeseGromit]

I'm in the same boat.
I've been trying for a few days, and from what I can see in this thread, the thing that works for some is to just keep trying?

I've got no problem getting Tasmoto on the device, it's flashing the coordinator that's the issue.
I've tried using release/tasmota32-zbbrdgpro.factory.bin and the .be/.hex files it includes, as well as the (apparently) newer versions available here https://github.com/arendst/Tasmota/tree/development/tasmota/berry/zigbee

I've tried reflashing, resetting, power cycling and all sorts of combinations of the above with no luck.

I just keep hitting a roadblock here:

import sonoff_zb_pro_flasher as cc
cc.load("SonoffZBPro_coord_20220219.hex")
cc.check()
FLH: Starting verification of HEX file
FLH: Verification of HEX file OK
cc.flash()
FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
FLH: Exception raised 'protocol_error' - 'received 'bytes('5555')''

Any further suggestions, or anything I can try?
This is my first experience with any of this (Tasmoto/Zigbee/Sonoff/Berry, etc) so I have no idea what would be worthwhile to try or not.

Thanks

Edit to add: Should the LEDs be on or off? Mine are on until I set this in Configuration -> Configure other:

{"NAME":"Sonoff Zigbee Pro","GPIO":[0,0,576,0,480,0,0,0,0,1,1,5792,0,0,0,3552,0,320,5793,3584,0,640,608,32,0,0,0,0,0,1,0,0,0,0,0,0],"FLAG":0,"BASE":1}

[Araforn]

I've spent hours on this to the point i bricked my device.

I just gave up and just bought two SLZB-06's. I won't regret my purchase 😌

[dgel27]

Hi,
It seems i have same behaviour.
I think i cannot flash the zigbee part. I seems that begin, but i cannot see any output on cc.flash()

After waiting the time and power cycle i have below logs from 2022 version:

00:00:00.001 HDW: ESP32-D0WD-V3 v3.1
00:00:00.076 UFS: FlashFS mounted with 908 kB free
00:00:00.094 CFG: Loaded from File, Count 29
00:00:00.105 QPC: Count 1
00:00:00.106 CFG: CR 403/699, Busy 0
00:00:00.109 I2C: Bus1 using GPIO26(SCL) and GPIO25(SDA)
00:00:00.110 TYA: Active=0
00:00:00.113 ROT: Mode 1
00:00:00.121 BRY: GC from 3930 to 3149 bytes, objects freed 5/17 (in 1 ms) - slots from 35/61 to 22/61
00:00:00.156 BRY: GC from 4445 to 3508 bytes, objects freed 7/35 (in 0 ms) - slots from 51/76 to 37/76
00:00:00.156 BRY: Berry initialized, RAM used 3508 bytes
00:00:00.195 BRY: No 'preinit.be'
00:00:00.196 ZIG: GPIOs Rx:23 Tx:19
00:00:00.198 ZIG: Serial UART2
00:00:00.198 SRC: Restart
00:00:00.201 Project tasmota - ZB2 Version 14.2.0(release-zbbrdgpro)-3_0_4(2024-08-14T12:39:09)
00:00:00.201 ETH: No ETH MDC and ETH MDIO GPIO defined
00:00:00.202 ZIG: Loading Zigbee data
00:00:00.209 ZIG: No Zigbee device information
00:00:00.213 ZIG: No Zigbee device data
00:00:00.214 ZIG: ZbLoad '<internal_plugin>' loaded successfully
00:00:00.465 BRY: No 'autoexec.be'
00:00:00.608 WIF: Checking connection...
00:00:00.608 WIF: Attempting connection...
00:00:01.077 WIF: Connecting to AP1 HomeAutomation Channel 1 BSSId EC:8C:A2:49:83:48 in mode HT40 as tasmota-747144-4420...
00:00:02.552 WIF: IPv4 192.168.1.44, mask 255.255.255.0, gateway 192.168.1.1
00:00:03.676 WIF: Checking connection...
00:00:03.677 WIF: Connected
00:00:03.703 WIF: IPv6 Local fe80::9654:c5ff:fe74:7144%st1
00:00:03.882 HTP: Web server active on tasmota-747144-4420 with IP address 192.168.1.44
00:00:03.884 NTP: Sync time...
00:00:03.897 WIF: DNS resolved '2.pool.ntp.org' (45.144.172.66) in 11 ms
00:00:04.011 RTC: UTC 2025-05-16T03:39:15Z, DST 2025-03-30T02:00:00, STD 2025-10-26T03:00:00
04:39:15.000 RTC: Synced by NTP
04:39:15.906 MQT: Attempting connection...
04:39:15.923 MQT: Connected
04:39:15.926 MQT: tele/tasmota_747144/LWT = Online (retained)
04:39:15.928 MQT: cmnd/tasmota_747144/POWER =
04:39:15.929 MQT: Subscribe to cmnd/tasmota_747144/#
04:39:15.930 MQT: Subscribe to cmnd/tasmotas/#
04:39:15.931 MQT: Subscribe to cmnd/DVES_747144_fb/#
04:39:15.934 MQT: tele/tasmota_747144/INFO1 = {"Info1":{"Module":"Sonoff Zigbee Pro","Version":"14.2.0(release-zbbrdgpro)","FallbackTopic":"cmnd/DVES_747144_fb/","GroupTopic":"cmnd/tasmotas/"}}
04:39:15.947 MQT: tele/tasmota_747144/INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-747144-4420","IPAddress":"192.168.1.44","IP6Global":"","IP6Local":"fe80::9654:c5ff:fe74:7144%st1"}}
04:39:15.971 MQT: tele/tasmota_747144/INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":13}}
04:39:15.976 TFS: File 'autoexec.bat' not found
04:39:17.147 SRC: MQTT
04:39:17.148 CMD: Grp 0, Cmd 'STATUS', Idx 1, Len 1, Pld 1, Data '1'
04:39:17.153 MQT: stat/tasmota_747144/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"https://ota.tasmota.com/tasmota32/tasmota32-zbbrdgpro.bin","RestartReason":"Software reset CPU","Uptime":"0T00:00:06","StartupUTC":"2025-05-16T03:39:11","Sleep":50,"CfgHolder":4617,"BootCount":12,"BCResetTime":"2025-05-15T19:30:37","SaveCount":29}}
04:39:17.197 SRC: MQTT
04:39:17.198 CMD: Grp 0, Cmd 'STATUS', Idx 1, Len 2, Pld 11, Data '11'
04:39:17.201 BRY: GC from 5720 to 3954 bytes, objects freed 18/45 (in 1 ms) - slots from 75/91 to 46/91
04:39:17.208 MQT: stat/tasmota_747144/STATUS11 = {"StatusSTS":{"Time":"2025-05-16T04:39:17","Uptime":"0T00:00:06","UptimeSec":6,"Heap":161,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":23,"MqttCount":1,"Berry":{"HeapUsed":3,"Objects":45},"Wifi":{"AP":1,"SSId":"HomeAutomation","BSSId":"EC:8C:A2:49:83:48","Channel":1,"Mode":"HT40","RSSI":84,"Signal":-58,"LinkCount":1,"Downtime":"0T00:00:03"}}}
04:39:17.348 HTP: Main Menu
04:39:18.907 QPC: Reset
04:39:19.899 BRY: GC from 4329 to 3954 bytes, objects freed 1/45 (in 1 ms) - slots from 47/91 to 46/91
04:39:19.907 MQT: tele/tasmota_747144/STATE = {"Time":"2025-05-16T04:39:19","Uptime":"0T00:00:08","UptimeSec":8,"Heap":162,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":3,"Objects":45},"Wifi":{"AP":1,"SSId":"HomeAutomation","BSSId":"EC:8C:A2:49:83:48","Channel":1,"Mode":"HT40","RSSI":84,"Signal":-58,"LinkCount":1,"Downtime":"0T00:00:03"}}
04:39:20.898 APP: Boot Count 13
04:39:21.558 CFG: Saved, Count 30, Bytes 4096
04:39:23.165 HTP: Tools
04:39:24.909 MQT: tasmota/discovery/9454C5747144/config = {"ip":"192.168.1.44","dn":"ZB2","fn":["ZB2",null,null,null,null,null,null,null],"hn":"tasmota-747144-4420","mac":"9454C5747144","md":"Sonoff Zigbee Pro","ty":0,"if":0,"ofln":"Offline","onln":"Online","state":["OFF","ON","TOGGLE","HOLD"],"sw":"14.2.0","t":"tasmota_747144","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"bat":0,"dslp":0,"sho":[],"sht":[],"ver":1} (retained)
04:39:24.917 MQT: tasmota/discovery/9454C5747144/sensors = {"sn":{"Time":"2025-05-16T04:39:24"},"ver":1} (retained)
04:39:25.149 HTP: Console
04:39:26.597 ZIG: rebooting ZNP device
04:39:29.498 ZbInput discarding byte 00
04:39:29.500 ZIG: {"ZbZNPReceived":"4180000201020701"}
04:39:29.504 MQT: tele/tasmota_747144/RESULT = {"ZbState":{"Status":1,"Message":"CCxxxx ZNP booted","RestartReason":"Power-up","MajorRel":2,"MinorRel":7}}
04:39:29.647 ZIG: checking device configuration
04:39:29.649 ZIG: ZbZNPSent 2102
04:39:29.699 ZIG: {"ZbZNPReceived":"610202010207013B89340100"}
04:39:29.704 MQT: tele/tasmota_747144/RESULT = {"ZbState":{"Status":50,"MajorRel":2,"MinorRel":7,"MaintRel":1,"Revision":20220219}}
04:39:29.717 ZIG: ZbZNPSent 2108600000
04:39:29.748 ZIG: {"ZbZNPReceived":"6108000155"}
04:39:29.750 ZIG: ZbZNPSent 2108870000
04:39:29.798 ZIG: {"ZbZNPReceived":"6108000100"}
04:39:29.800 ZIG: ZbZNPSent 2108830000
04:39:29.848 ZIG: {"ZbZNPReceived":"61080002FFFF"}
04:39:29.854 MQT: tele/tasmota_747144/RESULT = {"ZbState":{"Status":2,"Message":"Resetting configuration"}}
04:39:29.858 ZIG: ZbZNPSent 21090300000103
04:39:29.898 ZIG: {"ZbZNPReceived":"610900"}
04:39:29.900 ZIG: ZbZNPSent 410000
04:39:31.648 ZbInput discarding byte 00
04:39:31.650 ZIG: {"ZbZNPReceived":"4180000201020701"}
04:39:31.652 ZIG: ZbZNPSent 2109830000020100
04:39:31.698 ZIG: {"ZbZNPReceived":"610900"}
04:39:31.700 ZIG: ZbZNPSent 21092D00000800000000CCCCCCCC
04:39:31.748 ZIG: {"ZbZNPReceived":"610900"}
04:39:31.750 ZIG: ZbZNPSent 21098400000400080000
04:39:31.798 ZIG: {"ZbZNPReceived":"610900"}
04:39:31.800 ZIG: ZbZNPSent 21098700000100
04:39:31.848 ZIG: {"ZbZNPReceived":"610900"}
04:39:31.850 ZIG: ZbZNPSent 21096200001000004471000000000000447100000000
04:39:31.898 ZIG: {"ZbZNPReceived":"610900"}
04:39:31.900 ZIG: ZbZNPSent 21096300000100
04:39:31.948 ZIG: {"ZbZNPReceived":"610900"}
04:39:31.950 ZIG: ZbZNPSent 210901010020FFFFFFFFFFFFFFFF5A6967426565416C6C69616E636530390000000000000000
04:39:31.998 ZIG: {"ZbZNPReceived":"610902"}
04:39:32.000 ZIG: ZbZNPSent 21098F00000101
04:39:32.048 ZIG: {"ZbZNPReceived":"610900"}
04:39:32.050 ZIG: ZbZNPSent 2107600001000100
04:39:32.098 ZIG: {"ZbZNPReceived":"610700"}
04:39:32.099 ZIG: ZbZNPSent 21096000000155
04:39:32.148 ZIG: {"ZbZNPReceived":"610900"}
04:39:32.150 ZIG: ZbZNPSent 2108620000
04:39:32.199 ZIG: {"ZbZNPReceived":"6108001000004471000000000000447100000000"}
04:39:32.204 MQT: tele/tasmota_747144/RESULT = {"ZbState":{"Status":3,"Message":"Configured, starting coordinator"}}
04:39:32.209 ZIG: ZbZNPSent 2F080100080000
04:39:32.248 ZIG: {"ZbZNPReceived":"6F0800"}
04:39:32.250 ZIG: ZbZNPSent 2F080000080000
04:39:32.298 ZIG: {"ZbZNPReceived":"6F0800"}
04:39:32.300 ZIG: ZbZNPSent 2F0504
04:39:34.650 WIF: Checking connection...
04:39:35.648 ZIG: {"ZbZNPReceived":"6F0500"}
04:39:35.721 ZIG: {"ZbZNPReceived":"4F80010204"}
04:39:35.898 ZIG: {"ZbZNPReceived":"45C008"}
04:39:37.648 ZIG: {"ZbZNPReceived":"45C008"}
04:39:37.848 ZIG: {"ZbZNPReceived":"45C008"}
04:39:38.197 ZIG: {"ZbZNPReceived":"45C000"}
04:39:38.248 ZIG: {"ZbZNPReceived":"4F80080200"}
04:39:38.298 ZIG: {"ZbZNPReceived":"4F80080200"}
04:39:54.650 WIF: Checking connection...
04:39:55.698 ZIG: timeout, goto label 99
04:39:55.702 MQT: tele/tasmota_747144/RESULT = {"ZbState":{"Status":99,"Message":"Abort"}}
04:39:55.705 ZIG: Abort
04:39:55.706 ZIG: Stopping (99)
04:40:14.649 WIF: Checking connection...

I have the same ZBpro, that works fine.
Is it some way to flash zigbee module with external tools?

Thanks!

[OK1XRP]

Hi,
i had the same problem.
After verification of file and start flash : FLH: Exception raised 'protocol_error' - 'received 'bytes('5555')''
It's unbelievable, but I found the solution, on board is button for switching zigbee radio. When is "ON" and zigbee led lighting , flashing not work. When i switeched zigbee radio to off and led was grey, flash new fw passed.

[ItsCheeseGromit]

Mine has actually started working as well...
I have not touched it since my last post on May 8. It's been powered off and sitting on my desk.

Yesterday I plugged it in and the proper zigbee menus are there and everything seems to be working as exected.
The only thing that has changed in that time is I changed my laptop OS to Linux (Mint Mate to be specific). I don't see what kind of difference that would make since I did actually try flashing in Windows 10 and via a Mint Live USB earlier.

So... Yeah. shrug

[dgel27]

In my case problem solved by changing config manually after burning. #23435

[elektromassa]

Hi,
same error. I tried both new and old versions of the programming files, and the tasmota in development and release versions. Nothing. I'm actually thinking of throwing it into the wall too!

18:42:38.711 FLH: Verification of HEX file OK
18:42:38.820 BRY: GC from 20196 to 15345 bytes, objects freed 48/230 (in 3 ms) - slots from 229/259 to 193/259
18:42:38.844 FLH: cc2652_flasher rx=23 tx=19 rst=15 bsl=22
18:42:38.848 BRY: Serial UART1
18:42:38.883 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
18:42:38.997 FLH: Exception raised 'protocol_error' - 'received 'bytes('5555')'