[WIP]: EFR32 EZSP adapter implementation and test

[kirovilya]

After accepting the alpha version of the code, now I propose to write comments here until we complete the development.

The adapter is designed to work with EFR32 chips using the EZSP v8 protocol. Recommended firmware NCP 6.7.8.

The work with devices with such chips was tested:

• Re-flashed Sonoff Zigbee Bridge gateway https://www.digiblur.com/2020/07/how-to-use-sonoff-zigbee-bridge-with.html
• Flashed devboard EByte E180-ZG120B New Zigbee to Ethernet "DIY" Corrdinator zigpy/zigpy#584
• Flashed usb stick based on SM-011 https://modkam.ru/?p=1889 (description in Russian, use the translator)
• Defaro Sprut stick https://spruthub.ru/device/defaro-sprut-stick-2-pro (description in Russian, use the translator)

Settings:

• specify port parameter or gateway address
• set adapter to "ezsp"

Worked:

• Pairing/Leaving
• Bind/Unbind
• ZCL messages/commands
• Network map

TODO:

• Improving the stability work of the network
• Groups
• Touchlink
• Backup/Restore
• OTA update
• Tests
• ZGP (Zigbee Green Power)

I urge the developers to participate in the finalization of the adapter. I'm not an expert in TypeScript and EmberZNet, so I ask for help.

[MattWestb]

Have you getting some user with EM357 or EM3581 that have updating the firmware to EZSP6.7.8.0 to testing if they is working ?

It shall working if Ssilabs have making all OK then the protocol is is independent of the hardware its running.

I posing one request for testing in EM35X forum.

If going well you have getting some more thousand possible user of Z2M :-)))

Great work done going from alpha stage and and implanting more functionality !!!

[kirovilya]

@MattWestb no, i haven't. I think it should work in the same way there, too. the protocol is the same.

[MattWestb]

I have asking our brave EM35X users if some can testing it and im 95% sure its working OK :-))

[Hedda]

The adapter is designed to work with EFR32 chips using the EmberZNet v8 protocol. Recommended firmware NCP 6.7.8.

General tip when buying an EZSP v8+ compatible adapter is to buy one based on a newer Silicon Labs EFR32MGxx SoC if possible.

Warning! In summary do not use a Zigbee to WiFi bridge/gateway, (like ITead's Sonoff ZBBridge Zigbee WiFi Bridge gateway hacked/re-flashed with Tasmota or ESPHome), instead f need to connect over the network then be sure to get a wired LAN bridge/gateway. Be warned from using Wi-Fi-based Zigbee-to-IP serial network bridges/gateways. The EZSP protocol requires a very stable connection to the serial port. If connecting to Silicon Labs EFR32MGxx SoC using a serial-to-IP tunnel over a WiFi network then it is expected to see NCP entered a failed state. Requesting APP controller restart in the logs. This is a normal part of the operation and indicates there was a drop in communication between ZHA and the EFR32MGxx SoC SoC.

Update! At the time of writing (2022-06-30) Silicon Labs EmberZNet Zigbee NCP version 6.10.3.0 firmware is recommended for both Zigbee2MQTT and Home Assistant's ZHA integration if you have a Silabs EFR32MGxx based Zigbee adapter.

Note! All Silicon Labs SoC based adapters should work long as update between Silabs EmberZNet 6.7.x or 6.10.x versions, (Silabs EmberZNet 7.0.x Zigbee NCP firmware should work as well since it is backwards compatible with EZSP v8, but for now, do not yet recommend using the upcoming EmberZNet 7.1.x and newer because they implement EZSP v9 and later, and is not fully backwards compatible with EZSP v8 and support for it should therefore not be considered mature).

Best practice! Regularly update the Zigbee Coordinator USB adapter/dongle/stick firmware as new versions contain bug-fixes from Silicon Labs SDK, and most important is to also always use the Zigbee Coordinator USB adapter/dongle/stick using a very long USB extension cable, as well as only ever connect it to a USB 2.0 port or via USB 2.0 hub (and never a USB 3.0 port/hub) in order to avoid EMF/EMI/RMI interference which is infamously well known to seriously affect Zigbee signal reception performance!

It is advised to buy a Zigbee USB dongle based on EFR32MG13 SoC or later as buying a newer SoC should be more future-proof:

• Home Assistant SkyConnect (USB dongle based on EFR32MG21) works out-of-the-box using default NCP firmware (not RCP)
  • https://www.home-assistant.io/skyconnect/
• ITead Sonoff Zigbee 3.0 USB Dongle Plus model “ZBDongle-E” (based on EFR32MG21)
  • https://itead.cc/product/zigbee-3-0-usb-dongle/
    • Note! - The no longer sold Zigbee 3.0 dongle barebone model "9888010100045" adapter from ITead was also based on EFR32MG21 and should also work, however, as that board did not have any EMF shielding and poor antenna design or at least reportingly using a poorly tuned circuit board antenna so signal reception has been reported to be extremly sensitive to interference unless using a very long USB extension cable and/or adding some basic shielding on your own.
      • https://www.facebook.com/watch/?v=262086502015726
• Tube's EFR32 based Ethernet and/or USB Gateway (based on ESP32 with MGM210P Zigbee radio module with EFR32MG21)
  • https://tubeszb.com
  • https://github.com/tube0013/tube_gateways
• ZB-GW04 USB stick (a.k.a. "easyiot Zigbee dongle") USB dongle which uses EFR32MG21 based "SM-011 v1.0" Zigbee module from CoolKit-Technologies.
  • https://easyiot.aliexpress.com/store/all-wholesale-products/1101491524.html
    • https://www.aliexpress.com/item/1005002791666029.html
• 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/
• Zvidar Z-DG-Z01 (based on EFR32MG21)
  • http://www.zvidar.com
  • https://zigbee.blakadder.com/Zvidar_Z-DG-Z01.html
• Defaro Sprut Stick 2 Pro (based on EFR32MG21. Description in Russian, use a translator)
  • https://spruthub.ru/device/defaro-sprut-stick-2-pro
• 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
• DIY Zigbee Coordinator gateway based on EByte E180-ZG120B dev board if the 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
• 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
• 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
• DIY ESP32/ESP8266 based "Zigbee-to-IP" network bridges/gateways using "SM-011 V1.x" (ZYZBP008) radio module from CoolKit-Technologies. (based on EFR32MG21). Note that the "SM-011 V1.x" module on this board is missing Electromagnetic shielding (e.i. metal covering to protect the SoC and sensitive components from EMF) and is reportingly using a poorly tuned circuit board antenna so signal reception has been reported to be extremely sensitive to EMF/EMI/RMI interference unless using 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).
• DIY Modkam USB dongle (description only in Russian so use a translator) which also uses EFR32MG21 based "SM-011 v1.0" Zigbee module from CoolKit-Technologies.
  • Silicon Labs EFR32MG21 based SoC modules, dongles/sticks, and gateways or bridges zigpy/zigpy#586
• 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

It should really work with any Silicon Labs EFR32 Zigbee NCP SoC from EFR32MG21/MGM210 and EFR32MG12/MGM12 series:

• 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

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

Tip! Firmware can be easily be flashed with Nabu Casa's Universal Silicon Labs Flasher or Elelabs's EZSP Firmware Update Utility:

• https://github.com/NabuCasa/universal-silabs-flasher
• https://github.com/Elelabs/elelabs-zigbee-ezsp-utility
• https://github.com/NabuCasa/silabs-firmware
  https://github.com/itead/Sonoff_Zigbee_Dongle_Firmware
• https://github.com/walthowd/husbzb-firmware
• https://github.com/grobasoz/zigbee-firmware/
• https://github.com/xsp1989/zigbeeFirmware/
• https://github.com/skgsergio/silabs-multiprotocol-firmware-zbgw04-usb/tree/main/firmware/ncp
• https://github.com/zha-ng/EZSP-Firmware
• https://github.com/MattWestb/EFR32-FW

You can even compile your own EmberZNet Zigbee NCP (EZSP) firmware with silabs-firmware-builder originally from Nabu Casa:

• https://github.com/NabuCasa/silabs-firmware-builder

There are also forks of Nabu Casa's silabs-firmware-builder that has been extended with more features, like example these:

• https://github.com/Nerivec/silabs-firmware-builder
• https://github.com/darkxst/silabs-firmware-builder

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 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 to avoid EMF regardless of which Zigbee Coordinator that you are using!

[danielk117]

Tried it with 5 thermostat SEA801. Works basically 👍 but there are some problems. Z2M restarts every few minutes with the following message...

│Mar 06 15:03:25 raspberrypi npm[14963]: /opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:67                                      │
│Mar 06 15:03:25 raspberrypi npm[14963]:                     waiter.reject(new Error(message));                                                       │
│Mar 06 15:03:25 raspberrypi npm[14963]:                                   ^                                                                          │
│Mar 06 15:03:25 raspberrypi npm[14963]: Error: {"frameId":85,"sequence":261} after 30000ms                                                           │
│Mar 06 15:03:25 raspberrypi npm[14963]:     at Timeout._onTimeout (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:67:35)       │
│Mar 06 15:03:25 raspberrypi npm[14963]:     at listOnTimeout (node:internal/timers:556:17)                                                           │
│Mar 06 15:03:25 raspberrypi npm[14963]:     at processTimers (node:internal/timers:499:7)                                                            │
│Mar 06 15:03:25 raspberrypi npm[14963]: npm ERR! code 1                                                                                              │
│Mar 06 15:03:25 raspberrypi npm[14963]: npm ERR! path /opt/zigbee2mqtt                                                                               │
│Mar 06 15:03:25 raspberrypi npm[14963]: npm ERR! command failed                                                                                      │
│Mar 06 15:03:25 raspberrypi npm[14963]: npm ERR! command sh -c node index.js                                                                         │
│Mar 06 15:03:25 raspberrypi npm[14963]: npm ERR! A complete log of this run can be found in:                                                         │
│Mar 06 15:03:25 raspberrypi npm[14963]: npm ERR!     /home/pi/.npm/_logs/2021-03-06T14_03_25_317Z-debug.log                                          │
│Mar 06 15:03:25 raspberrypi systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=1/FAILURE                                      │
│Mar 06 15:03:25 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.

[kirovilya]

@danielk117 Thanks for testing. After accepting the latest changes, you can check again - the reconnection in case of errors has been implemented and some pending moments have been removed.

[Koenkk]

Changes will be available in 1 hour in the dev branch (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html)

[danielk117]

Thank you both! 😃 I'm already on dev branch and will try the latest version now.

[danielk117]

@kirovilya
Sorry man, same errors for now.

│Mar 06 21:02:06 raspberrypi npm[12167]: Assertion failed                                                                                             │
│Mar 06 21:02:06 raspberrypi npm[12167]: Assertion failed                                                                                             │
│Mar 06 21:02:42 raspberrypi npm[12167]: /opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:67                                      │
│Mar 06 21:02:42 raspberrypi npm[12167]:                     waiter.reject(new Error(message));                                                       │
│Mar 06 21:02:42 raspberrypi npm[12167]:                                   ^                                                                          │
│Mar 06 21:02:42 raspberrypi npm[12167]: Error: {"frameId":97,"sequence":267} after 10000ms                                                           │
│Mar 06 21:02:42 raspberrypi npm[12167]:     at Timeout._onTimeout (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:67:35)       │
│Mar 06 21:02:42 raspberrypi npm[12167]:     at listOnTimeout (node:internal/timers:556:17)                                                           │
│Mar 06 21:02:42 raspberrypi npm[12167]:     at processTimers (node:internal/timers:499:7)                                                            │
│Mar 06 21:02:42 raspberrypi npm[12167]: npm ERR! code 1                                                                                              │
│Mar 06 21:02:42 raspberrypi npm[12167]: npm ERR! path /opt/zigbee2mqtt                                                                               │
│Mar 06 21:02:42 raspberrypi npm[12167]: npm ERR! command failed                                                                                      │
│Mar 06 21:02:42 raspberrypi npm[12167]: npm ERR! command sh -c node index.js                                                                         │
│Mar 06 21:02:42 raspberrypi npm[12167]: npm ERR! A complete log of this run can be found in:                                                         │
│Mar 06 21:02:42 raspberrypi npm[12167]: npm ERR!     /home/pi/.npm/_logs/2021-03-06T20_02_42_328Z-debug.log

npm debug log:

0 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
1 info using npm@7.3.0
2 info using node@v15.5.0
3 timing config:load:defaults Completed in 4ms
4 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 5ms
5 timing config:load:builtin Completed in 5ms
6 timing config:load:cli Completed in 4ms
7 timing config:load:env Completed in 0ms
8 timing config:load:file:/opt/zigbee2mqtt/.npmrc Completed in 2ms
9 timing config:load:project Completed in 4ms
10 timing config:load:file:/home/pi/.npmrc Completed in 0ms
11 timing config:load:user Completed in 1ms
12 timing config:load:file:/usr/etc/npmrc Completed in 0ms
13 timing config:load:global Completed in 0ms
14 timing config:load:cafile Completed in 1ms
15 timing config:load:validate Completed in 1ms
16 timing config:load:setUserAgent Completed in 2ms
17 timing config:load:setEnvs Completed in 2ms
18 timing config:load Completed in 25ms
19 verbose npm-session 3488c9d57fec89ec
20 timing npm:load Completed in 44ms
21 timing command:run-script Completed in 1232065ms
22 timing command:start Completed in 1232071ms
23 verbose stack Error: command failed
23 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/index.js:64:27)
23 verbose stack     at ChildProcess.emit (node:events:376:20)
23 verbose stack     at maybeClose (node:internal/child_process:1063:16)
23 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:295:5)
24 verbose pkgid zigbee2mqtt@1.18.1-dev
25 verbose cwd /opt/zigbee2mqtt
26 verbose Linux 5.4.83-v7l+
27 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
28 verbose node v15.5.0
29 verbose npm  v7.3.0
30 error code 1
31 error path /opt/zigbee2mqtt
32 error command failed
33 error command sh -c node index.js
34 verbose exit 1

[danielk117]

As written before, the problem still exists, but i think it happens less often.
I Found another error, which wasn't there with the CC2530. It happend a couple of times since yesterday.

Around 07:45 i was trying to set zigbee/thermostat_wohnzimmer/set/current_heating_setpoint to 17. The device itself does the job, but Z2M says after 2 minutes (at 07:47:46) the current_heating_setpoint is 22 (which wasn't true).
I think the message Assertion failed has to do with that.

Mar 07 07:41:43 raspberrypi npm[3136]: Zigbee2MQTT:info  2021-03-07 07:41:43: MQTT publish: topic 'zigbee/thermostat_flur', payload '{"anti_scaling":"ON","away_mode":"OFF","battery_low":false,"child_lock":"LOCKED","current_heating_setpoint":15,"frost_detection":"OFF","linkquality":176,"local_temperature":14.7,"local_temperature_calibration":0,"preset_mode":"none","system_mode":"heat","window_detection":"OFF"}'
Mar 07 07:45:33 raspberrypi npm[3136]: Zigbee2MQTT:info  2021-03-07 07:45:33: MQTT publish: topic 'zigbee/thermostat_kinderzimmer', payload '{"anti_scaling":"OFF","away_mode":"OFF","battery_low":false,"child_lock":"LOCKED","current_heating_setpoint":21,"frost_detection":"OFF","linkquality":120,"local_temperature":22.1,"local_temperature_calibration":0,"preset_mode":"none","system_mode":"heat","window_detection":"OFF"}'
Mar 07 07:45:43 raspberrypi npm[3136]: Zigbee2MQTT:info  2021-03-07 07:45:43: MQTT publish: topic 'zigbee/thermostat_kinderzimmer', payload '{"anti_scaling":"OFF","away_mode":"OFF","battery_low":false,"child_lock":"LOCKED","current_heating_setpoint":21,"frost_detection":"OFF","linkquality":116,"local_temperature":22.1,"local_temperature_calibration":0,"preset_mode":"none","system_mode":"heat","window_detection":"OFF"}'
Mar 07 07:45:54 raspberrypi npm[3136]: Zigbee2MQTT:info  2021-03-07 07:45:54: MQTT publish: topic 'zigbee/thermostat_kinderzimmer', payload '{"anti_scaling":"OFF","away_mode":"OFF","battery_low":false,"child_lock":"LOCKED","current_heating_setpoint":21,"frost_detection":"OFF","linkquality":116,"local_temperature":22.1,"local_temperature_calibration":0,"preset_mode":"none","system_mode":"heat","window_detection":"OFF"}'
Mar 07 07:45:59 raspberrypi npm[3136]: Zigbee2MQTT:info  2021-03-07 07:45:59: MQTT publish: topic 'zigbee/thermostat_kinderzimmer', payload '{"anti_scaling":"OFF","away_mode":"OFF","battery_low":false,"child_lock":"LOCKED","current_heating_setpoint":21,"frost_detection":"OFF","linkquality":116,"local_temperature":22.1,"local_temperature_calibration":0,"preset_mode":"none","system_mode":"heat","window_detection":"OFF"}'
Mar 07 07:46:05 raspberrypi npm[3136]: Assertion failed
Mar 07 07:46:05 raspberrypi npm[3136]: Assertion failed
Mar 07 07:46:21 raspberrypi npm[3136]: Zigbee2MQTT:info  2021-03-07 07:46:21: MQTT publish: topic 'zigbee/thermostat_kinderzimmer', payload '{"anti_scaling":"OFF","away_mode":"OFF","battery_low":false,"child_lock":"LOCKED","current_heating_setpoint":21,"frost_detection":"OFF","linkquality":116,"local_temperature":22.1,"local_temperature_calibration":0,"preset_mode":"none","system_mode":"heat","window_detection":"OFF"}'
Mar 07 07:47:46 raspberrypi npm[3136]: Zigbee2MQTT:info  2021-03-07 07:47:46: MQTT publish: topic 'zigbee/thermostat_wohnzimmer', payload '{"anti_scaling":"ON","away_mode":"OFF","battery_low":false,"child_lock":"LOCKED","current_heating_setpoint":22,"frost_detection":"OFF","linkquality":188,"local_temperature":22.2,"local_temperature_calibration":0,"preset_mode":"none","system_mode":"heat","window_detection":"OFF"}'

Any idea?