Add configuration key for MQTT client ID #220
Merged
Conversation
This file contains 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
The `id` key in the `mqtt` section of the configuration can be used to supply a unique ID for each service instance. When multiple insteon-mqtt services are connected to the same MQTT broker, they could be configured to use separate topics, but not separate client IDs. This resulted in the broker breaking the connections as the services connected and reconnected. Signed-off-by: Kevin P. Fleming <[email protected]>
|
Thanks. I'm going to add a commented out id input in the sample config.yaml file. That's the only doc's for the yaml entries right now - otherwise no one will know that this option exists. I'll also add this into the release notes. |
|
You're very welcome! This project is fantastic, I've got two instances running on my network now (house and garage, using 2413U PLMs) and it's fast and easy to configure. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
idkey in themqttsection of the configuration can be used tosupply a unique ID for each service instance.
When multiple insteon-mqtt services are connected to the same MQTT broker,
they could be configured to use separate topics, but not separate client IDs.
This resulted in the broker breaking the connections as the services connected
and reconnected.