Mqtt discovery optional nodeid#2840
Merged
balloob merged 4 commits intoJun 24, 2017
Merged
Conversation
|
@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. |
3 tasks
Landrash
added
the
new-feature
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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>/+/setinstead 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