-
Notifications
You must be signed in to change notification settings - Fork 59
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
Comments
+1 |
I agree and was discussing this with @marvinroger before. We started with #48 but wanted to discuss further optional topics. |
Oh. This is a duplicate of #45. Sorry for that. |
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
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:
Everything else can be omitted for a working controller<->device communication. Right now such an implementation would violate the spec though.
The text was updated successfully, but these errors were encountered: