ZB-GW03 support?

[sheppi72]

What you think about ZB-GW03 board?

Hardware details:

• ESP32 onboard chip (Dual core, 240MHz)
• Zigbee 3.0 coordinator
• Wired ethernet connection

Im not found any official data, but i can buy from several stores:

• EACHEN Zigbee Bridge Pro (ZB-GW03)
• SmartWise Zigbee Bridge Pro

Top	Bottom

[s-hadinger]

It's impossible to say if they will be flashable with Tasmota based on paper description. First the ESP32 must be flashable, i.e. secure boot is not enabled. Second there is no mention about what Zigbee chip is used. This Zigbee MCU needs to be flashable too, which has a low chance.

[Hedda]

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

[sfromis]

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.

[Jason2866]

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

[sfromis]

Works for me

[Hedda]

FYI, I do not own one but collected some more information and a few more pictures for reference:

ZB-GW03 eWeLink Ethernet Zigbee Gateway is based on ESP32 and Silabs EFR32/EZSP Zigbee has been hacked with unofficial Tasmota32.

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

ZB-GW03 v1.0 and ZB-GW03-V1.2 is apparently sold rebranded under many names, including SmartWise and EACHEN brands:

https://www.okosabbotthon.hu/smartwise-zigbee-bridge-pro

https://ewelinkcommunity.net/device-lists/zigbee/eachen-zb-gw03/

https://www.aliexpress.com/item/4000459723849.html

https://www.amazon.de/APP-Fernbedienung-Sprachsteuerung-Funktioniert-Verbindung-Smart-Produkten/dp/B094JKVLNR/

Looks like is it is based on the same "SM-011 V1.0" EFR32MG21 module by CoolKit as ITead uses in their Sonoff ZBBridge Zigbee Bridge:

zigpy/zigpy#586

https://www.coolkit.cn/product/sm-011/

https://github.com/CoolKit-Technologies/DevDocs/tree/master/Zigbee

https://github.com/CoolKit-Technologies/DevDocs/blob/master/Zigbee/SM-011%E5%BA%94%E7%94%A8%E6%8C%87%E5%AF%BC%E4%B9%A6.md

https://translate.google.com/translate?hl=&sl=auto&tl=en&u=https%3A%2F%2Fgithub.com%2FCoolKit-Technologies%2FDevDocs%2Fblob%2Fmaster%2FZigbee%2FSM-011%E5%BA%94%E7%94%A8%E6%8C%87%E5%AF%BC%E4%B9%A6.md

Tip:

Know that the "SM-011 V1.0" module CoolKit is known for being very susceptible to electromagnetic interference due to lack of RF shielding, and a relatively poor antenna design that has not been properly tuned in hardware for that specific integrated PCB antenna.

Because of this, you want to make sure to keep this Zigbee gateway away from other electronic appliances or other sources of electromagnetic interference, as well as try to place it in an optimal location a little bit away from walls, ceilings and floors built with dense building materials.

As always try to as soon as possible to add many mains-powered Zigbee devives closer to the Zigbee gateway so that they can act as Zigbee routers for wireless Zigbee end-devices,

[sfromis]

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.

[Hedda]

FYI, there's now a detailed step-by-step instruction about flashing Tasmota on it for Zigbee2Tasmota (also using with Home Assistant's ZHA):

https://thehelpfulidiot.com/a-wired-sonoff-zigbee-alternative ← ORIGINAL POST

https://thehelpfulidiot.com/update-a-wired-sonoff-zigbee-alternative ← UPDATE 1

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

@vahempio created a firmware image (.bin file) build as linked by thehelpfulidiot which include flashing instructions:

https://github.com/vahempio/Tasmota-for-eWeLink

Again, basic info for experienced Tasmota and Z2T users here :

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

and there is also a discussion about ZB-GW03 (ZBGW03) in Home Assistant community forum here:

https://community.home-assistant.io/t/zb-gw03-ewelink-ethernet-zigbee-gateway-now-hacked-with-tasmota-zbbridge-so-can-be-used-via-mqtt-or-as-a-remote-zigbee-adapter-with-home-assistant-zha/341223

