If i reflash my dongle to ember, do i have to repair all the devices or will they still work. Everything seems to be working fine on Ezsp, i don’t want to break it and cause myself hassles unnecessarily
I have 49 Zigbee devices and didn’t have to re-pair any.
Sonoff Dongle Plus-E
Thank you i took the plunge, and did have to repair some, others just needed repowering. However it wasn’t to bad.
Why should you move to Ember?
It says in the log that the Ezsp driver is deprecated, and Ember is the updated driver
1 Like
thx 4 the feedback
Just in the process of flashing the Sonoff-E with ember FW. Tried all these versions without success.
- ncp-uart-hw-v7.4.3.0-zbdonglee-115200.gbl
- ncp-uart-hw-v7.4.3.1-zbdonglee-115200.gbl
- ncp-uart-hw-v7.4.3.2-zbdonglee-115200.gbl
And yes, I did change the adapter to ember 
And also rebooted the whole system a couple of times. Using an RPI4 and HAOS.
All gave the same error message (bellow). I had to reflash with ncp-uart-hw_6.10.3_115200.gbl Also no need to repair any devices after going back to this FW.
Anyone else with same challenge?
type or pas[2024-06-04 19:48:58] error: z2m: Error while starting zigbee-herdsman
[2024-06-04 19:48:58] error: z2m: Failed to start zigbee
[2024-06-04 19:48:58] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-06-04 19:48:58] error: z2m: Exiting...
[2024-06-04 19:48:58] error: z2m: Error: [BACKUP] Current backup file is from an unsupported EZSP version (min: 12).
at EmberAdapter.getStoredBackup (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1363:23)
at EmberAdapter.initTrustCenter (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1156:37)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at EmberAdapter.initEzsp (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:865:19)
at EmberAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:2683:24)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:127:29)
at Zigbee.start (/app/lib/zigbee.ts:62:27)
at Controller.start (/app/lib/controller.ts:109:27)
at start (/app/index.js:107:5)te code here
Tried to
Upgrade from:
Coordinator type: EZSP v8
Coordinator revision: 6.10.3.0 build 297
To:
Coordinator type: EZSP v12
Coordinator revision: 7.3.1.0 build 176
Start HA and Z2M and let it finish the start up precedure
And then to:
Coordinator type: EmberZNet
Coordinator revision: 7.4.3 [GA]
…initially I thought this would do the trick, Z2M started but no devices worked as expected. Went back to 7.3.1.0 build 176. And concluded to wait until more users have updated to ember.
The solution is simple : after flashing firmware 7.4.x, start Zigbee2MQTT with the EZSP-driver, let it run a few minutes so it can create a version 12 backup file, and then change to the ember driver.
2 Likes
Well updated to ember and had to reconnect all of my devices. I use Zigbee2MQTT on a raspbarry pi and connect it with HA via Zigbee2MQTT proxy add on.
Was a pain in the ass but got it working, now I hope it will be stable. The only problem I had was with IKEA switches spaming the network and wanting to connect, I had to pull the battieries out of them and then add one by one.
1 Like
Just gave it a try. I have FW 7.4.3 flashed on the dongle. Z2M started and I can see the devices. However none of them are responding. When trying to re-pair a switch, there is no reaction after permitting to join.
Z2M log bellow (I cannot find any useful information there…)
[2024-06-06 21:30:55] debug: z2m: Skipping discovery of 'sensor/0xd0cf5efffe31045e/linkquality/config', already discovered
[2024-06-06 21:30:55] debug: z2m: Skipping discovery of 'sensor/0xd0cf5efffe31045e/update_state/config', already discovered
[2024-06-06 21:30:55] debug: z2m: Skipping discovery of 'binary_sensor/0xd0cf5efffe31045e/update_available/config', already discovered
[2024-06-06 21:30:55] debug: z2m: Skipping discovery of 'update/0xd0cf5efffe31045e/update/config', already discovered
[2024-06-06 21:31:50] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-06-06 21:31:50] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-06-06 21:31:50] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4 frmNum=0] Added to rxQueue
[2024-06-06 21:31:50] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=1]
[2024-06-06 21:31:50] debug: zh:ember:ezsp: <=== [FRAME: ID=63:"MESSAGE_SENT_HANDLER" Seq=51 Len=22]
[2024-06-06 21:31:50] debug: zh:ember:ezsp: ezspMessageSentHandler(): callback called with: [type=BROADCAST], [indexOrDestination=65533], [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":154}], [messageTag=255], [status=DELIVERY_FAILED], [messageContents=]
[2024-06-06 21:31:50] error: zh:ember: Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":154} messageTag=255]
[2024-06-06 21:32:55] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-06-06 21:32:55] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-06-06 21:32:55] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4 frmNum=1] Added to rxQueue
[2024-06-06 21:32:55] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=2]
[2024-06-06 21:32:55] debug: zh:ember:ezsp: <=== [FRAME: ID=63:"MESSAGE_SENT_HANDLER" Seq=51 Len=22]
[2024-06-06 21:32:55] debug: zh:ember:ezsp: ezspMessageSentHandler(): callback called with: [type=BROADCAST], [indexOrDestination=65533], [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":159}], [messageTag=255], [status=DELIVERY_FAILED], [messageContents=]
[2024-06-06 21:32:55] error: zh:ember: Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":159} messageTag=255]
[2024-06-06 21:33:01] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-06-06 21:33:01] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-06-06 21:33:01] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4 frmNum=2] Added to rxQueue
[2024-06-06 21:33:01] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=3]
[2024-06-06 21:33:01] debug: zh:ember:ezsp: <=== [FRAME: ID=63:"MESSAGE_SENT_HANDLER" Seq=51 Len=22]
[2024-06-06 21:33:01] debug: zh:ember:ezsp: ezspMessageSentHandler(): callback called with: [type=BROADCAST], [indexOrDestination=65533], [apsFrame={"profileId":0,"clusterId":6,"sourceEndpoint":0,"destinationEndpoint":0,"options":256,"groupId":0,"sequence":8}], [messageTag=255], [status=DELIVERY_FAILED], [messageContents=]
[2024-06-06 21:33:01] error: zh:ember: Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":6,"sourceEndpoint":0,"destinationEndpoint":0,"options":256,"groupId":0,"sequence":8} messageTag=255]
[2024-06-06 21:33:50] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-06-06 21:33:50] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-06-06 21:33:50] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4 frmNum=3] Added to rxQueue
[2024-06-06 21:33:50] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=4]
[2024-06-06 21:33:50] debug: zh:ember:ezsp: <=== [FRAME: ID=63:"MESSAGE_SENT_HANDLER" Seq=51 Len=22]
[2024-06-06 21:33:50] debug: zh:ember:ezsp: ezspMessageSentHandler(): callback called with: [type=BROADCAST], [indexOrDestination=65533], [apsFrame={"profileId":0,"clusterId":6,"sourceEndpoint":0,"destinationEndpoint":0,"options":256,"groupId":0,"sequence":69}], [messageTag=255], [status=DELIVERY_FAILED], [messageContents=]
[2024-06-06 21:33:50] error: zh:ember: Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":6,"sourceEndpoint":0,"destinationEndpoint":0,"options":256,"groupId":0,"sequence":69} messageTag=255]
[2024-06-06 21:33:59] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-06-06 21:33:59] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-06-06 21:33:59] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4 frmNum=4] Added to rxQueue
[2024-06-06 21:33:59] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=5]
[2024-06-06 21:33:59] debug: zh:ember:ezsp: <=== [FRAME: ID=63:"MESSAGE_SENT_HANDLER" Seq=51 Len=22]
[2024-06-06 21:33:59] debug: zh:ember:ezsp: ezspMessageSentHandler(): callback called with: [type=BROADCAST], [indexOrDestination=65533], [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":164}], [messageTag=255], [status=DELIVERY_FAILED], [messageContents=]
[2024-06-06 21:33:59] error: zh:ember: Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":164} messageTag=255]
Maybe add it here
and
Copy from my post here → SkyConnect v7.3.2.0 ezsp to ember - driver depricated - #13 by Hedda
FYI, Zigbee2MQTT lists EmberZNet with firmware 7.4.x as supported (using their new adapter: ember), and they also updated that page to list adapter: ezsp as deprecated (i.e. older firmware is not recommended):
Recommend read and ask any specific questions in Zigbee2MQTT’s own community discussions/forum on GitHub (or post issues there) instead of posting about it here in Home Assistant’s community forum:
Anyway, as I understand, in summery:
You need to have upgraded to at least EmberZNet 7.4.x firmware version or later to use the new ”ember” driver/adapter in Zigbee2MQTT, but from what I read it is suggested that existing Zigbee2MQTT users first upgrade to EmberZNet 7.3.x firmware version while still using the old ”ezsp” driver/adapter as it sounds like a migration to the new ”ember” driver will go smoother if already have had the old ”ezsp” driver/adapter working EmberZNet 7.3.x firmware version while still using the old ”ezsp” driver/adapter in Zigbee2MQTT. If you do that first before upgrading to EmberZNet 7.4.x.x firmware then you should not need to re-pair any devices.
Hence the multi-step process you need to follow do depends on your specific setup and you need to ask in the Zigbee2MQTT community if you need step-by-step that applies to your setup. The process for actually updating firmware version will not be different.
Suggest start by reading and try following this article regarding migrating Zigbee2MQTT from the ezsp adapter to the new ember adapter:
Summery; ezsp adapter is now deprecated in Zigbee2MQTT’s zigbee-herdsman library, which means that the Zigbee2MQTT developers are by doing so strongly recommending users to upgrade and migrate to ember adapter, and that migration might require a multi-step process depending on what EmberZNet firmware version you are using today. Users that continues to use the ezsp adapter will for now simply get a warning in their logs that they are using a deprecated adapter, however it will not stop working.
Note! If you have a EFR32MG12/MGM12 series or EM35x/EM35xx or ETRX35x based adapter then you need to buy a newer adapter. You need at least EFR32MG13/MGM13 series to be able to upgrade to EmberZNet 7.4.x.x firmware. So you preferably want to migrate to newer Silicon Labs based Zigbee Coordinator then you should consider getting an EFR32MG2x based USB radio dongle (EFR32MG21 or EFR32MG24 today, or EFR32MG26 in the future), at least if you plan on continuing to use Silicon Labs based Zigbee adapters, though technically you can even upgrade EFR32MG13 with EmberZNet 7.4.x.x firmware (but probably not to EmberZNet 7.5.x.x firmware when that comes).
For reference see:
- Improved Ember (EZSP) driver (experimental) · Koenkk/zigbee2mqtt · Discussion #21462 · GitHub
- New ember adapter implementation targeting EZSP 13 and above by Nerivec · Pull Request #918 · Koenkk/zigbee-herdsman · GitHub
- feat: Log EZSP adapter deprecated by Koenkk · Pull Request #1039 · Koenkk/zigbee-herdsman · GitHub
PS: Note that “Deprecated” does not mean that the ezsp adapter will be removed yet, instead it means you are discouraged from using it as it is being phased out and replaced by the newer ember adapter (which is not compatible with older firmware or all hardware).
1 Like
Well after 10 days of using the ember firmware I must say it us super stable, before I had two of my light bulbs going off line once every two or three days, now they work all the time. Also my temp sensor in garage was going offline, but now stays online all the time.
From my experience go with the ember firmware!
For best long-term stability should also take actions to follow best practice tips regardless of your setup:
Great guide!
I actually did everything as in your guide, but my setup is over two years old and I followed some other info found on this forum or on the web.
My setup has not changed since updating to Ember firmware, I use the same coordinator in the same place, with the same zigbee channel. All of my devices have not changed, the only diference may be the order in which I’ve added devices now versus when I made my original network. But I think the new firmware made my network much more stable.
#Thank you very much, @francisp for your solution! It helped bring back a few devices. However, in my case, only 3 out of 100 devices are working correctly. I am currently in the process of manually re-pairing the remaining devices. If anyone has additional suggestions or solutions, they would be greatly appreciated.
Hi all
I’ve updated first my Dongle-E to 7.3.1.2 via web uploader then I installed the 7.4.3.0 without restarting Z2M in a Proxmox container.
After Z2M restart, I found no device, so I rolled back to a snapshot created just before fw upgrade and all the device are back, but most are offline.
I’ve not changed, at this point ezsp to ember, as suggested by someone in this thread.
I’ve waited 20 min, but still no change.
So what now, change ezsp to ember and try to re-pair all the offline devices?
Thanks