svrooij
commented
3 years ago I don't know the homieiot convention, but you can always add new topics to output the data.
If you keep the following in mind, that would make accepting the PR easier:
- Start your changes from the
betabranch. - No changes to the current functionality.
- Add config switch (boolean) to enable this optional functionality.
- Also document the changes, maybe subpage of integrations
- I would suggest that you use the SonosCommandMapping for controlling stuff, that way if we implement new functionality the user can also use it in the your convention.
slobberbone
It would be interesting to implement in this project the specification describe here : https://homieiot.github.io/
However, MQTT doesn’t define the structure and content of these messages and their relation. An IoT device publishes data and provides interaction possibilities but a controlling entity will need to be specifically configured to be able to interface with the device.
The Homie convention defines a standardized way of how IoT devices and services announce themselves and their data on the MQTT broker.
It is thereby a crucial aspect on top of the MQTT protocol for automatic discovery, configuration and usage of devices and services.
Some other xxx2mqtt already purpose this and I think specification for MQTT is the futur of home automation. It would be not changing the way of this project work actually, but add another way to publish.
I'm from the open source project NextDom (home automation software) and we are working on another solution from scratch. We want to organize NextDom directly with MQTT and Node-Red (Nextdom becoming a kind of orchestrator. In this way, this standard for MQTT will be very interesting for us of course, but also for all others home automation software.
Thanks for reading and give me some feed back about that !