feat(mqtt): report the router's own MQTT exposure to the embedded agent - #408
Merged
Merged
Conversation
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
1 participant
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.
NetGrip exposes itself to Home Assistant over MQTT, but NetPulse did not know
it, so its fleet publisher kept a per-router device with 6 entities as well:
two devices per router in Home Assistant.
The embedded agent now reports the live state of NetGrip's own MQTT client
(enabled and node id) through the agent payload's
mqttsection, reading thecurrent config on every push so the toggle is reflected without restarting the
agent. Bumps the agent dependency to v1.3.0, which carries the section.
Closes #407