Skip to content

Mqtt discovery optional nodeid #2840

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

Merged

Conversation

AlexMekkering
Copy link
Contributor

Description:
This PR adds support for an optional <node_id> level to MQTT discovery topics. This supports all config topics which match the pattern <prefix_topic>/<component>/[<node_id>/]<object_id>/config.
The purpose is to give other clients more means to only subscribe to their own command topics (e.g. when switches and/or lights are involved) by using one single wildcarded subscription topic like homeassistant/+/<own_node_id>/+/set instead of subscribing to every topic they're interested in.
When multiple MQTT clients are involved, this will minimize the load on them because they'll only get their own topics forwarded by the MQTT server.

Pull request in home-assistant (if applicable): home-assistant/core#8096

@mention-bot
Copy link

@AlexMekkering, thanks for your PR! By analyzing the history of the files in this pull request, we identified @fabaff and @ih8gates to be potential reviewers.

@Landrash Landrash added the new-feature This PR adds documentation for a new Home Assistant feature to an existing integration label Jun 19, 2017
@balloob balloob merged commit 55bec87 into home-assistant:next Jun 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-feature This PR adds documentation for a new Home Assistant feature to an existing integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants