FYI, seems like ZB-GW03 has been hacked with Tasmota32 and look to support same Tasmota and Silabs firmware as Sonoff ZBBridge

https://templates.blakadder.com/ewelink_ZB-GW03

Indeed, got the device working (not me doing the hacking). A precompiled binary is in the works to make it simpler. The device is basically the Sonoff ZbBridge, modified for ESP32, Ethernet and USB-C socket.

Please give me feedback if this unofficial build of Tasmota ZigbeeBridge is working or not. https://github.com/tasmota/install in section special

That RF design is a good reason for using Ethernet and turning off Wifi, which is a clear source of EMI on the same 2.4 GHz frequency range.

If you want to connect it to ZHA or Z2M, do not flash it as a router, but as a coordinator. A router depends on reaching a coordinator, instead of doing more than being part of the mesh.

Thx a lot for your answer,
I agree with you... but I have already a coordinator (USB-Key sonoff) and I need to get measures in my cellar where there is no Zigbee. With Z2M, I can not have 2 coordinators.
So, my idea was to use a CPL plug with a ZB-GW03 as router to extand my Zigbee network via ethernet.
Here is my problem... Please, feel free to tell me if it exists a simpler solution to my problem! :))

François

The "simpler" solution is to realize that what you want is not how Zigbee works.

If you already have a coordinator, that is the device for ZHA or Z2M to talk to. A Zigbee router is not connected to those systems, and it is useless to have Ethernet on a router device, as this is is only part of the Zigbee mesh. You cannot extend the Zigbee mesh via Ethernet.

You gain nothing by paying extra for features not applicable to a simple router, which basically just as well could be a plug or similar.

If zigbee from your usb dongle doesn't reach your cellar, why not just get another coordinator there like a tasmotized sonoff zbbridge pro which has ethernet and which will push to your MQTT broker.
You will just have 2 independant zigbee networks.

By the way the English for "CPL" (courant porteur en ligne) Seems to be either PLC (power line communication) or BPL (broadband over power line). I never got that working reliably at home.

@frberry It is not possible to what you want the way you describe you want to achieve by connecting a Zigbee Router over Ethernet. You really only have the option to either create two separate Zigbee networks using two Zigbee Coordinator adapter or you can extend the Zigbee network mesh wirelessly using Zigbee Router devices via the Zigbee RF protocol.

With Z2M, I can not have 2 coordinators.

You have to run two separate instances of Zigbee2MQTT or ZHA, with each Z2M/ZHA instance having their own dedicated Zigbee Coordinator that runs its own separate Zigbee network that knows nothing about each other at the Zigbee level, instead you utilize them, both at the application layer using MQTT other application/message protocol for integration.

So, my idea was to use a CPL plug with a ZB-GW03 as router to extand my Zigbee network via ethernet.

That is not how it works, it simply can not do that. You can not extend your Zigbee network by connecting to a Zigbee router via Ethernet. The Zigbee network does tunnel over your Ethernet network. So while you can connect to Tasmota over Ethernet, you can not pair the Zigbee network over Ethernet, just because you run Tasmota on the ESP chip it does not create a tunnel for the Zigbee protocol.

Thanks a lot!

I flashed with this firmware and seems to be working. The only problem now it's the huge packet loss using Wifi connection (10% or more)... anyone has the same issue?

I'm not using ZHA, standalone mode (MQTT to SERVER)

Program Version | 13.3.0.3(zig_bridge32)
:{"Status":55,"Version":"6.7.10.0","Protocol":8,"Stack":2}
19:31:40.065 RSL: RESULT = {"ZbState":{"Status":55,"Version":"6.7.10.0","Protocol":8,"Stack":2}19:31:40.065 RSL: RESULT = {"ZbState":{"Status":55,"Version":"6.7.10.0","Protocol":8,"Stack":2}

Running a ping -c 100 ip.add.re.ss on the device:
100 packets transmitted, 100 received, 0% packet loss, time 99141ms
Also using precompiled Tasmota 13.0.3.3, and the test was not using Ethernet.

If you have much Zigbee activity at the same time (I had not), there could be a risk of interference of two 2.4 GHz radios in close proximity. While worse with same Channel number, proximity as such is not great, even if Wifi should still run ok with 10% packet loss on small packets. Of course, the usual details like signal strength, congestion and RF noise sources can be major factors too.

Obviously, using the Ethernet capabilities of the device can be recommended for getting a better connection.

@rubenvg95
I agree with @sfromis and I confirm: no packet loss with ethernet connection.

Ciao,
Lucio

Problem it's on Wifi, no ethernet.

After a couple of hours, I cannot even access to web GUI (very slow access). I tested another board (not 1.4 version) on same location, with same wifi, and I'm not suffering this problem. Probably it's a hardware problem.

This method worked for me, thank you so much, I bricked my 1.4 doing an upgrade and these three steps worked like a charm.

For anyone needing pins
usb programmer -> Board
3.3 -> 3.3
gnd -> gnd
rx -> tx
tx -> rx
And on the 1.4 board short the gnd and IO0 when plugging in the usb programmer
I just left mine shorted until after the ESPFlasher step (I forgot to remove it)

Hi, can you please explain your steps?

1. install xsp1989's firwamre
2. upload zigbee ota
3. upgrade to Tasmota 13 standard firmware
4. backlog template {"NAME":"ZHA-bridge","GPIO":[0,0,5472,0,5504,0,0,0,5793,5792,320,544,5536,0,5600,0,0,0,0,5568,0,0,0,0,0,0,0,0,608,640,32,0,0,0,0,0],"FLAG":0,"BASE":1} ; module 0
5. TCPBaudrate 115200

Am I missing something?

Also applied that rules, but I don't know if it's mandatory:
"backlog rule1 on system#boot do TCPStart 8888 endon ; rule1 1 ; tcpstart 8888"
"backlog rule2 on system#boot do Wifi 0 endon ; rule2 1"

On the Zigbee2mqtt I had to add this to get it working

serial:
  port: tcp://zb-gw03-eth.local:8888
  adapter: ezsp

HI, I have bought an already flashed ZG-GW03 with this important info:

00:00:00.003 HDW: ESP32-D0WD-V3 
00:00:00.108 TFS: File '.drvset003' not found
00:00:00.126 Project tasmota - Tasmota Version 12.5.0(tasmota)-2_0_7(2023-07-03T20:38:42)
00:00:04.166 ZIG: Resetting EZSP device
02:50:24.997 RSL: RESULT = {"ZbState":{"Status":1,"Message":"EFR32 EZSP booted","RestartReason":"Power-on","Code":2}}
02:50:25.097 RSL: RESULT = {"ZbState":{"Status":55,"Version":"6.7.9.0","Protocol":8,"Stack":2}}

Seeing that info I see that I have already the last version of zigbee chip: 6.7.9.0 (https://github.com/arendst/Tasmota/blob/development/tools/fw_SonoffZigbeeBridge_ezsp)

I also have 12.5.0 version of tasmota, but I dont have OTA url in my firmware upgrade webui.

What is exactly the firmware update OTA url? Master? DEvelopment? and which?
Am I correct about that I have the last version of zigbee?

Thanks a lot.

The suitable Tasmota firmware build is tasmota32-zigbeebridge.bin, and release or development should both be fine, without much difference with the latest development build. And yes, 6.7.9 is indeed the lastest tested and known-to-work variant.

Hi @sfromis thanks a lot !!!

Sorry, do you mean "tasmota32-zbbrdgpro.bin" ?

No, I meant the binary I wrote, however it is instead found in
https://github.com/Jason2866/Tasmota-specials/tree/firmware/firmware/tasmota32/other

https://github.com/xsp1989/ZB-GW03_firmware/tree/master/tasmota
If you need the latest firmware for ZB-GW03, please follow this

tasmota32-zbbrdgpro.bin is for CC2652-based devices, not EZSP-based devices. The ZB-GW03 is more like the non-"pro" Sonoff Zigbee bridge, just with ESP32 and Ethernet instead of ESP8266 and only Wifi.

https://github.com/xsp1989/ZB-GW03_firmware/tree/master/tasmota
If you need the latest firmware for ZB-GW03, please follow this

This is not a beta version, this is a firmware built for ZB-GW03 based on the officially released version.

Great thanks a lot. I will read all information about your already made version, great!

excuse me,I'd like to know does this supports matter or not?

From what I can see, the Tasmota support for acting as a Matter device is not included in those binaries from xsp1989, which fits well with Zigbee and Matter being completely unrelated features of Tasmota. It should be possible to do a custom build including both, but that does not give you any integration of the features.

Matter to Zigbee is not planned in the following weeks. You'll have to wait a little longer

So, it means that even if I build a custom build including both, I still can't connect the zigbeee device to matter thought tasmota, right?

Well, you can if you do the bridging yourself, picking up payloads from one side, and issuing matching commands to the other side.

I need to expand zigby's network to another house where there is Wi-Fi and a network. To do this, I bought this device in the hope that it will work in router mode?

That is not possible. You can not tunnel the Zigbee traffic over an IP network. So no, you can not connect to a Zigbee Router over WiFI or a LAN network to extend your Zigbee network.

You can only tunnel the serial communication protocol between the Zigbee gateway application and a the serial interface of a Zigbee Coordinator.

Is there any way to switch it to this mode. (turn off the coordinator)

You can flash the Zigbee chip with Zigbee Router firmware which makes it possible to pair/join directly as a Zigbee Router via Zigbee just like any other Zigbee Router device, (but not over an IP network like you asked/want).

PS: Off-topic but FYI; the Thread protocol has a feature to tunnel Thread traffic over an IP network to extend a Thread network, (but again, Zigbee does not).

Damn, I understand you. I thought it would be easier. Thank you.
ps. Then I will buy SONOFF ZBMINI Zigbee and install an external antenna there and then maybe the signal will become stronger and I will get to another house. At the moment, the signal quality between the two SONOFF ZBMINI Zigbee is 29/28 (

You still can create indépendant zigbee networks each reporting to your HA
It doesn't have to be a single network
Just pair each device to the closest coordinator

And the coordinator could (like with Tasmota) bridge the communication to/from MQTT. Note that this does not mean an ability to make a Zigbee end device appear in another Zigbee mesh network.

Then I will buy SONOFF ZBMINI Zigbee and install an external antenna there and then maybe the signal will become stronger and I will get to another house. At the moment, the signal quality between the two SONOFF ZBMINI Zigbee is 29/28 (

@KrabKley Tip is to either create two seperate Zigbee networks (each with its own Zigbee Coordinator and use MQTT to present all devices at the application level) or simply add many more and better Zigbee Router devices to your existing Zigbee network. For that you can for example easily re-purpose Sonoff ZBDongle-E and Sonoff ZBDongle-P Zigbee USB adapters with external antennas as Zigbee Routers by flashing with such firmware then power via USB-chargers. I recommend reading and following my best practice guide here -> https://community.home-assistant.io/t/zigbee-networks-how-to-guide-for-avoiding-interference-and-optimize-for-getting-better-range-coverage/515752

This thread is talking about that: #21361

Hello,
so I just flashed my ZB-GW03 with the latest tasmota bridge firmware

Program Version 14.1.0.4 (3c88411-zig_bridge32)
Build Date & Time 2024-08-02T18:06:37
Core/SDK Version 3_0_4/5.1.4.240801

it runs, but when I try to activate the serialtcp connection with

backlog rule1 on system[#boot] do TCPStart 8888 endon ; rule1 1 ; template {"NAME":"Sonoff Zigbee Pro","GPIO":[0,0,576,0,480,0,0,0,0,1,1,5792,0,0,0,5472,0,320,5793,5504,0,640,608,32,0,0,0,0,0,1,0,0,0,0,0,0],"FLAG":0,"BASE":1} ; module 0

it applies the configuration, starts the server on port 8888, accepts connections, but then reboots and get back to a default configuration ( I've to put back my wifi pass )...

not sure if I'm doing something silly here...

Yes, you are doing something silly, configuring a template meant for the Sonoff Zigbee Bridge pro for the ZB-GW03. And your rule is using a trigger syntax you invented, not something valid with Tasmota.

Ah ! Thank you for your answer:)

ok. silly indeed.

So digging a bit more I ended up on the tasmota documentation.
https://tasmota.github.io/docs/Serial-to-TCP-Bridge/#commands

00:00:00.001 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.030 UFS: FlashFS mounted with 304 kB free
00:00:00.043 CFG: Loaded from File, Count 18
00:00:00.052 QPC: Count 1
00:00:00.056 I2C: Bus1 using GPIO32(SCL) and GPIO33(SDA)
00:00:00.088 BRY: Berry initialized, RAM used 3515 bytes
00:00:00.115 ZIG: ZBBridge EEPROM found at address 0x50
00:00:00.120 Project tasmota - Tasmota Version 14.0.0(tasmota)-3_0_0(2024-05-27T19:28:52)
00:00:04.154 ZIG: Resetting EZSP device
04:54:34.276 RSL: STATE = {"Time":"2024-08-03T04:54:34","Uptime":"0T00:00:09","UptimeSec":9,"Heap":138,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":38},"Wifi":{"AP":1,"SSId":"xxxx","BSSId":"xxxxxxxxxx","Channel":1,"Mode":"HT20","RSSI":78,"Signal":-61,"LinkCount":1,"Downtime":"0T00:00:03"}}
04:54:40.675 ZIG: Resetting EZSP device
04:54:41.976 RSL: RESULT = {"ZbState":{"Status":1,"Message":"EFR32 EZSP booted","RestartReason":"Power-on","Code":2}}
04:54:42.076 RSL: RESULT = {"ZbState":{"Status":55,"Version":"7.4.3.0","Protocol":13,"Stack":2}}
04:54:42.079 RSL: RESULT = {"ZbState":{"Status":98,"Message":"Only EZSP protocol v8 is currently supported"}}
04:54:42.092 RSL: RESULT = {"ZbState":{"Status":99,"Message":"Abort"}}
04:54:42.094 ZIG: Abort
04:54:42.094 ZIG: Stopping (99)
16:15:09.835 CMD: TCPStart 8888
16:15:09.850 RSL: RESULT = {"Command":"Unknown"}

The doc says that TCPStart should be a supported command.

I'm probably very confused.

After a bit of fiddling I think I got somewhere.
I first installed the ncp-uart-nsw_6.7.9_115200.ota
this solved the

04:54:42.094 ZIG: Abort
04:54:42.094 ZIG: Stopping (99)

problem above.

Then I assigned the GPIOs for tcp Rx and Tx

Now TCPStart 8888 works and I get 16:37:18.763 TCP: Got connection from 192.168.2.4 without errors...

Now lets' see if I can get zigbee2mqtt working with this

@derlbear I successfully flashed https://github.com/xsp1989/ZB-GW03_firmware/blob/master/tasmota/v14.2.0/firmware/tasmota32-ZB-GW03-EN.bin but when I want flash https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/ZigbeeBridge_SM-011-signed/ncp-uart-sw_7.4.3.0_115200.ota I get error Upload Failed
Invalid file signature

To upload the Zigbee firmware, you need to first configure the gpios (apply the right template)

@sfromis Is there any guide how to do it? Thanks

https://templates.blakadder.com/ewelink_ZB-GW03

but when I want flash https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/ZigbeeBridge_SM-011-signed/ncp-uart-sw_7.4.3.0_115200.ota I get error Upload Failed
Invalid file signature

Also make sure that you download the correct file (i.e. the raw file) and not just the webpage (which is a common mistake people make when trying to download raw files from GitHub). You need to download from the link marked as "Raw" to the right on the code page:

FYI, there are more tips and links here too -> https://community.home-assistant.io/t/zb-gw03-ewelink-ethernet-zigbee-gateway-now-hacked-with-esphome-and-tasmota-so-can-be-used-via-mqtt-or-as-a-remote-zigbee-coordinator-lan-adapter-with-home-assistants-zha-integration-or-zigbee2mqtt/341223/

That includes these three links Home Assistant community member thehelpfulidiot series of step-by-step guides for these which includes details instructions (that are still valid even if they are getting a bit old now):

• https://thehelpfulidiot.com/a-wired-sonoff-zigbee-alternative
  • https://thehelpfulidiot.com/update-a-wired-sonoff-zigbee-alternative
    • https://thehelpfulidiot.com/update-2-a-wired-sonoff-zigbee-alternative

Note that if you want to use it with the built-in native Zigbee2Tasmota (Z2T) Zigbee Gateway implementation inside Tasmota then Tasmota themselves hosts copies of tested (older) versions of EmberZNet NCP (EZSP) firmware image for the EFR32MG21 chip because those older versions are the only ones that been tested.

However if you are trying to flash a newer EmberZNet NCP (EZSP) firmware image to the Silicon Labs EFR32 (EFR32MG21) SoC chip in order to use it as a remote Zigbee Coordinator adapter with the latest Zigbee2MQTT or Home Assistant's ZHA integration then note that it needs to be a newer signed EmberZNet NCP firmware image that specifically matches the signature of the previous EmberZNet firmware for the SM-011 module used inside these, and fact is that the only one we know of who been able to sign EmberZNet firmware for it is xsp1989 so you can only use his signed firmware images for the ZB-GW03 (and the Sonoff ZBBridge from ITead) -> https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware/ZigbeeBridge_SM-011-signed