If you want to use it as a remote Zigbee Coordinator adapter for Home Assistant's ZHA integration or Zigbee2MQTT then check out these:

https://www.digiblur.com/2020/07/how-to-use-sonoff-zigbee-bridge-with.html

https://www.digiblur.com/2021/03/zigbee2mqtt-with-sonoff-zigbee-bridge.html

https://www.youtube.com/watch?v=dC1AEyFhmnc

[Hedda]

FYI, Zigbee Router firmware for EFR32MG21 adapters/dongles has now been released by xsp1989 on GitHub. From readme sounds as if as so far been tested with ITead Zigbee 3.0 USB Dongle and an SM-011 based USB adapter.

Since the same "SM-011 V1.0" Zigbee radio modules by CoolKit Technologies is also used inside some Zigbee gateways/hubs like this ZB-GW03 eWeLink Ethernet Zigbee Gateway sold by EACHEN and SmartWise as well as the popular ITead Sonoff ZBBridge, so could perhaps be that the same Zigbee Router firmware could maybe also be used on the SM-011 Zigbee module in all or some of those products as well?

https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware/Zigbee3.0_Dongle/RouterForDongle

https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/Zigbee3.0_Dongle/RouterForDongle/RouterForDongle.gbl

https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/Zigbee3.0_Dongle/RouterForDongle/README.md

xsp1989/zigbeeFirmware#16

xsp1989/zigbeeFirmware#2

[Hedda]

FYI, @xsp1989 has also uploaded/shared a signed Zigbee Router firmware for ZB-GW03 and ITead Sonoff ZBBridge to his google drive here:

https://drive.google.com/file/d/1H-M5CTh_XGGVl2te4vHLQ5SfGPHL6yCS/view?usp=sharing

This is the signed routing firmware used by ZBB, the usage method is the same as the unsigned firmware.

https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/Zigbee3.0_Dongle/RouterForDongle/README.md

Firmware for "SM-011 V1.0" EFR32MG21 Zigbee module by CoolKit inside these has now been tested on Sonoff ZBBridge and ZB-GW03:

https://www.digiblur.com/2022/02/convert-sonoff-zigbee-bridge-to-router-repeater.html

https://github.com/syssi/esphome-zb-gw03/blob/main/docs/router.md

The idea about using these as Zigbee routers is being discussed more specifically for ITead's Sonoff ZBBridge hacked with Tasmota here:

#11536

[sfromis]

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.

[frberry]

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

[sfromis]

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.

[barbudor]

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.

[Hedda]

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

[xsp1989]

https://github.com/xsp1989/ZB-GW03_firmware

We have built tasmota firmware in all languages based on ZB-GW03. The ETH version has wifi turned off by default, and it can be used after power-on without configuring the template. If you need to check the IP address, you can use the mdns tool to scan the network to find tasmota’s gateway, and you can also log in to the background of your router to check the gateway’s IP address. If the ETH version does not meet your needs, you can also use the WIFI&ETH version without additional configuration.

[sammcj]

FYI there's a newer V1.4 variant out now.

I can confirm it works, I needed to first flash it with @xsp1989's firmware using ESP Flasher.

Then I was able to upload the zigbee ota.

Then upgrade to Tasmota 13 using the standard Tasmota firmware.

[rubenvg95]

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}

[sfromis]

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.

[Fantalucio]

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

Ciao,
Lucio

[rubenvg95]

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.

[Jjarrard]

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)

[Fantalucio]

Hi,
my ZB-GW03 v1.4 works in ZHA only after sending through tasmota console the command "TCPBaudrate 115200".

Ciao,
Lucio

FYI there's a newer V1.4 variant out now.

I can confirm it works, I needed to first flash it with @xsp1989's firmware using ESP Flasher.

Then I was able to upload the zigbee ota.

Then upgrade to Tasmota 13 using the standard Tasmota firmware.

[derlbear]

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?

[Fantalucio]

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"

[mvadu]

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

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

[mvadu]

I bought a pre flashed ZB-GW03. This came with v1.4 board and came with 12.5.0(tasmota) with build date of 2023-07-03T20:38:42. But it doesn't look like its from @xsp1989 branch since it does enable WiFi. There is no way for me to confirm the EFR32MG21 firmware version. I am not able to just use the OTA to upgrade the Tasmota version either. @xsp1989 in your repo I see only 12.x had a ETH only firmware, in 13.x its WiFi+Eth. Are you planning to add ETH only there?

