Plugin open to Silicon Labs coordinator

[pipiche38]

The plugin is now compatible with Silicon Labs coordinators. Thanks to Elelabs for their sponsorship

https://elelabs.com/products/elelabs-usb-adapter.html

[Hedda]

FYI, the general tip when buying an "EZSP" compatible adapter is to buy one based on one of the newer Silicon Labs EFR32 chips if possible.

Adapters based on EFR32MG12, EFR32MG13, EFR32MG21 or EFR32MG24 + EmberZNet Zigbee NCP 6.7.8 firmware are recommended today.

All Silicon Labs chip based adapters should work long as updated between Silabs EmberZNet 6.7.x to 7.0.x Zigbee NCP firmware.

It is however advised to buy one based on EFR32MG13 or newer and buying even newer should obviously be more future-proof:

• ITead Sonoff Zigbee 3.0 USB Dongle Plus model “ZBDongle-E” (based on EFR32MG21)
  • https://itead.cc/product/zigbee-3-0-usb-dongle/
• Elelabs Zigbee USB Adapter (ELU013, based on EFR32MG12) (based on EFR32MG13P)
  • https://elelabs.com/products/elelabs-usb-adapter.html
• Elelabs Zigbee Raspberry Pi Shield (ELR023, based on EFR32MG13P)
  • https://elelabs.com/products/elelabs-zigbee-shield.html
• POPP ZB-STICK (701554) (rebranded Elelabs ELU013, based on EFR32MG12)
  • https://www.popp.eu/zb-stick/
• POPP ZB-SHIELD (701561) (rebranded Elelabs ELR023, based on EFR32MG12)
  • https://www.popp.eu/zb-shield/
• Zigbee 3.0 dongle barebone model "9888010100045" adapter from ITead (based on EFR32MG21). Note that the board missing EMF shielding and is reportingly using poorly tuned circuit board antenna so signal reception has been reported to be very sensitive to interference unless use long USB extension cable and/or add some basic shielding on your own) .
  • https://www.facebook.com/watch/?v=262086502015726
