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

Slim down required Homie topics #86

Closed
davidgraeff opened this issue Apr 25, 2018 · 4 comments
Closed

Slim down required Homie topics #86

davidgraeff opened this issue Apr 25, 2018 · 4 comments

Comments

@davidgraeff
Copy link
Member

I thought about the effort and additional memory usage to make an existing MQTT embedded client Homie compatible (in this case ESPeasy). I noticed that Homie actually requires a lot of topics to be implemented.

Why is it required to have "$localip", "$mac", "$fw/name", "$implementation", "$stats" and other attributes.? Can those attributes be marked as "optional" or "recommended" instead?

You have to thing of what a controller essentially needs from a homie device. That is:

  • auto-discovery of the device, the nodes, the properties,
  • the property types, formats and units,
  • the device's name and state.

Everything else can be omitted for a working controller<->device communication. Right now such an implementation would violate the spec though.

@nicola-lunghi
Copy link

+1

@ThomDietrich
Copy link
Collaborator

I agree and was discussing this with @marvinroger before. We started with #48 but wanted to discuss further optional topics.
Marvin: Wdyt?

@davidgraeff
Copy link
Member Author

Oh. This is a duplicate of #45. Sorry for that.

@ThomDietrich
Copy link
Collaborator

Indeed. Let's move the discussion over there then. Would you add your OP and some additional comments over there?

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

3 participants