-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation - Recommendations on how to discover devices #93
Comments
I would be interested in what every one expects auto discovery to be, as for me that is not clear at all. |
Duplicate of #51 Please add your comments there! |
@ThomDietrich sorry, missed that some how. |
Copied from the readme:
It is absolutely not about the semantic of an input or output. It is just about controllers knowing of all available inputs and ouputs and their data types (int, bool, string, etc). |
As per title, I was thinking maybe we could alos recommend which topics and a order the order of those topics to discuss to discover a device, node and props ... Also some theory code on how to achieve discovery. This could help implentation of platforms trying to discover homie devices.
Alos maybe to same for clients devices wanting to be discovered, the best way to achieve implement. Order of messages ect
Keep in mind it's just related to mqtt discovery ect....
The text was updated successfully, but these errors were encountered: