Yes, I don’t think it’s new, but since we’re encouraging changing the driver now, the behavior is suddenly quite noticeable, which wasn’t the case before; it was rare to modify this configuration
It’s fixed.
When the dongle was changed, the z2m container had a new mqtt password; that’s no longer the case.
Tested and working
1 Like
Excellent !! I’ll test right away
That’s perfect, it works like a charm! I’ll do a review and if it’s good it’ll go to production for me
1 Like
The code looks good to me, just a small note: there is a modified file that isn’t really related to the PR:
master ← cicoub13:feat-z2m-ember
ouvert 09:44AM - 16 Feb 26 UTC
### Pull Request check-list
To ensure your Pull Request can be accepted as fa… st as possible, make sure to review and check all of these items:
- [X] If your changes affect the code, did you write the tests?
- [X] Are tests passing? (`npm test` on both front/server)
- [X] Is the linter passing? (`npm run eslint` on both front/server)
- [X] Did you run prettier? (`npm run prettier` on both front/server)
- [x] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community ([forum](https://community.gladysassistant.com/)) for testing before merging.
NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
### Zigbee2Mqtt - Migrate to ember driver
The ezsp driver in Zigbee2MQTT is deprecated in favor of the new ember driver for EmberZNet-based adapters (SkyConnect, Sonoff ZBDongle-E, TubesZB EFR32, etc.). The ember driver requires EmberZNet firmware ≥7.4.x (EZSP 13) and has been available since Z2M 1.36.0.
Currently adapters/index.js maps 6 dongles to CONFIG_KEYS.EZSP = 'ezsp'. These need to default to CONFIG_KEYS.EMBER = 'ember', while keeping ezsp available as a legacy option for users with firmware < 7.4.x.
This satisfies three requirements:
1. New users select a dongle name → get ember driver
2. Existing users whose stored dongle name is unchanged → auto-migrated to ember on next restart (the mapping lookup finds ember now)
3. Users with old firmware who need EZSP → select the (legacy ezsp driver) variant in the setup UI
## Summary by CodeRabbit
* **New Features**
* Shows Zigbee coordinator firmware and container error info in status views.
* Displays an Ember firmware warning in local setup when firmware is older than 7.4.x, with upgrade guidance.
* Shows a specific EZSP protocol-version warning in local setup when detected from container logs.
* **Chores**
* Adapter list reorganized to expose adapter type/config key and mark legacy EZSP entries.
* Added container log inspection and a migration to rename legacy EZSP entries for clarity.
If I remember correctly, ESLint wouldn’t pass without that JSDoc.
But when I test on master, ESLint passes (with just a warning ).
Anyway, I’ll restore it.
Ah, let’s see, that should pass! Normally, if it’s on master it’s because the PR that merged this bit of code passed ESLint.
Thanks!
That’s fine with me, it’s merged into master and it’s going out in the next Gladys release (should be today!).
1 Like
Ok thanks, I’ll merge when the release is live