Hello,
I don’t know when the problem started, but I noticed that even when I click ‹ Update › for the following devices, they return to the same state:
Do you have the same problem?
I’m using an external Z2M (Zigbee2MQTT) running 2.7.2
I can reproduce it as well!
Can someone create a GitHub issue to keep track of the bug?
Same for me, with the Z2M integrated into Gladys.
@pierre-gilles I was wondering what the consequences are of not updating devices in the Zigbee integration? Since you don’t say in a new release that this bug is fixed, I no longer click the ‹ update › buttons, but I don’t know if that’s the right thing to do or not…
1 Like
This issue hasn’t been fixed yet, but it has no impact. It’s just a small visual glitch in the interface, with no consequences
4 Likes
Hi everyone,
I’ve worked on a fix that has been merged and will be included in the next version of Gladys:
master ← fix-zigbee2mqtt-device-update-bug
ouvert 03:15PM - 23 Mar 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] If you are adding a new feature/service, did you run the integration comparator? (`npm run compare-translations` on front)
- [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.
- [x] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)
- [x] If you are adding a new features/services which needs explanation, did you modify the user documentation? See [the GitHub repo](https://github.com/GladysAssistant/v4-website) and the [website](https://gladysassistant.com).
- [x] Did you add fake requests data for the demo mode (`front/src/config/demo.js`) so that the demo website is working without a backend? (if needed) See [https://demo.gladysassistant.com](https://demo.gladysassistant.com).
NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
### Description of change
Fix https://github.com/GladysAssistant/Gladys/issues/2411
## Summary by CodeRabbit
* **Bug Fixes**
* Improved detection and handling of energy consumption and cost features by standardizing how existing features are identified, preventing duplicates and preserving correct feature links.
* **Tests**
* Updated and strengthened tests to validate the revised feature identification, external-id consistency, and non-duplication behavior.
Thanks everyone for your patience
4 Likes
The fix is live in Gladys Assistant 4.72:
Bonsoir à tous !
Gladys Assistant 4.72.0 est disponible
Nouvelles fonctionnalités
Zigbee : Support du double on/off pour bouton IKEA BILRESA Le bouton IKEA BILRESA est maintenant pleinement supporté via Zigbee2mqtt.
IA : Réduction de la latence et des coûts Les images de caméras envoyées à l’IA sont maintenant redimensionnées avant envoi, ce qui réduit la latence et le coût des appels.
Liste des intégrations : Ajout de tags Les intégrations sont maintenant taguées (local, cloud, Gla…
1 Like