Follow-up to the conversation regarding the migration required for Zigbee dongles linked to the ezsp driver.
I think an automatic migration is dangerous and I prefer that users switch themselves, notably because of the firmware that needs to be updated.
I was thinking of doing the following on Gladys’s ZIgbee2Mqtt configuration page
replace ITead Sonoff Zigbee 3.0 USB Dongle Plus V2 model \"ZBDongle-E\" with Sonoff Zigbee 3.0 USB Dongle Plus V2 model \"ZBDongle-E\" (driver ezsp deprecated)
add an entry Sonoff Zigbee 3.0 USB Dongle Plus V2 model \"ZBDongle-E\" (driver emberznet)
check the firmware version installed on the dongle (accessible in the topic zigbee2mqtt/bridge/info)
if the version is < 7.4.x, disable the emberznet option and display a message saying « You should update your Zigbee dongle’s firmware, here is the procedure to follow: »
if the version is >= 7.4.x, display the message « You should update the driver used by z2m by selecting in the list above Sonoff Zigbee 3.0 USB Dongle Plus V2 model \"ZBDongle-E\" (driver emberznet) » with maybe a link to a Gladys doc that explains the why and impacts
Changing the model and saving by the user updates the configuration (without impact on the network/link with devices) => to be verified
Problem, there are 6 dongles in this case.
I don’t know how to handle the case for a new installation, as the firmware version information is not accessible
You can put a yellow message that appears above if the user selects the driver « Ember »: « Warning, your dongle must have firmware version > XX, here is the procedure to check your firmware version: XXXXXX »
I don’t know whether I should flash my ZBDONGLE-E; I’m afraid it might no longer be recognized in Gladys.
The dongle loses devices under zigbee2mqtt fairly regularly and it’s annoying to have to redo the pairing, especially with the ZBMINI-L2 modules that are in the flush-mounted box…
Otherwise there’s the option of buying the ZBDONGLE-P, but it can now only be found second-hand.
Hello. Indeed, I haven’t finished the development, because you need to take into account all cases so as not to update the driver while the firmware isn’t up to date.
I think an automatic migration is dangerous and I prefer that users switch themselves, notably because of the firmware that needs to be updated.
Problem, there are 6 dongles in this case.