• USB-stick or a DIY ESP32/ESP8266 based bridge/gateway using "SM-011 V1.0" (ZYZBP008) module from CoolKit-Technologies. (based on EFR32MG21). Note that the "SM-011 V1.0" module missing EMF shielding and is reportingly using a poorly tuned circuit board antenna so signal reception has been reported to be very sensitive to interference unless use a very long USB extension cable that is properly shielded and/or maybe even add some basic shielding to the board itself on your own). Those include:
  • ZB-GW04 USB dongle (a.k.a. easyiot stick)) which uses EFR32MG21 based "SM-011 v1.0" Zigbee module from CoolKit-Technologies.
    • https://www.aliexpress.com/item/1005002791666029.html
  • Modkam DIY USB dongle (description only in Russian so use a translator) (as well see discussion at Silicon Labs EFR32MG21 based SoC modules, dongles/sticks, and gateways or bridges zigpy/zigpy#586) which also uses EFR32MG21 based "SM-011 v1.0" Zigbee module from CoolKit-Technologies.
    • https://modkam.ru/?p=1889
• Defaro Sprut Stick 2 Pro (based on EFR32MG21. Description in Russian, use a translator)
  • https://spruthub.ru/device/defaro-sprut-stick-2-pro
• EByte E180-ZG120B dev board if bootloader is first reflashed to standard Silabs Gecko Bootloader via JTAG (based on EFR32MG12), see zigpy/zigpy#584 and https://github.com/zha-ng/EZSP-Firmware
• DIY "Billy EZSP" ESP32 or ESP8266 based bridge/gateway using IKEA TRÅDFRI ICC-A-1 Module ripped from an IKEA Tradfri Series device with hacked firmware
  • https://github.com/MattWestb/IKEA-TRADFRI-ICC-A-1-Module
• tube0013 style DIY open-source-hardware Zigbee to Ethernet gateways based on ESP32 running ESPHome with serial-bridge configuration.
  • https://github.com/tube0013/tube_gateways
  • New Zigbee to Ethernet "DIY" Corrdinator zigpy/zigpy#584
  • https://www.tubeszb.com/shop/coordinators/2
• Tube's EFR32 Series2 Ethernet/USB Gateway (based on ESP32 with MGM210P Zigbee radio module with EFR32MG21)
  • https://www.tubeszb.com/product/efr32_gw_2/6?cp=true&sa=false&sbp=false&q=false&category_id=2
  • https://github.com/tube0013/tube_gateways
• Tuya TYGWZ-01 / Lidl Silvercrest Smart Gateway (Zigbee bridge with wired Ethernet port) hacked with serial-to-ip server.
  • https://paulbanks.org/projects/lidl-zigbee/ha.html
  • https://paulbanks.org/projects/lidl-zigbee/
  • https://community.home-assistant.io/t/hacking-the-silvercrest-lidl-tuya-smart-home-gateway/270934
  • https://github.com/banksy-git/lidl-gateway-freedom
  • Tuya TYGWZ01 Smart Gateway with EZSP 6.7.8.0 ! ! zigpy/zigpy#650
• ZB-GW03 eWeLink Ethernet Zigbee Gateway (also sold rebranded under EACHEN and SmartWise brands + others)
  • 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
• Sonoff ZBBridge Zigbee WiFi Bridge gateway re-flashed with Tasmota or ESPHome (though note this hardware is not recommended as a remote Zigbee Coordinator since EZSP serial connection over Wi-Fi does not make for a stable solution).
  • https://community.home-assistant.io/t/sonoff-zbbridge-sonoff-zigbee-bridge-from-itead/187346
• Xiaomi Gateway 3 (ZNDMWG03LM and ZNDMWG02LM) on stock firmware but hacked with AlexxIT project (though note this hardware is not recommended as a remote Zigbee Coordinator since EZSP serial connection over Wi-Fi does not make for a stable solution).
  • https://github.com/AlexxIT/XiaomiGateway3#zigbee2mqtt-mode
• Cortet ZM3588S-USB or Cortet ZM357S-USB EM35x USB Sticks by CEL (note that these are based on Silabs much older EM3588 and EM357 "Ember" families of chips so not recommended for new purchase as no new firmware is maintained and released for these old hardware chips).
  • https://github.com/walthowd/husbzb-firmware and https://github.com/grobasoz/zigbee-firmware
• Nortek GoControl QuickStick Combo Model HUSBZB-1 (note that this is based on Silabs much older EM3581 "Ember" family chip so not recommended for new purchase as no new firmware is maintained and released for these old hardware chips).
  • https://github.com/walthowd/husbzb-firmware and https://github.com/grobasoz/zigbee-firmware
• Bitron Video/Smabit BV AV2010/10 USB-Stick (note that this is based on Silabs muck older EM3587 "Ember" family chip so not recommended for new purchase as no new firmware is maintained and released for these old hardware chips).
  • https://github.com/walthowd/husbzb-firmware and https://github.com/grobasoz/zigbee-firmware
• Telegesis ETRX357USB if reflashed (note that this is based on Silabs much older EM357 / EM357x "Ember" family chip so not recommended for new purchase as no new firmware is maintained and released for these old hardware chips).
  • https://github.com/walthowd/husbzb-firmware and https://github.com/grobasoz/zigbee-firmware

With right firmware should work with any Silicon Labs EFR32 Zigbee NCP SoC from EFR32MG2x/MGM2x0 and EFR32MG12/MGM1x series:

• https://www.silabs.com/wireless/zigbee/efr32mg24-series-2-modules (not released yet due to the current worldwide chip shortage)
• https://www.silabs.com/wireless/zigbee/efr32mg24-series-2-socs
• https://www.silabs.com/wireless/zigbee/efr32mg21-series-2-modules
• https://www.silabs.com/wireless/zigbee/efr32mg21-series-2-socs
• https://www.silabs.com/wireless/zigbee/efr32mg13-series-1-modules
• https://www.silabs.com/wireless/zigbee/efr32mg13-series-1-socs
• https://www.silabs.com/wireless/zigbee/efr32mg12-series-1-modules
• https://www.silabs.com/wireless/zigbee/efr32mg12-series-1-socs

Please note that the first EFR32MG1 and old EM35x/EM35xx chips will not get support for the upcoming EmberZNet 7.x firmware/SDK, (Silicon Labs had planned to release that SDK much sooner but upcoming EFR32MG23 and EFR32MG24 series delay caused later release).

Firmware can be updated with example Elelabs EZSP Firmware Update Utility or the Zigbee firmware updater image by walthowd:

https://github.com/Elelabs/elelabs-zigbee-ezsp-utility

https://github.com/walthowd/husbzb-firmware

https://github.com/grobasoz/zigbee-firmware/

https://github.com/xsp1989/zigbeeFirmware/

https://github.com/zha-ng/EZSP-Firmware

https://github.com/MattWestb/EFR32-FW

Note! Baud rate configuration setting will depend on the firmware you use, as some use 115200 and others 57600 baudrate.

Direct link to zigpy wiki page where MattWestb documented recommended application firmware version for different EZSP Coordinators:

https://github.com/zigpy/zigpy/wiki/Coordinator-Firmware-Updates#recommended-firmware-version-for-ezsp-coordinators

PS: Remember to always use a long USB extension cable with it to avoid EMF/EMI regardless of which Zigbee Coordinator you are using!

[NilsBohr]

@Hedda
I don't agree with what you are saying. I think you only confuse the users.

Meaning adapters based on EFR32MG12, EFR32MG21, or EFR32MG24, and recommended firmware is EmberZNet Zigbee NCP 6.7.8 now, (EFR32MG13 is also technically compatible but they have less flash storage and less RAM so not recommend due to not being future-proof).

Where did you get this information about MG13? What are you basing your assumptions on?

There is no difference noticeable in any shape or form to the end user, when using MG13.
In fact as long as you are not using older EM35* SoC you will not notice any difference. You can use any EFR32MG based microcontrollers, including slightly older MG1 series.

P.S. ELR023 are MG13 based.

P.S2: Fantastic summary overall! I probably was just way too triggered. Appologies

[NilsBohr]

@Hedda

Understand that EFR32MG12/MGM12 series and older chips will not get support for the upcoming EmberZNet 7.x firmware/SDK, (Silicon Labs had planned for that to be released sooner but the upcoming EFR32MG23 and EFR32MG24 series has been delayed).

I have just checked the SDK 7.x.
EFR32MG12, EFR32MG13, EFR32MG21, EFR32MG24 all have support in SDK 7.x
EFR32MG1, EM35* does not have support in SDK7.x

Realistically future firmware updates for any products in your list based on MG12,MG13,MG21, MG24 only depend on the manufacturer/community will to release new firmware updates for at least next 3 years.

[Hedda]

OK I will change my original post above.

As I understand the size of RAM and flash are the two leading factors in limiting how many Zigbee 3.0 devices a coordinator can support?

E.i. on paper an EFR32MG13 with NCP Zigbee Coordinator will not be able to support as many Zigbee 3.0 devices as those others?

FYI, my assumption was made based purely on Silabs specification which shows EFR32MG13 having max 512kB flash and max 64kB RAM:

https://www.silabs.com/wireless/zigbee/efr32mg13-series-1-modules
https://www.silabs.com/wireless/zigbee/efr32mg13-series-1-socs

Compared to specs of the others, which show EFR32MG13, EFR32MG21, EFR32MG24 have at least max 1024kB flash and max 96kB RAM:

https://www.silabs.com/wireless/zigbee/efr32mg24-series-2-modules (not released yet due to the current worldwide chip shortage)
https://www.silabs.com/wireless/zigbee/efr32mg24-series-2-socs
https://www.silabs.com/wireless/zigbee/efr32mg21-series-2-modules
https://www.silabs.com/wireless/zigbee/efr32mg21-series-2-socs
https://www.silabs.com/wireless/zigbee/efr32mg12-series-1-modules
https://www.silabs.com/wireless/zigbee/efr32mg12-series-1-socs

[Hedda]

@NilsBohr By the way, the posts here under https://github.com/zigbeefordomoticz/Domoticz-Zigbee/discussions are just another type of community forum for informal discussions and not at all any "official" documentation of the Zigbee Plugin for Domoticz or Domoticz itself.

For "official" documentation you want to instead checkout the readme and wiki's:

https://github.com/zigbeefordomoticz/Domoticz-Zigbee/blob/stable6/readme.md

https://zigbeefordomoticz.github.io/wiki/

https://github.com/zigbeefordomoticz/Domoticz-Zigbee/wiki

https://www.domoticz.com/wiki/ZigbeeForDomoticz

PS: Regardless, I am also not a member of this project myself. I am only a hobby technology evangelist promoting Zigbee in open-source.

[NilsBohr]

@Hedda

As I understand the size of RAM and flash are the two leading factors in limiting how many Zigbee 3.0 devices a coordinator can support?
E.i. on paper an EFR32MG13 with NCP Zigbee Coordinator will not be able to support as many Zigbee 3.0 devices as those others?

That is decided by the Firmware developer and SDK limitations, when compiling the Firmware.
You can see it for example in a nice table for some of the Open Source firmwares:
https://github.com/zha-ng/EZSP-Firmware/tree/master/Elelabs-ELU013#efr32mg13p-v8-676-sw-115200

Which means it is defined purely by how much effort/thought/care the company/community gave to the specific hardware. And on paper any company/enthusiast can release the latest and greatest MG24 product and firmware with support for only 8 devices, because they miss configured the firmware. And vice versa you can find incredibly optimized TI CC2530 firmwares, which push the limits of that old MCU to the skies.

The number of RAM/FLASH or devices do not limit future support or updates or being "future-proof". That depends purely on when Silicon labs or community/company drops the support for specific hardware.

And again, I agree with your overall recommendation to stick with the newest available MCUs.
And again, thank you for promoting the Zigbee, so much great stuff happened, because of your contributions!
I should have chosen the words more carefully. Sorry again.