Skip to content
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

Closed
timpur opened this issue May 2, 2018 · 4 comments
Closed

Documentation - Recommendations on how to discover devices #93

timpur opened this issue May 2, 2018 · 4 comments

Comments

@timpur
Copy link
Contributor

timpur commented May 2, 2018

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....

@timpur timpur changed the title Documentation - Recommendations on how to discover Documentation - Recommendations on how to discover devices May 2, 2018
@ingoogni
Copy link

ingoogni commented May 2, 2018

I would be interested in what every one expects auto discovery to be, as for me that is not clear at all.
Two non related devices for example, lets have a temperature sensor and lets have a PID controller, what is there to discover and what can be done with that.

@ThomDietrich
Copy link
Collaborator

ThomDietrich commented May 2, 2018

Duplicate of #51

Please add your comments there!

@ThomDietrich ThomDietrich marked this as a duplicate of #51 May 2, 2018
@timpur
Copy link
Contributor Author

timpur commented May 2, 2018

@ThomDietrich sorry, missed that some how.

@timpur timpur closed this as completed May 2, 2018
@davidgraeff
Copy link
Member

Copied from the readme:

The Homie convention strives to be a communication definition on top of MQTT between IoT devices and controlling entities.

MQTT supports easy and unrestricted message-based communication. 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 communication channel. The Homie convention is thereby a crucial aspect in the support of automatic discovery, configuration and usage of devices and services over the MQTT protocol.

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants