Has anybody started this dongle with zigbee2mqtt in HA ?
FYI, Silicon Labs EZSP (v8) support in zigbee-herdsman (which Zigbee2MQTT depends on) was just recently added and as such is not mature and currently only available in Zigbee2MQTT dev branch. They are however looking for testers that want to experiment and help out testing it. Initial development has been started on experimental (pre-alpha stage) support for various Zigbee coordinatior adapters based on Silicon Labs EFR32 SoC families with EmberZNet NCP 6.7.8 firmware or later via EZSP version 8 (EmberZNet Serial Protocol) interface. This include all hardware based on SoCs/Modules from Silabs EFR32MG21/MGM210 and EFR32MG12/MGM12 series. More information and discussion available in the Zigbee-herdsman repository on GitHub:
https://github.com/Koenkk/zigbee-herdsman/issues/319
Note! All the issues regarding interference that I posted above of course also apply to Zigbee2MQTT, as such this is not the best hardware to test EZSP with because any problems can be due to interferance.
FYI, other than using a very long USB extension cable with your dongle and adding electromagnetic shielding to your other devices/appliances (like your Raspberry Pi enclosure), another tip is to add electromagnetic shielding to all the parts of the dongle circuit board that is not the PBC trace antenna.
This type of electromagnetic shielding can done by first wrapping it in one layer of some kind of isolating film or tape around it and then wrapping a layer of conductive metallic tape on top of that.
Just make sure to not cover the antenna and as well as electrically grounding the conductive metallic tape to the USB jacketing (which act as a point of the electrical ground) checking it makes contact.
Rather than using just any tape lying around a better solution would probably be a good idea try using either heat-shrink tubing or kapton-tape as the isolation layer (both types are widely available online).
https://en.wikipedia.org/wiki/Heat-shrink_tubing
https://en.wikipedia.org/wiki/Kapton
Also, rather than using any metallic tape, suggested consider buying conductive copper tape (checking that the adhesive/glue on the metallic tape really is a âconductiveâ variant as ânon-conductiveâ variant also exist, as then it should be easy to ground that conductive tape by just wrapping part of the USB mantel/jacketing as the point of the electrical ground). Tip is to just search for âconductive metal tapeâ.
https://en.wikipedia.org/wiki/Electrically_conductive_adhesive
https://en.wikipedia.org/wiki/Copper_tape
âŚonce I get around to this myself I probably do it overkill style; i.e.:
- First wrap a layer of Kapton-tape (no need to touch USB mantel, and making sure not to cover the PCB trace antenna on the board),
- Then wrap a layer of conductive metallic tape, (that needs to touch USB mantel/jacketing, and making sure not to cover the PCB trace antenna on the board).
- Lastly heat-shrink tubing over everything (here you could probably choose if you also want to cover PCB trace antenna or not).
Again, be sure to touch USB to ground copper-tape but not to cover the tip of the dongle/stick circuit board which has PCB trace antenna!
Reference:
https://en.wikipedia.org/wiki/Electromagnetic_shielding
PS: If you are using a Raspberry Pi or other single-board-computer with wired Ethernet and you do not need to use its WiFi or Bluetooth then you can also add a layer of electromagnetic shielding to its enclosure as well (or just buy a metal case for it).
I cannot find the hardware address of the Itead zigbee stick under Supervisor->Hardware. Iâve tried both USB2.0 and USB3.0 portsâŚis there a secret Iâm missing?
Got it working. Had to enter the /dev/serial/by-id information manually, plus change port speed to 115200. Finally found the stick.
Any idea why my Itead device wonât add any Aqara sensors? Trying to add water sensor but dongle wonât pair. Itâs on a long USB cableâŚ
I found when pairing Aqara sensors, I had to press the button regularly after it had gone into pairing mode in order for HA to pick it up.
1 Like
All the Aqara and Xiaomi devices are infamous for having loads of compatibility issues with most Zigbee implementations that are not their own. Suggest check out this post on Hubitat which have pairing tips:
PS: Also read other dongle tip on about adding conductive metallic tape as electromagnetic shielding:
I bought the Zigbee 3.0 USB dongle together with their button switch directly from ITead. I plugged it into a USB 2.0 on my RPI4 with a long USB lead. When I install the ZHA integration, it picks it up and installs it but I get the following error:
And this is the error I get on the logs:
Logger: homeassistant.components.zha.core.gateway
Source: components/zha/core/gateway.py:152
Integration: Zigbee Home Automation (documentation, issues)
First occurred: August 11, 2021, 10:04:49 PM (98 occurrences)
Last logged: 12:18:45 AM
Couldn't start EZSP = Silicon Labs EmberZNet protocol: Elelabs, HUSBZB-1, Telegesis coordinator
Traceback (most recent call last):
File "/usr/local/lib/python3.9/asyncio/tasks.py", line 492, in wait_for
fut.result()
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 152, in async_initialize
self.application_controller = await app_controller_cls.new(
File "/usr/local/lib/python3.9/site-packages/zigpy/application.py", line 74, in new
await app.startup(auto_form)
File "/usr/local/lib/python3.9/site-packages/bellows/zigbee/application.py", line 109, in startup
self._ezsp = await bellows.ezsp.EZSP.initialize(self.config)
File "/usr/local/lib/python3.9/site-packages/bellows/ezsp/__init__.py", line 83, in initialize
await ezsp.reset()
File "/usr/local/lib/python3.9/site-packages/bellows/ezsp/__init__.py", line 98, in reset
await self._gw.reset()
File "/usr/local/lib/python3.9/site-packages/bellows/uart.py", line 223, in reset
return await asyncio.wait_for(self._reset_future, timeout=RESET_TIMEOUT)
File "/usr/local/lib/python3.9/asyncio/tasks.py", line 494, in wait_for
raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError
Anny assistance in getting this integrated and working please?
I also get this error in the log:
Logger: zigpy.application
Source: /usr/local/lib/python3.9/site-packages/zigpy/application.py:78
First occurred: 12:30:47 AM (9 occurrences)
Last logged: 12:38:04 AM
Couldn't start application
Looks like you donât have entered/selected correct Serial Device Path as the full path should be longer.
Supervisor > System > Host System > dot menu > Hardware have a list of available device paths.
PS: Unrelated but by the way, also make sure you upgrade firmware on ITead Zigbee 3.0 USB dongle.
Thank you @Hedda, greatly appreciate your assistance. I got the correct Device Path from the hardware section, and installed it manually and it work. You are STAR!
I figured I am on version 678 but did not bother to upgrade it to 679, as after reading the link you sent, donât have a clue on how to do it.
You can upgrade via either of these two tools/scripts as long as provide the correct firmware image file:
PS: Tips is that easier to upgrade on a other computer than the one running your Home Assistant, and any operating system will work as long as you first install Python (though command syntax will differ).
FYI, ITead just announced an upcoming âSonoff Zigbee 3.0 USB Dongle Plusâ based on TI CC2652P:
I understand ITead only went with CC2652P instead of Silicon Labs EFR32MG21 for this âPlusâ dongle version because of the current silicon chip shortage (which Silabs parts suffered for more than most).
Hopefully, we will also see ITead release a new fixes revision of their cheaper Zigbee 3.0 USB dongle with proper RF shielding and either corrected PCB antenna design or better yet a ceramic chip antenna.
As we know, ITeadâs existing ânon-Plus Zigbee 3.0 USB dongleâ is based on Silabs EFR32MG21 SoC which is just as powerful but sadly was proven that ITeadâs first Zigbee 3.0 USB Dongle PCB board revision had a badly designed integrated PCB antenna and no electromagnetic shielding which caused huge issues, and to this date, it has been listed as âout-of-stockâ since after the initial batch was sold.
FYI, ITead has now released Silabs EmberZNet 6.10 (v6.10.3) firmware for their EFR32MG21 dongle:
https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware/Zigbee3.0_Dongle
Not tested but will probably work on ZB-GW02, ZB-GW03, ZB-GW04, and Sonoff ZBBridge as well?
I understand they all use same radio board design based on âSM-011 V1.0â radio module by CoolKit:
https://github.com/zigpy/zigpy/discussions/586
xsp1989 also announced the good news is that a router firmware âwill be released soonâ (so probably).
FYI; Zigbee Router firmware for EFR32MG21 adapters has now been released by xsp1989 on GitHub.
From readme it sounds tested with ITead Zigbee 3.0 USB Dongle and an SM-011 based USB adapter.
The same âSM-011 V1.0â Zigbee radio modules by CoolKit Technologies is also used inside some Zigbee gateways/hubs like the popular ITead Sonoff ZBBridge and ZB-GW03 eWeLink Ethernet Zigbee Gateway sold by EACHEN and SmartWise, 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
FYI, ITead has now also released a new Zigbee dongle based on the same EFR32MG21 SoC however the new one features the same external antenna + metal-enclosure as ITeadâs dongle that is based on Texas Instruments CC2652P, as well as shipping in similar retail packaging to make it more attractive for sale in brick and mortar stores:
Comparing âZBDongle-Pâ vs. âZBDongle-Eâ vs. barebone EFR32MG21 dongle
verses 
versus 
| Feature/Model | ZBDongle-P | ZBDongle-E | 9888010100045 |
|---|---|---|---|
| Radio SoC/MCU chip | Texas Instruments CC2652P | Silicon Labs EFR32MG21 | Silicon Labs EFR32MG21 |
| Zigbee Stack (Serial Interface Protocol API/CLI) | Z-Stack v3 (ZNP 3) | EmberZNet (EZSP v8) | EmberZNet (EZSP v8) |
| Optional Zigbee Router firmware | Yes (9dBm firmware available from Koenkk) | Yes (20dBm firmware available from ITead) | Yes (20dBm firmware available from ITead) |
| USB to UART/Serial Converter Chip | CP2102 or CP2102N | CH9102F | CH340 |
| USB EEPROM Product Description ID | SONOFF Zigbee 3.0 USB Dongle Plus | SONOFF Zigbee 3.0 USB Dongle Plus V2 (first need to run update script if from first hardware batch shipped) | None (no USB chip EEPROM) |
| Home Assistant USB Auto Disovery | Yes | Yes (but way need to run update script if from first hardware batch shipped) | Not possible |
| Flow Control | None by default (Hardware flow control optional with alternative firmware and flipped dip-switchďź | Software flow control | Software flow control |
| RF Transmit Output Power | 9dBm (firmware hardcoded), Max: 20dBm | 20dBm (default) | 20dBm (default) |
| Antenna | External (rotatable and tiltable) | External (rotatable and tiltable) | Onboard circuit board antenna |
| Enclosure/case | Aluminum all-metal shell casing | Aluminum all-metal shell casing | None |
| Length | 63mm | 52mm | ? |
| Packaging | Retail-box with manual | Retail-box with manual | Anti-static bag only |
| Home Assistant ZHA | Supported | Supported | Supported |
| Zigbee2MQTT | Supported | Experimental support as still in development by zigbee-herdsman dev, see https://github.com/Koenkk/zigbee-herdsman/issues/319 | Experimental support as still in development by zigbee-herdsman dev, see https://github.com/Koenkk/zigbee-herdsman/issues/319 |
| IoBroker | Supported | Experimental support as still in development by zigbee-herdsman dev, see https://github.com/Koenkk/zigbee-herdsman/issues/319 | Experimental support as still in development by zigbee-herdsman dev, see https://github.com/Koenkk/zigbee-herdsman/issues/319 |
| OpenHAB ZigBee Binding | Not yet, see request and discussion | Supported | Supported |
| Domoticz Zigbee Plugin | Supported | Supported | Supported |
| Jeedom Zigbee Plugin | Supported | Supported | Supported |
4 Likes
Hi, I go the same issue with vibration feature while the sensor keeps reporting temperature regulary. How did you fix the issue with temperature :)?
@nhuythuy please start a new separate thread instead as that question is off-topic for this thread.
1 Like