[ortegafernando]

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.

[sfromis]

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.

[ortegafernando]

Hi @sfromis thanks a lot !!!

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

[sfromis]

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

[xsp1989]

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

[ortegafernando]

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

Sorry, then what is the difference between tasmota32-zbbrdgpro.bin and tasmota32-zigbeebridge.bin ? I thought that ZB-GW03 was "zigbee bridge pro". But now I am very confused,

Thanks

[sfromis]

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.

[xsp1989]

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

[ortegafernando]

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

Thanks, I am now confused with this version. I supposed that it is a kind of beta version with some improvements that will be add to tasmota official github in future, isn't it? Thanks

[xsp1989]

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

[ortegafernando]

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

[tsgxwolf]

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

[sfromis]

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.

[tsgxwolf]

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.

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? I saw in tasmota's description that it mentioned that matter support will be added to zigbee devices later. Does it mean that,this is just because tasmota officially does not provide support for linking zigbee bridge and matter for now, and I just need to wait?

[s-hadinger]

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

[sfromis]

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.

[KrabKley]

I have a coordinator, sonoff usb zigbee 3.0 dongle e and everything works fine with HAOS.
But 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? Is there any way to switch it to this mode. (turn off the coordinator)

[Hedda]

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

[KrabKley]

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 (

[barbudor]

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

[sfromis]

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.

[Hedda]

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

[robvanoostenrijk]

The latest Z2M requires a never EZSP protocol version besides what comes on this device:

z2m: Coordinator firmware version: '{"meta":{"maintrel":"10 ","majorrel":"6","minorrel":"7","product":8,"revision":"6.7.10.0 build 423"},"type":"EZSP v8"}'

Has anyone succesfully flashed an updated newer Zigbee firmware then ncp-uart-sw_6.7.10_115200.ota?

From what I understand the zbdonglee Zigbee firmware should be compatible if the ZB-GW03 accepts unsigned firmware:
https://github.com/darkxst/silabs-firmware-builder/tree/main/firmware_builds/zbdonglee

However, I have no way to recover from a bad flash. Did something test if the ZB-GW03 can support 7x series Zigbee firmware?

[sfromis]

This thread is talking about that: #21361

[abate]

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

[sfromis]

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.

[abate]

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.

[abate]

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

[radudorurus]

Need help.
Got ZB-GW03 v1.4 from ali some time ago.

• updated ZB chip as instructed
• the Tasmota FW was v12 I think.
• did the config, eth only, ZHA, paired one HUE plug, worked
• after restart no more working, the paired device disappeared
• yes I did also the rule to start TCP and switch template.
• wanted to switch to Z2M
• could not upgrade over OTA or by bin file web interface because of the signature issue.

Today I said I'll give another chance.
Used Tasmota web installer witt custom bin drag and drop.
But any GW03 fw v12...14 ends with bootloop and invalid header messages in console.
Tried the factory bins without success.
Any clues?

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
invalid header: 0x204c4257
invalid header: 0x204c4257
invalid header: 0x204c4257
invalid header: 0x204c4257
invalid header: 0x204c4257
invalid header: 0x204c4257
invalid header: 0x204c4257
ets Jul 29 2019 12:21:46

[sfromis]

Looks like you flashed the wrong file, the correct one should have a name like tasmota32.factory.bin. What exact file name did you flash?

[radudorurus]

The device was working previously.
I said let's start from scratch and tried tasmota32-zigbeebridge.factory.bin

But it seems solved.
Flashed the tasmota32 solo from official web installer
Got it working, connected to wifi
Uploaded the latest ZB-GW03 fw bin on webinterface and now it is working.
Trying to get the LAN working but I think the version 14.2.0 does not have LAN driver

[sfromis]

Tasmota 14.2 on ESP32 does have Ethernet driver, as long as you make sure to do the needed configuration, including pins. Works for me.

[radudorurus]

Yes It had but does not get IP from DHCP server.
Set it manually, static and does not work.