How to upgrade/migrate ZBDongle-E from 6.x firmware to 7.4? #22919
Replies: 5 comments 3 replies
-
Upgrade from 6.x to 7.3 (version 12), run Zigbee2MQTT so it can make a backup, upgrade from 7.3 to 7.4 (then Zigbee2MQTT can restore the backup) |
Beta Was this translation helpful? Give feedback.
-
I was successful in upgrading ZBDongle-E from 6.x firmware to 7.4. The firmware update didn't work for me on the website. I flashed the firmware: Instructions for flshing for Linux i've got there: I edited the file:
I deleted: And everything worked just great! |
Beta Was this translation helpful? Give feedback.
-
Upgrade from 6.10.3 directly to 7.4.2 does work. I have done it last week. In a second step you can switch to ember. |
Beta Was this translation helpful? Give feedback.
-
I'm still trying to flash the ZBDongle-E using a Win11 Laptop. I have tried "connect" on https://darkxst.github.io/silabs-firmware-builder/. This failed even if I have installed suggested driver. Does anyone succeed flashing using Win11? Please let me know how to do. |
Beta Was this translation helpful? Give feedback.
-
Tengo el mismo problema estoy intentándolo por Windows, instalo los controladores me reconoce el dispositivo pero al darle a conectar me dice que fue imposible |
Beta Was this translation helpful? Give feedback.
-
I'm trying my best to catch up with the whole deal with the changeover from the
ezsp
driver to the rewrittenember
driver, but it's been throwing me for a loop, having to look in several different places and needing to determine what sources of info are up to date... (For instance, the website FAQ says that coordinator backup isn't supported for EZSP, so I didn't bother attempting it, but then the "adapters" page says it does...)I have a ZBDongle-E that was running some 6.x firmware version that it came with (may have been 6.9 or 6.10), which has been running happily with Z2M (Home Assistant addon) for the past year. I successfully flashed
ncp-uart-hw-v7.4.2.0-zbdonglee-115200.gbl
via the Silicon Labs Flasher addon from Home Assistant. Then I changed over Z2M's config to useadapter: ember
and tried to start it, but it complained about the backup file being unsupported (Current backup file is from an unsupported EZSP version (min: 12).
). So I changed the driver back toezsp
thinking I might need it to do something first, but all it gave me wasFailure to init network
. Finally, I downgraded the adapter to NCP 6.10.3 from itead's repo, restored the partial backup of Z2M I had made in Home Assistant, and tried starting Z2M again to restore functionality... but the device list is completely empty! Am I screwed?Edit: Right, so the Home Assistant-side addon backup doesn't actually back up any of Z2M's own configuration. At the moment, in Z2M's config directory, I have a
coordinator_backup.json
with an emptydevices
array, aconfiguration.yaml
that lists my device descriptions and config tweaks, adatabase.db
with no devices in it, and adatabase.db.backup
with all the devices in it. Seems like I'll have to re-pair everything... but I'm still not sure what I should have done to make this go smoothly.Beta Was this translation helpful? Give feedback.
All reactions