SONOFF Zigbee Bridge Pro (ZBBridge Pro) Router firmware

[roburb]

It is a new discussion for the router firmware for ZBBridge Pro.
The discussion begin #14419 (comment).

[roburb]

There is a router firmware, but there is issue with flashing of this firmware, see the link in first comment.
Any idea, please?

[s-hadinger]

Use this firmware https://github.com/arendst/Tasmota/blob/development/tools/fw_SonoffZigbeeBridgePro_router_only_cc2652/SonoffZBPro_router_20220125.hex

[allansari]

After flashing, I couldn't connect the flashed ZB Pro to Hubitat? It's not showing

[Mike59FR]

Hello,

I've this probem with Sonoff Zbbridge-P and router mode, see please #16957 (reply in thread):

17:27:13.574 ZIG: rebooting ZNP device
17:27:13.740 ZIG: ZbZNPSent 0xFF x 255
17:27:13.741 ZIG: ZbZNPSent 410000
17:27:18.429 HTP: Tools
17:27:18.752 ZIG: timeout, goto label 99
17:27:18.754 RSL: RESULT = {"ZbState":{"Status":99,"Message":"Abort"}}
17:27:18.755 ZIG: Abort
17:27:18.756 ZIG: Stopping (99)

Thanks for your help.

[a24me]

Not very nice to lock the public discussion <link> to Collaborators only. It does not help the community.

[sfromis]

Not very nice to reuse an old discussion thread for different topics. Clearly separate threads is a much better way to go.

[s-hadinger]

The original discussion was also getting too big with many subthreads which makes it almost impossible for the community to follow.

This was definitely not a punishment, rather a tentative to make the topic more visible and easy to follow

[a24me]

The firmware file
https://raw.githubusercontent.com/arendst/Tasmota/development/tools/fw_SonoffZigbeeBridgePro_router_only_cc2652/SonoffZBPro_router_20220125.hex
contains at least one error, cannot pass the checks and thus cannot be uploaded.
Fixed and now looking for the button functionality...

[s-hadinger]

What do you mean 'fixed'? Do you have a patched file to share to the community?

[a24me]

Dear @s-hadinger,

I really do not understand the term punishment and the reason behind it. Could you explain?

The way you put it, you should then pin the link to this new topic, at:

the beginning of the previous topic you locked
in the relative thread you locked/cut/stopped the discussion
at the end of the old topic

unlock the old one

so the community can continue to use the old one for the reason it exists and uninterruptedly continue to this one for the ROUTER functionality of the device.
Besides, if I was in your position, I would have never lock a topic for such a reason. I would have contact in a kind way the user and explain him/her what is the most beneficial for the community way and would have propose him/her the relative actions.

Waiting for your next actions.

[s-hadinger]

Thank you so much for sharing your views about managing the community. I was precisely saying that locking the previous thread was not done in bad spirit, but rather to make the discussion easier to read for new joiner.

I felt believed that having one topic per discussion made it easier for new joiner to get the information.

Back to sharing to the community, are you eventually willing to share what you "fixed"?

[roburb]

@a24me, share with us your modifications, please?
What have you done, to have working router mode.
Thank you

[s-hadinger]

Never mind, it looks like a24me is not willing to share with the community after all.

I have fixed the checksum in the firmware, see #16987

[Jason2866]

@a24me Could you share the infos what you did, so that the community can participate?

[a24me]

Just fixed the error in the firmware and uploaded it to the chip

[Jason2866]

Well, what exactly did you changed? The screenshot does not show that.

[seebaer1976]

when running from:
import sonoff_zb_pro_flasher as cc cc.load("SonoffZBPro_router_20220125.hex") cc.check()

I always get the following message:

FLH: Starting verification of HEX file
BRY: Exception> 'value_error' - invalid checksum
stack traceback:
unknown source>: in function parse
unknown source>: in function check
unknown source>: in function main

the SonoffZBPro_coord_20220219.hex passes the check

does anyone have an idea why it is or what i forgot?

[seebaer1976]

after flashing, once completely taken from the stream.
in ha, let the SONOFF Zigbee 3.0 USB Dongle Plus search for devices.
then plugged the bridge back in and pressed the button with a needle so that the green led came on.
after a short time the router was found and set up.

that was my order

[roburb]

I have flashed the firmware from #16957 (reply in thread) Thank you @s-hadinger.
The pairing is exactly as you @seebaer1976 wrote, thanks.
The ZB Bridge is working in router mode now.

[Powermaniaxx]

The error appears for me, I have loaded the hex. What can I do?

Hex from

#16957

[s-hadinger]

I suspect your file is bad. How did you download it and what does it contain?

[Powermaniaxx]

Solution: Do not load HEX with right click! ;)

