I’ve successfully flashed ncp-uart-hw-v7.3.2.0-zbdonglee-none-115200.gbl to the new dongle but I’m unable to execute universal-silabs-flasher --device /dev/tty.usbserial-202305080921111 --probe-method ezsp write-ieee --ieee e0798dfffe77c2f0 on the new dongle to write the same address I’ve on the old dongle.
This means my only option will be to just flash the old dongle with new firmware version and forget to just switch dongles.
I’m not sure what functionality is included/required in the Z2M backup/restore for EZSP. I just assumed the change in the dongle with same address and different firmware version would ‘just work’. I consider the dongle was as a pure hardware device without a memory that requires to be permanent between boots (except for the ieee address)
Like darkxst says in the github issue, the only way to know the differences, is to read Silabs SDK release notes… and ensure the adapter also supports new features, if it’s hardware-dependent ones.
That is only partially the case when using as RCP (Radio Co-Processor) with the Silicon Labs EmberZNet Zigbee deamon (i.e. the multiprotocol addon with Silabs zigbeed), though not really true then either as it with RCP just offloads most but not all runtime parts of the Zigbee stack to the host computer when used as RCP. However it really is not the case when using as NCP (Network Co-Processor) as then the whole Zigbee stack is stored and runs onboard the Zigbee Coordinator microcontroller chip hardware on the dongle adapter, including all the Zigbee network information and security keys for your paired/joined devices. More details in Silabs docs if want to know how those two architectures work → https://www.silabs.com/documents/public/user-guides/ug103-03-fundamentals-design-choices.pdf
For tips on workaround backup and restore method/process for full NVRAM backups needed for Zigbee radio adapter migrations if using Zigbee2MQTT see this discussion in their community (which explain how to migrate between different radio types for Z2M regardless of manufacturer and Zigbee stack used) → https://github.com/Koenkk/zigbee2mqtt/discussions/16478
There is still only have experimental support for Silicon Labs EmberZNet based adapters in the zigbee-herdsman libary it depends on but if you upgrade to the very latest community firmware and use Zigbee2MQTT Edge (beta) releases then there is a new ”Ember” driver that you can configure it to use that is supposedly better than their ”EZSP” driver. Note that you should post any follow-up questions to that the in the Zigbee2MQTT community discussion forum on GitHub instead → https://github.com/Koenkk/zigbee2mqtt/discussions
I have a general question as I own a ZBDongle-E to which I have connected several Xiaomi humidity sensors using the zigbee2mqtt protocol.
My question is as follows: I have purchased a https://moeshouse.com/products/wifi-3-in-1-co2-monitor
It says that it is fully compatible with the Tuya protocol. Do I need to buy anything extra for it to be recognized by Home Assistant, or will the adapter I have work? I have Home Assistant running on a Raspberry Pi 4.
@Chris1989 all such questions about Zigbee2MQTT compatbility or support should not be posted/asked here in the Home Assistant forum but instead to Zigbee2MQTT’s own community discussions/forum → Koenkk/zigbee2mqtt · Discussions · GitHub
Edit: Update! Wait, the linked product is WiFi based (and not a Zigbee device), so can tell you that no Wi-Fi devices will ever work with Zigbee, as Zigbee is a completly different protocol so it totally unrelated here or ZHA and for Zigbee2MQTT, see → Zigbee - Wikipedia You really need to post that off-topic question elsewhere, not here.
@Hedda is correct. Tuya WiFi devices are a completely different animal and will not work with z2m at all.
That said, you may be able to use the core Tuya integration (100% web dependent), or if lucky the HACS Local Tuya integration(web needed for setup only). I think there are a couple of forks of LocalTuya now, and haven’t kept up with which is best. I no longer have any Tuya Wifi devices.
When I did have a few Tuya WiFi plugs, the LocalTuya in HACS never gave me any problems.
FYI, the popular Zigbee Gateway host application software Zigbee2MQTT to soon require EmberZNet 7.4.0.0 firmware or later if using a Silicon Labs based Zigbee Coordinator adapter. They have at least marked their old ezsp adapter code in their zigbee-herdsman library as deprecated with a reference that Z2M users should migrate to their new ember adapter code instead, and that new ember adapter requires EmberZNet 7.4.x.x Zigbee NCP firmware at a minimum (as it is not backwards compatible):
Anyway, “deprecated” in this case only means that the code for their old ezsp adapter will no longer maintained by Zigbee2MQTT developers and that Z2M users will from now on have an yet undefined grace period to migrate to the new ember adapter.
Zigbee2MQTT’s developers on purpose choose to do a clean rewrite their new ember adapter code as “greenfield project” with focus on only supporting EZSP v13 (EmberZNet Serial Protocol version 13 which is only available in EmberZNet 7.4.0.0 firmware and later) to avoid constraints and limitations imposed by old code or old firmware.
Having personally migrated 100% of my Zigbee devices to Home Assistant’s own built-in native ZHA integration I am today not sure how well backup and restore is working these days if using their old ezsp adapter in Zigbee2MQTT but at least until recently there was no ability to restore from backup in Z2M if using that ezsp adapter in Zigbee2MQTT, see → Koenkk/zigbee-herdsman#319 and the unofficial workaround to backup and restore before if using ezsp adapter in Zigbee2MQTT was to backup and restore using zigpy-cli, see Koenkk/zigbee2mqtt#16478 but I believe the new ember adapter in Zigbee2MQTT has full native support for backup and restore but I am not sure about native migrations from ezsp adapter to ember adapter inside Zigbee2MQTT.
Note! Regardless of above, be aware that Silicon Labs adapters are currently still “experimental” in Z2M → Supported Adapters | Zigbee2MQTT however their plan is that this will change in the future with their new ember adapter code becomes more stable. Though for now only Texas Instruments CC2652 and CC1352 based adapters are officialy recommended for Zigbee2MQTT as of yet. So you might instead want to consider buying and migrating to ITead’s “Sonoff Zigbee 3.0 USB Dongle Plus” (model “ZBDongle-P”) based on Texas Instruments CC2652P
PS: Not sure if ITead’s personel reads issues on their GitHub repository but posted feature request here:
They have never released a single firmware update for the ZBDongle-E, dont see why they would start now. They seem happy for their users to rely on community built firmwares!
I’m looking to update the firmware on my EFR32MG21 Sonoff dongle. Do you know if the original EFR32MG21 dongle (i.e. Sonoff Zigbee 3.0 USB Dongle, model 9888010100045) can be updated to the new EmberZNet 7.4.x.x firmware. Or is it only compatible with the ZBDongle-E model?
EDIT: I did manage to upgrade the firmware successfully. I used Darkxst’s firmware for the DongleE and flashed it using the manual process - for some reason Darkxst’s web flasher didn’t pick up my device (maybe because the CH340 uart, while the ZB-DongleE is different, or maybe for some other reason). Either way my Z2M is all working nicely on Ember now.
warning: zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember'
will become the officially supported EmberZNet driver in next release.
If using Zigbee2MQTT see https://github.com/Koenkk/zigbee2mqtt/discussions/21462
as well as errors such as
error: zh:ezsp:ezsp: Frame changeSourceRouteHandler parsing error: RangeError: Attempt to access memory outside buffer bounds
at new NodeError (node:internal/errors:405:5)
at boundsError (node:internal/buffer:86:11)
at Buffer.readUInt16LE (node:internal/buffer:245:5)
at Buffer.readUIntLE (node:internal/buffer:182:17)
at Function.deserialize (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/types/basic.ts:19:67)
at new EZSPFrameData (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:180:54)
at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:154:23
at Array.every (<anonymous>)
at Function.createFrame (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:148:15)
at Ezsp.onFrameReceived (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:439:35)
I’ve read through the discussion #21462 and am really none the wiser, apart from acknowledging that the ezsp adapter will no longer be supported. Do I need to change the adapter firmware to the Ember version and if so does anyone have a step by step guide they could point me towards?
This thread is specifically only about hardware and firmware, for Zigbee2MQTT configuration discussion/questions or issues and other application related things you need to post to their project and own community on GitHub:
