Salut @Jac34 , je crois que je t’ai répondu, @AlexTrovato travaille sur une PR pour pouvoir s’affranchir de cette étape de configuration, afin que les appareils Zigbee2mqtt soient détectée/et configurée automatiquement.
ça se passe dans cette PR:
GladysAssistant:master ← atrovato:zigbee2mqtt-device-parser
opened 06:10PM - 19 Sep 21 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 affects code, did your 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 features/services, did you run integration comparator? (`npm run compare-translations` on front)
- [x] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)
- ~~[ ] 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).~~
- ~~[ ] Did you add fake requests data for the demo mode (`front/src/config/demo.json`) 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
Add automatic device builder from Zigbee2mqtt device definition message.
Now service read the MQTT retained message from zigbee2mqtt containing device definition and map it to Gladys device / features : https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttbridgedevices
No more "device model" mapping.
Tests from : https://community.gladysassistant.com/t/zigbee2mqtt-debug/6080/46?u=alextrovato