what is the next step?

[ZamliyMedre]

Hi,

I have the standard sonoff Zigbee bridge hardware, can we use this firmware on those also ? I wish to use them as routers, I have come across digiblur's guide on the internet to convert them which does work however it seems you can only pair 5 child devices per router for some reason.

However, if you flash the tasmota bridge firmware on the same hardware as a coordinator it supports upto 32 devices..

Any help would be very much appreciated.

Many Thanks,

Erdem

[s-hadinger]

No. Zigbee Bridge uses EFR32 MCU while Zigbee Bridge Pro uses CC2652P. They are completely different chips

[ZamliyMedre]

I see, so if I replace the older models with the PRO version of Sonoff bridge and flash it with this router firmware would it have the same limitation of maximum 5-6 child devices directly connected to router ?

The reason why I ask is, I have Aqara contact sensors quite a few of them doted around the house and these sensors seems to stick with the initial router / coordinator they are connected to and they don't seem to like to roam through a different router. For this I have a router on each floor of my property to connect Aqara sensors located on that floor.

I use Zigbee2Mqtt and this way they seem to be stable.. but having being able to connect only 5 child devices per router is not ideal.

I would appreciate if you can confirm if this limitation is not applicable with this firmware used on the PRO version of Sonoff bridge, I will order 3 today :)

Many Thanks

[s-hadinger]

This limitation comes from the router firmware and is generally linked to the limited resources of the hardware. I haven't tried but chances are that it supports more child devices. The person who compiled the router firmware should be able to tell

[allansari]

Hi

Got my new HE hub C7 before unfortunately before the C-8 was released.

Never mind, after taking decisions with HE,i want to strengthen coverage, so i flashed (Sonoff ZigBee bridge Pro) & trying to make it as a repeater but unfortunately, I couldn't pair it with Hubitat.

i tried to follow all the steps in GutHub and here : Sonoff Zigbee Bridge Simply as a Router in HE

it flashed successfully i assume but can't pair it with Hubitat and link it as a device ??

Chip Info:

Chip Family: ESP32
Chip Model: ESP32-D0WDQ5-V3 (revision 3)
Number of Cores: 2
Max CPU Frequency: 240MHz
Has Bluetooth: YES
Has Embedded Flash: NO
Has Factory-Calibrated ADC: YES
MAC Address: 40:22:D8:5F:4E:48
here it shows , flashed successfully

10:57:19.651 FLH: Starting verification of HEX file
10:57:29.898 FLH: Verification of HEX file OK
10:57:33.254 FLH: cc2652_flasher rx=23 tx=19 rst=15 bsl=22
10:57:33.293 FLH: Flashing started (takes 5 minutes during which Tasmota is unresponsive)
11:01:19.704 FLH: Flashing completed: OK
11:01:19.807 FLH: Flash crc32 0x000000 - 0x2FFFF = bytes('1598929A')

Those the files i uploaded

are these configurations correct??

[allansari]

And what I have to do with this flashed bridge?

[s-hadinger]

Why did you buy it in the first place?

[sfromis]

If what you want is to waste the Sonoff Zigbee Bridge Pro as a router instead of a coordinator, you can find and flash router firmware to replace the coordinator firmware normally used by Tasmota. This would remove the Zigbee functionality from Tasmota involvement, as that would leave the Zigbee chip running standalone, without doing what it is meant to be capable of. You'd be running a more expensive device without getting benefit from what you paid.

[allansari]

