Sonoff Zigbee Bridge Pro, Problems with Firmwareupgrade on Berry Console #23074

Patrix2911 · 2025-02-26T16:28:25Z

Patrix2911
Feb 26, 2025

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 · 2025-02-27T17:15:29Z

s-hadinger
Feb 27, 2025
Collaborator

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

1 reply

sidorovit Mar 2, 2025

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 · 2025-03-03T22:45:49Z

pterhu
Mar 3, 2025

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' ()

0 replies

s-hadinger · 2025-03-04T10:56:55Z

s-hadinger
Mar 4, 2025
Collaborator

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?

4 replies

pterhu Mar 6, 2025

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

s-hadinger Mar 6, 2025
Collaborator

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

Is it the same revision as this one?

pterhu Mar 7, 2025

I bought it few days/weeks ago.

s-hadinger Mar 7, 2025
Collaborator

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

s-hadinger · 2025-03-06T22:40:48Z

s-hadinger
Mar 6, 2025
Collaborator

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')

4 replies

kgooris Mar 7, 2025

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 Mar 8, 2025
Collaborator

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 Mar 8, 2025

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 Mar 11, 2025

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....

s-hadinger · 2025-03-11T22:08:23Z

s-hadinger
Mar 11, 2025
Collaborator

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

6 replies

s-hadinger Mar 11, 2025
Collaborator

Thanks, at least we are progressing. The response from BSL is 5555 instead of being CC. I now need to find information about the new bootloader

kgooris Mar 11, 2025

ok, reflash = same result. Thx already.

kgooris Mar 11, 2025

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.

pterhu Mar 12, 2025

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')''

pterhu Mar 12, 2025

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?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sonoff Zigbee Bridge Pro, Problems with Firmwareupgrade on Berry Console #23074

{{title}}

Replies: 5 comments 15 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Sonoff Zigbee Bridge Pro, Problems with Firmwareupgrade on Berry Console #23074

Replies: 5 comments · 15 replies

s-hadinger Feb 27, 2025 Collaborator

s-hadinger Mar 4, 2025 Collaborator

s-hadinger Mar 6, 2025 Collaborator

s-hadinger Mar 7, 2025 Collaborator

s-hadinger Mar 6, 2025 Collaborator

s-hadinger Mar 8, 2025 Collaborator

s-hadinger Mar 11, 2025 Collaborator

s-hadinger Mar 11, 2025 Collaborator

Replies: 5 comments 15 replies

s-hadinger
Feb 27, 2025
Collaborator

s-hadinger
Mar 4, 2025
Collaborator

s-hadinger Mar 6, 2025
Collaborator

s-hadinger Mar 7, 2025
Collaborator

s-hadinger
Mar 6, 2025
Collaborator

s-hadinger Mar 8, 2025
Collaborator

s-hadinger
Mar 11, 2025
Collaborator

s-hadinger Mar 11, 2025
Collaborator