ITead "SONOFF Zigbee Bridge Pro" (ZBBridge-P) new CC2652P and ESP32 based Zigbee Gateway to WiFi Bridge

Can you test if original eWeLink firmware is compatible with SonoffLAN custom component over LAN?

Sonoff LAN custom component is available via HACS and does support their previous Zigbee bridge:

Otherwise consider trying flashing/hacking the ESP32 inside it yourself with tasmota32 or ESPHome?

As this is a brand new device, trying to flash it with tasmota32 or ESPHome and get Zigbee working on it even just though remote serial is of course option meant for advanced users, hackers and developers.

I’m pretty sure that the old Zigbee Bridge code won’t work on the “Pro” bridge as it has a different processor (as far as I’m aware) and a different chipset … NotEnoughTech said that there wasn’t a firmware available for it as yet too.



If you mean SonoffLAN custom component then it is not reflashing anything so not dependent on chip.

However, if you mean only flashing existing tasmota-zbbridge or tasmota32 and esphome firmware images to access the Zigbee module on these then of course those already precompiled firmware images will not work as they were either built for the previous ITead Sonoff ZBBridge (with ESP8266/ESP8285) or standard ESP32 dev boards respectively and just as importantly they were built for boards with a slightly different pinouts mapping which will make old images not made for these use the wrong pins.

What I meant was that the new ITead Sonoff ZBBridge is based on a standard ESP32-DOWD-V3 (which I believe is the same chip as the generic Espressif ESP-WROVER-KIT development board and Espressif ESP32 Dev Module / Espressif ESP32-WROVER-E module) so it should, in theory, be possible to just flash a generic esphome and/or tasmota32 build image and try to figure out the pinout used by this device, then start developing from there, so obviously you need to be able to make builds yourself and code some if want to get started playing with Tasmota or ESPHome on this today:

"Tasmota32 is initially developed and tested with the dual core ESP32-D0WD-V3 and later expanded to include single core or PSRAM versions."

Generic builds would of course then not get the Zigbee2Tasmota bridge or serial stream server as that is not included out-of-the-box but it would act as the first proof of concept to see if can even flash Tasmota32 and/or ESPHome. So you would not be able to practically use it yourself unless you learn to make custom builds yourself with external components.

All devices based on the original ESP32 are supported by ESPHome. Simply select ESP32 when the ESPHome wizard asks you for your platform and choose a board type from this link when the wizard asks you for the board type.

What he meant was that there are no precompiled firmware images available for it as yet for this brand new product. But if what digiblur said in this video is correct and the firmware is not locked then there is nothing technically stopping you from building and compiling yourself then flashing that to the ESP32.

Not having locked firmware means that there is nothing holding back developers from hacking these to flash different firmware, and after it it hacked/flashed with different firmware then hackers/developers can try to figure out the pinouts (GPIO pins) used for the Zigbee module. So some coding is needed.

Once those with ESP32 development experince have hacked these and got access to the Zigbee module then they will probably release prebuilt images that anyone can flash themself.

Devs should be able to build own firmware following ZB-GW03 guides as hardware is very similar. See:


What is missing is a pinout mapping which can be figured out by tracing the paths on the PCB boards.

So given that I don’t “code” then it isn’t going to work for me with Home Assistant…

FYI, the Tasmota developer who coded their Zigbee2Tasmota (Z2T) now got one of these, he already started working on adding initial support for it, they are for now using Tasmota’s “tasmota32-nspanel.bin” build as a base because is it based on tasmota32 and have similar build specifications for PSRAM. etc.:

It means that Tasmota and ESPHome do not work today out-of-the-box for these brand new devices, yes. So it means will have to have patience for someone else with coding skills to code all support for it.

Again this is a brand new device so not sure what you expected with out-of-the-box support, but please understand that since it does not have any new unique features it should in theory not take very long.

Can anybody provide all pinouts used to interact with CC2652?
I want to build a firmware for it.

Tasmota developers posted pinout here →

Summery, they initially figured out that this schematic digiblur’s contact at ITead shared look incomplete:

For starters, BSL GPIO should be set to DIO_8 which is not standard and DIO_8 is also used for SPI.

They since also found out that DIO_15 seems connected to PAD#15 on the CC2652 Zigbee module.

As well as that DIO_24 … DIO_29 seem to be connected on different pads.

Keep in mind that if you flash CC2652 firmware with wrong config then that will brick Bootloader (BSL) the Zigbee module and in order to unbrick Bootloader (BSL) will need to manually flash CC2652 with a cJTAG debug adapter, see →

FYI @mercenaruss posted in that he has already made some progress on an ESPHome build for this new ZBBridge-P.

Before attempting this yourself however note that needs to be made clear that users should for now not flash unmodified CC2652P images from Koenkk which the community normally uses as the CC2652P Zigbee module in this ZBBridge-P does not use the standard pins for BSL so flashing an unmodified CC2652 firmware to the Zigbee module will mean that will not be able to flash it again via BSL and will instead need to use a cJTAG probe adapter.

Originally posted by @mercenaruss in

I build a firmware on ESPHome,to be used with ZBBridge-P and Z2M. I managed to flash using cc2538-bsl & ZigStar MultiTool, unchecked AutoBSL. Trigered from webinterface Firmware Update and hit START in ZigStar MultiTool.

Screenshot 2022-05-31 145835

  1. Flash firmware using ESPHOME Flasher
  2. Flash Koenk firmware using ZigStar Multitool
  3. Connect to captive portal and setup your Wifi
  4. Identify ZBBridge IP and setup in Z2M, port 6638 ( port: tcp://ip:6638 )
  5. Enjoy

Working like charm in Z2M. P.S. Will add Reset button capability,buzzer and led indication of status. Also will added to ZigStar GW firmware

1 Like

Thank you for pointing this out.
Community can use modified firmware what is available on tasmota repository.
At the moment,firmware is working properly,without any issues.

1 Like

I managed to identify all GPIO’s used in the board.
You can enjoy Tom Cruise theme on link below:

1 Like

For reference that would be the CC2652 firmware from arendst’s Tasmota repository on GitHub here:

Just ordered a Sonoff Bridge Pro, is it possible to flash trough web interface or is soldering still required? i’m looking to use it for z2m.

GPIO flashing is still required but can be done without soldering, for tips see → ITead “SONOFF Zigbee Bridge Pro” (ZBBridge-P) new CC2652P and ESP32 based Zigbee Gateway to WiFi Bridge · Discussion #14419 · arendst/Tasmota · GitHub

I have pretty stable WiFi, are WiFi Serial coordinators really that unstable? Also some people mention that USB adapters are “faster”, is the response time poor on WiFi coordinators?

FYI, jonasled created an ESPHome configuration for Sonoff ZBBridge-P bridge here on GitLab:

It is in turn based on the ESPHome configuration from thegroove:

1 Like

hi, i hope my configuration helping some one

1 Like

Hey Guys, trying to set-up the ZBBrige-P with ZHA on my HA. There is very little info on the P version, and the guides for the non-P versions do not work “out of the box”. Anyway managed to get to the point where TCP ZBBridge Pro is running fine, however when I try to add it via ZHA I am getting a “failed to connect” error in HA. Tasmota console shows an attempt to connect from my HA IP address, however there it ends.

Any wise suggestions?

I think it is not possible without flashing it before!

@Hedda, i’m so happy, i have only one fix to make with esphome, but i don’t understand why. I need to enter in bsl mode for integrating with ZHA/Z2M

ok, tonight from Italy, upload new code, all now working very well