i thought it could be connected with Habitat but later, unfortunately i discovered its not listed as a device but that was late as I already flashed it :(

[PencilDH]

I am keen to get Bridge pro working as router I have two of them and would be nice to make the useful for something, I just switched to iHost from ITEAD

**** I was missing the step as a newbee that after installing the ESP32 firmware one needs to manually flash the Zgibee chip with the .hex file via berry scripts

[NetanHell]

Hi guys!
I had this exact problem when I initially added the Sonoff ZBBridgePro to HA, several monthes ago. Then, after a week, I somehow fixed it... but I don't remember how...!!! Zigbee just stopped working several days ago. I tried to re-attach the bridge but got an error in HA.

Everything went according to the guide, but for some reason, HA don't agree to add the device as an integration. It thinks for several seconds, then return "Failed to connect" ( like the picture ).

I know it's connecting, since I see the logs in Tasmota.

Can anyone think of a problem that might occur?
Thanks!

• I tried both ZBBridgePro and ZBBridgePro-TCP presets/parameters
• I tried different port numbers
• I tried to upgrade HA and the bridge

20:00:48.640 WIF: Checking connection...
20:00:48.891 TCP: Got connection from 172.25.25.13
20:00:49.350 TCP: to MCU/1: FE00210120
20:00:49.871 TCP: to MCU/1: EFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEF
20:00:49.929 TCP: to MCU/1: EF
20:00:52.336 TCP: to MCU/1: FE00210120
20:00:53.354 TCP: to MCU/1: FE00210120

Sonoff Zigbee Pro
Tasmota
Program Version	12.4.0(zbbrdgpro)
Build Date & Time	2023-02-24T15:35:22
Core/SDK Version	2_0_6/4.4.3.20230129
Uptime	0T00:11:50
Flash Write Count	73
Boot Count	33
Restart Reason	Software reset CPU
 
AP1 SSId (RSSI)	WIFI-Net (100%, -45 dBm) 11n
Hostname	tasmota-605A0C-6668
IP Address (wifi)	172.25.15.21
Gateway	172.25.15.254
Subnet Mask	255.255.255.0
DNS Server1	172.25.25.25
DNS Server2	172.25.25.26
 
HTTP API	Enabled
 
MQTT Host	
MQTT Port	1883
MQTT TLS	Disabled
MQTT User	DVES_USER
MQTT Client	DVES_605A0C
MQTT Topic	tasmota_%06X
MQTT Group Topic 1	cmnd/tasmotas/
MQTT Full Topic	cmnd/tasmota_605A0C/
MQTT Fallback Topic	cmnd/DVES_605A0C_fb/
MQTT No Retain	Disabled
 
Emulation	None
 
ESP Chip Id	6314508 (ESP32-D0WD-V3 rev.3)
Flash Chip Id	0x16405E (DIO)
Flash Size	4096 KB
Program Flash Size	4096 KB
Program Size	1460 KB
Free Program Space	1792 KB
Free Memory	157.8 KB (frag. 31%)
 
Partition app0	1792 KB
Partition app1*	1792 KB (used 81%)
Partition fs	444 KB

[s-hadinger]

We have no control in Tasmota about what HA sends. You need to report to the HA community.

Now looking at the logs, the MCU sends nothing back. It may be an electrical problem or the MCU is dead

[NetanHell]

Hi,
Thank you for your answer. I wanted to make sure it isn't related to the device before going to HA.
What you're saying sounds probable, considering the device seems to be bricked. I noticed it first today morning haha
I'll try to reflash the OS and see where it goes.

Thanks!

[cjgarciao]

Hi,
Is there a newer version of the router firmware for this device?
Is it possible to use one of the available in Koenkk/Z-Stack-firmware (20221102)?
Thanks,
Carlos.

[Jason2866]

No, and you can't use the Koenkk firmware. There are a changes needed.
What's wrong with this one https://github.com/arendst/Tasmota/blob/development/tools/fw_SonoffZigbeeBridgePro_router_only_cc2652/SonoffZBPro_router_20220125.hex

[cjgarciao]

I don't know if there is a problem with 20220125.
What happens to me is that one device (Sonoff SNZB-02 with EFEKTA firmware) was working fine connected to the coordinator. I moved it and I paired it again and it connected to the router and since then it doesn't send temperature or humidity data.
Therefore, I had thought about updating the router firmware, in case it was due to that.

Carlos.

[Jason2866]

We do not provide support for the router firmware.

[iFA88]

Hey there!
I would like to get some support about flashling Sonoff ZigBee bridge pro to a range extender (router).
I have successfully flashed with the https://ota.tasmota.com/tasmota32/tasmota32-zbbrdgpro.factory.bin and after that OTA fw upgrade with https://ota.tasmota.com/tasmota32/tasmota32-zbbrdgpro.bin.
Then i have uploaded the https://github.com/arendst/Tasmota/blob/development/tools/fw_SonoffZigbeeBridgePro_router_only_cc2652/SonoffZBPro_router_20220125.hex file and with berry script executed this: (I had to run this with curl because it had taken so long that browser dopped that request)

import sonoff_zb_pro_flasher as cc
cc.load("SonoffZBPro_router_20220125.hex")
cc.check()
cc.flash()FLH: Starting verification of HEX file
FLH: Verification of HEX file OK
FLH: cc2652_flasher rx=23 tx=19 rst=15 bsl=22
FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
FLH: Flashing completed: OK
FLH: Flash crc32 0x000000 - 0x2FFFF = bytes('4C911E26')

After restart i see the device in my zigbee2mqtt:

but in the tasmota console i have the following:

00:00:00.002 HDW: ESP32-D0WD-V3 v3.0 
00:00:00.193 UFS: FlashFS mounted with 868 kB free
00:00:00.224 CFG: Loaded from File, Count 23
00:00:00.234 QPC: Count 1
00:00:00.240 I2C: Bus1 using GPIO26(SCL) and GPIO25(SDA)
00:00:00.393 BRY: Berry initialized, RAM used=3932 bytes
00:00:00.477 TFS: File '.drvset003' not found
00:00:00.485 Project tasmota - Tasmota Version 13.2.0.1(zbbrdgpro)-2_0_14(2023-10-28T14:25:27)
00:00:01.290 WIF: Connecting to AP1 nemadokwifit Channel 1 BSSId D2:21:F9:9C:90:A1 in mode 11n as tasmota-616044-0068...
00:00:03.131 WIF: Connected
00:00:03.391 HTP: Web server active on tasmota-616044-0068 with IP address 192.168.1.48
00:00:03.397 UPP: Multicast (re)joined
10:22:14.387 RSL: INFO1 = {"Info1":{"Module":"Sonoff Zigbee Pro","Version":"13.2.0.1(zbbrdgpro)","FallbackTopic":"cmnd/DVES_616044_fb/","GroupTopic":"cmnd/tasmotas/"}}
10:22:14.402 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-616044-0068","IPAddress":"192.168.1.48","IP6Global":"","IP6Local":"fe80::4222:d8ff:fe61:6044"}}
10:22:14.415 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":10}}
10:22:16.793 QPC: Reset
10:22:18.781 RSL: STATE = {"Time":"2023-10-29T10:22:18","Uptime":"0T00:00:09","UptimeSec":9,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":42},"Wifi":{"AP":1,"SSId":"nemadokwifit","BSSId":"D2:21:F9:9C:90:A1","Channel":1,"Mode":"11n","RSSI":86,"Signal":-57,"LinkCount":1,"Downtime":"0T00:00:04"}}
10:22:25.790 ZIG: rebooting ZNP device
10:22:30.961 ZIG: timeout, goto label 99
10:22:30.963 RSL: RESULT = {"ZbState":{"Status":99,"Message":"Abort"}}
10:22:30.965 ZIG: Abort
10:22:30.966 ZIG: Stopping (99)
10:23:22.170 CMD: ZbConfig
10:23:22.174 RSL: RESULT = {"ZbConfig":{"Channel":11,"PanID":"0xFFFF","ExtPanID":"0xCCCCCCCC61D82240","KeyL":"0x61D8224060440000","KeyH":"0x61D8224060440000","TxRadio":20}}

I'm not sure thats working as expected. My devices should be connected to this router which is connected to the coordinator. My devices are near to the router and a little far away from the coordinator. Zigbee2MQTT map says that all my devices are connected to the coordinator and not to the router.

Thanks for any help!

[iFA88]

@striker54

curl 'http://192.168.2.1/bc?c2=0&c1=import%20sonoff_zb_pro_flasher%20as%20cc%0Acc.load(%22SonoffZBPro_coord_20230507.hex%22)%0Acc.check()%0Acc.flash()' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0' -H 'Accept: */*' -H 'Accept-Encoding: gzip, deflate' -H 'DNT: 1' -H 'Connection: keep-alive' -H 'Referer: http://192.168.1.48/bc?' -H 'Pragma: no-cache' -H 'Cache-Control: no-cache'

You need replace the file name whatever you want and your device IP address.

[s-hadinger]

Why are you doing such complex thing? Why not just use the Berry console?

[iFA88]

Because browser xhr request will be timeout and you dont see when and whats happening :)

[sfromis]

To execute Berry code from a http request, it is not a good plan to create a dependency of how the Berry console works internally. It is better to use the Br command the regular way.

That could be executing a command like
Br import sonoff_zb_pro_flasher as cc cc.load("SonoffZBPro_coord_20230507.hex") cc.check() cc.flash()
via the usual (and documented) http://192.168.2.1/cm?cmnd=Br.....
Berry is generally not sensitive to line breaks or not.
Of course, doing URL encoding still applies, depending on your shell environment.

[striker54]

The curl command didnt't work for me. Error:
curl: (3) URL using bad/illegal format or missing URL
'cl' is not recognized as an internal or external command, operable program or batch file.)

But the solution of @sfromis with the Br command work perfectly.

Thank you both.
Best regards

[davidrpfarinha]

Hey folks,
Anyone was able to make the Sonoff Zigbee Bridge Pro work as the network adapter for Zigbee2MQTT?
I do see the connection within the logs, but on the Zigbee2MQTT docker it keeps failing, with an Error: SRSP - SAPI - readConfiguration after 6000ms.

Chers

[davidrpfarinha]

Hey @el-bakkali, eventually, I stopped using my Sonoff Zigbee Bridge Pro, and started using my Sonoff Zigbee Bridge. After changing between devices, everything is working as expected. It is a shame that the Sonoff Zigbee Bridge Pro doesn't work.

[s-hadinger]

"It is a shame that the Sonoff Zigbee Bridge Pro doesn't work" - what kind of statement is that?

I have a Sonoff Zigbee Bridge Pro working perfectly well for the last 18 months.

[sfromis]

Mine also works, but I'm not trying to connect it to Zigbee2MQTT

[el-bakkali]

Please can you share how you got it to work ?

[s-hadinger]

If your question is how to use it with Zigbee2MQTT, I'm afraid you should ask in their own forums

[davidrpfarinha]

"It is a shame that the Sonoff Zigbee Bridge Pro doesn't work" - what kind of statement is that?

I have a Sonoff Zigbee Bridge Pro working perfectly well for the last 18 months.

I'm only speaking on the context of using it for the Zigbee2MQTT, which led to my original comment 😅 I do have another one working with ZHA, and works like a charm.

[xeberth]

@saviothecnic

1. You should go to: Tools > Berry Scripting console, and run this commands to install the repeater firmware that is currently in your filesystem:

import` sonoff_zb_pro_flasher as cc
cc.load("SonoffZBPro_router_20220125.hex")
cc.check()
cc.flash()

Once the zb pro flasher completed the installation of the SonoffZBPro_router_20220125.hex file, device will be rebooted.

2. Wait until Tasmota GUI is up again, it can take several minutes.
3. When Tasmota GUI came up, go to Tools > Console and Click on Console (not Berry Scripting console, just Console)

• Into console logs, check if there are some log similar to this:

10:22:30.963 RSL: RESULT = {"ZbState":{"Status":99,"Message":"Abort"}}
10:22:30.965 ZIG: Abort
10:22:30.966 ZIG: Stopping (99)

If they are, its OK, it means that we are doing well, that log is expected when the ZBPro is already working as a router instead of as a coordinator.

4. Now we just need to run an additional command to configure the router module in Tasmota GUI

• In Same console Terminal where you find the logs, run this:
  backlog template {"NAME":"Sonoff ZigRouter","GPIO":[320,5088,0,5120,257,256,0,0,0,576,0,0,32,0],"FLAG":0,"BASE":18} ; delay1 ; module 0
• The bridge should reboot and come back up on the GUI, and now you should be able to see a new On Off Toggle1/Toggle2 Buttons in Tasmota GUI.

5. The device is ready to be paired with your Zigbee network. Go ahead and place it in the desired location of the home and power it up.

• Enable pairing on your Zigbee Network as you would normally pair a regular sensor, switch, etc, your coordinator should be able to discover your device as Router.
• In case you can't discover the Router in your network, simply use a paper clip to briefly push the reset button next to the USB power plug The green LED will light up. Allow 5-6 seconds to pass and press the button again, this will turn off the green LED and the device will be in pairing mode.
• Once the router is added to your network, it will be a matter of time before other end devices begin to connect through it. If you want to speed up the process you can temporarily disconnect other nearby devices with router function to "force" the rest to connect to the new ZBPro Router

[Mike59FR]

Good morning,

I flashed my SONOFF ZBBridge-P in router mode
by :
import sonoff_zb_pro_flasher as cc
cc.load("SonoffZBPro_router_20220125.hex")
cc.check()
cc.flash()

And the result is OK:
14:21:01.565 FLH: Verification of HEX file OK
14:21:01.645 FLH: cc2652_flasher rx=23 tx=19 rst=15 bsl=22
14:21:01.657 FLH: Flashing started (takes 5-8 minutes during which Tasmota is unresponsive)
14:25:19.381 FLH: Flashing completed: OK
14:25:19.490 FLH: Flash crc32 0x000000 - 0x2FFFF = bytes('4C911E26')

I currently have in GPIO:
{"NAME":"Sonoff ZigRouter","GPIO":[320,5088,0,5120,257,256,0,0,0,576,0,0,32,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":18}

My code file is:
SonoffZBPro_router_20220125.hex of size 434524 bytes

But I cannot pair my Sonoff ZBbridge-P to my ZHA gateway

Do I have incorrect information in my update please?
THANKS.

[Mike59FR]

Hello,
My green LED don't light up in pairing mode.
I currently have in GPIO:
{"NAME":"Sonoff ZigRouter","GPIO":[320,5088,0,5120,257,256,0,0,0,576,0,0,32,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":18}

Information on the web gui
Sonoff ZigRouter
Tasmota
Program Version | 14.0.0 (release-zbbrdgpro)

In mode Coordinator, my green LED lights up.
I don't understand the proplem ?
Thanks

[xeberth]

Firmware looks ok, however your GPIO seems different.

Try with this:

In Tasmota console apply the following config:

backlog template {"NAME":"Sonoff ZigRouter","GPIO":[320,5088,0,5120,257,256,0,0,0,576,0,0,32,0],"FLAG":0,"BASE":18} ; delay1 ; module 0

Reboot device, and share a screenshot of your Tasmota Main Menu and Console logs before/after rebooting.

[xeberth]

Another method of pairing is to press the "Toggle 1" button on the Tasmota GUI and leave it set to ON for 5-6 seconds then turn it back off. This is the same as the reset button paper clip push method above.

Of curse you need enable pairing on your Zigbee Network as you would normally pair a regular sensor, switch, etc

[Mike59FR]

Hello, Thank you for your response. I apply on console : backlog template {"NAME":"Sonoff ZigRouter","GPIO":[320,5088,0,5120,257,256,0,0,0,576,0,0,32,0],"FLAG":0,"BASE":18} ; delay1 ; module 0 and the Sonoff reboots automatically. I can't appair in ZHA page. And the LED is not green ( toggle 1 ON or reset Button). It's strange. Frendly Mike. 10:37:22.000 RTC: Synced by NTP 10:37:22.843 RSL: INFO1 = {"Info1":{"Module":"Sonoff ZigRouter","Version":"14.0.0(release-zbbrdgpro)","FallbackTopic":"cmnd/DVES_616A70_fb/","GroupTopic":"cmnd/tasmotas/"}} 10:37:22.856 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-616A70-2672","IPAddress":"192.168.1.7","IP6Global":"","IP6Local":"fe80::4222:d8ff:fe61:6a70%st1"}} 10:37:22.868 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":29}} 10:37:22.880 RSL: RESULT = {"POWER1":"ON"} 10:37:22.881 RSL: POWER1 = ON 10:37:22.883 RSL: RESULT = {"POWER2":"OFF"} 10:37:22.884 RSL: POWER2 = OFF 10:37:25.536 WIF: IPv6 Global 2a01:e0a:b73:a2d0:4222:d8ff:fe61:6a70 10:37:25.883 QPC: Reset 10:37:26.879 RSL: STATE = {"Time":"2024-06-06T10:37:26","Uptime":"0T00:00:08","UptimeSec":8,"Heap":159,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":44},"POWER1":"ON","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Freebox-5CA95C","BSSId":"20:66:CF:E4:93:20","Channel":6,"Mode":"HT20","RSSI":100,"Signal":-48,"LinkCount":1,"Downtime":"0T00:00:03"}} 10:37:27.873 APP: Boot Count 29 10:37:28.568 CFG: Saved, Count 85, Bytes 4096 10:37:33.622 ZIG: rebooting ZNP device 10:37:33.788 ZIG: ZbZNPSent 0xFF x 255 10:37:33.789 ZIG: ZbZNPSent 410000 10:37:38.784 ZIG: timeout, goto label 99 10:37:38.786 RSL: RESULT = {"ZbState":{"Status":99,"Message":"Abort"}} 10:37:38.787 ZIG: Abort 10:37:38.788 ZIG: Stopping (99) [image: image.png] Le mer. 5 juin 2024 à 22:36, Heber Mendoza ***@***.***> a écrit :

…

Firmware looks ok, however your GPIO seems different. Try with this: In Tasmota console apply the following config: backlog template {"NAME":"Sonoff ZigRouter","GPIO":[320,5088,0,5120,257,256,0,0,0,576,0,0,32,0],"FLAG":0,"BASE":18} ; delay1 ; module 0 Reboot device, and share a screenshot of your Tasmota Main Menu and Console logs before/after rebooting. — Reply to this email directly, view it on GitHub <#16957 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFAGRDII3RSRZZBRNVM3PFTZF5ZEPAVCNFSM6AAAAAARSM2T3KVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMOBSGI4DM> . You are receiving this because you commented.Message ID: ***@***.***>

-- Michel W 0641327644

[sfromis]

If you want to use it as a router, you should remove all Zigbee configuration after having flashed the firmware to the Zigbee chip. Tasmota can do nothing when it is running as router instead of coordinator.

Also, you cannot reach it directly from ZHA, Z2M etc. Router means that it only acts a mesh node to improve network topology, not as a device you can interact with.

[xeberth]

You need reach it directly from ZHA, Z2M etc if you want the device work as a router in your network.

You cannot expect that a device that is unknown to your ZigBee network simply start connecting to all the other devices and serve as a router without being discovered by the ZigBee coordinator and being paired.

[Mike59FR]

RE-Hello, My conf : [image: image.png] Le mer. 5 juin 2024 à 22:36, Heber Mendoza ***@***.***> a écrit :

…

Firmware looks ok, however your GPIO seems different. Try with this: In Tasmota console apply the following config: backlog template {"NAME":"Sonoff ZigRouter","GPIO":[320,5088,0,5120,257,256,0,0,0,576,0,0,32,0],"FLAG":0,"BASE":18} ; delay1 ; module 0 Reboot device, and share a screenshot of your Tasmota Main Menu and Console logs before/after rebooting. — Reply to this email directly, view it on GitHub <#16957 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFAGRDII3RSRZZBRNVM3PFTZF5ZEPAVCNFSM6AAAAAARSM2T3KVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMOBSGI4DM> . You are receiving this because you commented.Message ID: ***@***.***>

-- Michel W 0641327644

[xeberth]

Sorry seems you respond from email and image was not attached correctly, try reply directly from GitHub.

[Mike59FR]

Le jeu. 6 juin 2024 à 13:42, sfromis ***@***.***> a écrit :

If you want to use it as a router, you should remove *all* Zigbee configuration after having flashed the firmware to the Zigbee chip. Tasmota can do nothing when it is running as router instead of coordinator. Also, you cannot reach it directly from ZHA, Z2M etc. Router means that it *only* acts a mesh node to improve network topology, not as a device you can interact with. — Reply to this email directly, view it on GitHub <#16957 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFAGRDKMNUHI6HP67TUYNXDZGBDJDAVCNFSM6AAAAAARSM2T3KVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMOBYG43TI> . You are receiving this because you commented.Message ID: ***@***.***>

Maybe stupid question: how to delete the entire Zigbee configuration? You specify: in this mode, this router only acts as a node to improve the network topology. It's my case. But how do Zigbee objects know that they must communicate through this router and not communicate directly with the coordinator? Thank you in advance.

…

-- Michel W

[sfromis]

The Zigbee mesh is supposed to self-organize, instead of you directing each hop. As Tasmota cannot do anything when the Zigbee chip acts as a mesh router, you can basically unconfigure all gpios, especially those named with "Zigbee". If you configured via template, you can unselect the template by instead selecting module generic.

Of course, you could still use the ESP32 for other things Tasmota, like if you want a place to run some Berry code, or do some testing..... Just nothing Zigbee anymore.

[xeberth]

You can't unconfigure all gpios, because you need some of that gpios to turn device in pairing mode to be able to join in your current ZigBee network. If device never enter in pairing mode you cannot be able to join as a router.

[TobiasHorstmann76]

I flashed the device according to the instructions here. All went well. However the pairing is not working with Z2M. At my Sonoff there is only a blue LED. Neither reset trick (6secs etc) nor button1 works. The LED is constant on.

Is it normal there is still the "old" Zigbee Join Button on the UI? Or do I have to reset/delete some more data on the device?

File system looks like this:

[TobiasHorstmann76]

In addition I removed all zigbee configuration:

Blue light is constant on. Neither reset button nor Button1 seems to work (no reaction, no green light :(

[sfromis]

The "ZigRouter" template you tried does not make sense as it is for ESP8266, while the "pro" bridge is ESP32-based. When it comes to CC2652 pairing mode, I've not tried that, but someone earlier in this thread posted about making it work.
#16957 (reply in thread)

[TobiasHorstmann76]

thx sfromis. That was the missing hint - for ESP32 its even simpler with the pairing: Just remove power - then put Z2M into pairing mode - then power ESP32 up and it appears in Z2M:

[mediarath]

After having no success with the previously posted templates and being unable to pair the Bridge with either ZHA or Z2M, I adjusted the template so that I can now integrate the Bridge Pro into both systems without any issues. This has been tested in ioBroker ZHA as well as in Home Assistant ZHA and Z2M.

{"NAME":"Sonoff ZigRouter","GPIO":[0,0,576,0,257,256,0,0,0,0,0,5792,32,0,0,0,0,320,0,0,0,0,0,32,0,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":1}

As @sfromis already mentioned, the template has no actual functionality. The buttons do not work, but the green LED lights up when Power1 is on. However, this is irrelevant for pairing, as is the Reset button, which has no function. All you need to do is disconnect the Bridge from the power, wait a few seconds, and then plug it back in. It will automatically enter pairing mode.

This might help someone who has been facing difficulties. It would be great if someone could test the template and further optimize it if necessary.

[sfromis]

You could use the ESP32 part of the bridge for something else, like Bluetooth, running some Berry automations, or even a small web server. Or to play around with....

[Mike59FR]

Hello, I think your config generates a router. When I unplug it and plug it back in, the time in the ZHA console updates. But impossible to connect Zigbee devices to it. In the Tasmota console, can we please check the IEEE and the Nwk to be sure to target this router ? Is the Zigbee chip in the Sonoff a Texas Instrument chip Only the blue LED remains lit and the Toggle 1 and Toggle 2 buttons do not work. Thanks for your help. [image: image.png] Le mer. 3 juil. 2024 à 13:50, mediarath ***@***.***> a écrit :

…

After having no success with the previously posted templates and being unable to pair the Bridge with either ZHA or Z2M, I adjusted the template so that I can now integrate the Bridge Pro into both systems without any issues. This has been tested in ioBroker ZHA as well as in Home Assistant ZHA and Z2M. {"NAME":"Sonoff ZigRouter","GPIO":[0,0,576,0,257,256,0,0,0,0,0,5792,32,0,0,0,0,320,0,0,0,0,0,32,0,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":1} As @sfromis <https://github.com/sfromis> already mentioned, the template has no actual functionality. The buttons do not work, but the green LED lights up when Power1 is on. However, this is irrelevant for pairing, as is the Reset button, which has no function. All you need to do is disconnect the Bridge from the power, wait a few seconds, and then plug it back in. It will automatically enter pairing mode. This might help someone who has been facing difficulties. It would be great if someone could test the template and further optimize it if necessary. — Reply to this email directly, view it on GitHub <#16957 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFAGRDPYSFCS7BHI4HDOIFTZKPQO5AVCNFSM6AAAAAARSM2T3KVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNBXGI3TS> . You are receiving this because you commented.Message ID: ***@***.***>

-- Michel W 0641327644

[sfromis]

When you've flashed the CC2652 with router firmware, it is no longer visible to Tasmota, but acts on its own as a mesh router. You could use the ESP32 for some non-Zigbee purpose, but not to talk to the Zigbee chip. The Zigbee network should self-organize, but this can take some time.

[Mike59FR]

Hello, I confirm that this template works: {"NAME":"Sonoff ZigRouter XX","GPIO":[320,5088,0,5120,257,256,0,0,0.576,0,0.32,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":18} and that the Sonoff ZB Bridge is transformed into a router. Only the blue LED remains lit and the Toggle 1 and 2 buttons have no effect. Le mer. 3 juil. 2024 à 21:49, sfromis ***@***.***> a écrit :

…

When you've flashed the CC2652 with router firmware, it is no longer visible to Tasmota, but acts on its own as a mesh router. You could use the ESP32 for some non-Zigbee purpose, but not to talk to the Zigbee chip. The Zigbee network should self-organize, but this can take some time. — Reply to this email directly, view it on GitHub <#16957 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFAGRDN6T44LE5IBTC6C2NTZKRIVLAVCNFSM6AAAAAARSM2T3KVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNJSGAYDC> . You are receiving this because you commented.Message ID: ***@***.***>

-- Michel W 0641327644

[sfromis]

While that template is somewhat broken (has two syntax errors with . instead of ,), it includes a lot of irrelevant pins (including weird webcam pins). After the "pro" bridge is flashed with router firmware, you just don't need a template config, as Tasmota can do nothing Zigbee then.

[tequilaj-gh]

Hi, Unfortunately I am struggling to make my Zigbee Bridge Pro became a repeater. If anyone can help:

1. Flash the ZBBridge-P with tasmota32-zbbrdgpro.factory.bin using the usb 2 uart. Success
2. Access the device (SSID is hidden) and configure wifi. Success

Now, from the device's web interface:

1. Upgrade the firmware to tasmota32-zbbrdgpro.bin:
   Firmware Upgrade -> OTA with https://ota.tasmota.com/tasmota32/release/tasmota32-zbbrdgpro.bin -> start upgrade -> device should reboot by itself, I should not see the safe boot title. Success
2. Change the template to ```{"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}
   Configuration->Configure Other, set the template as above, click on activate, then save.
3. Upload the router hex file (SonoffZBPro_router_20220125.hex)
   Tools -> Manage File System -> Select the right file from the pc and then upload
4. Install the hex file
   Tools -> Berry Scripting console -> type:
   import sonoff_zb_pro_flasher as cc cc.load("SonoffZBPro_router_20220125.hex") cc.check() cc.flash()
   then run code.
5. Wait around 5~6 miinutes, from the main screen access Tools -> Console and look for
   RSL: RESULT = {"ZbState":{"Status":99,"Message":"Abort"}
6. Change the template to
   {"NAME":"Sonoff ZigRouter","GPIO":[0,0,576,0,257,256,0,0,0,0,0,5792,32,0,0,0,0,320,0,0,0,0,0,32,0,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":1}
   This will show some buttons on the main screen.

Now, I am not sure from the discussion, if the software and hardware buttons are usefull (i would like that they work, but I was unable to do it), I could pair the device looking for it after a power cycle only. The green light also never turns on, even when it is in pairing mode.

Is this the expected behavior? There a lot of templates around :/

[s-hadinger]

I'm repeating myself here (again).

ZBpro is not meant to be used as a router, and router mode is not supported by the Tasmota staff.

Almost any Zigbee device that is powered by mains (plug, bulb...) act as a router and works reasonably well. Please prefer such options.