Updated the MQTT component to optionally filter its messages by topic paths#1503
Closed
JohnVidler wants to merge 1 commit intoOpenEMS:developfrom
Closed
Updated the MQTT component to optionally filter its messages by topic paths#1503JohnVidler wants to merge 1 commit intoOpenEMS:developfrom
JohnVidler wants to merge 1 commit intoOpenEMS:developfrom
Conversation
|
This PR has been automatically marked as stale due to inactivity. It will be closed in 7 days if no further activity occurs. |
Contributor
|
implemented with #3321 |
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
2 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.
The current implementation of MQTT can turn in to a bit of a fire hose of data for situations where you only want some of the fields possible. This patch adds a filter function which inhibits certain topics from actually sending to the broker, instead they silently complete, doing nothing.
A single new configuration string has been added, into which a semicolon-delimited set of topic filters can be written allowing only topics which match these specifications to pass.
The topic filters use the same syntax as normal MQTT client subscriptions, so can use the
+and#specifiers to indicate single, or multi-level paths.An example path might be
edge/fems33/channel/meter+/+which would pull all metrics in meter0, meter1, etc. paths, but exclude any other topics.THIS NEEDS TESTING - Please can someone with an otherwise working setup please check that this works, as I'm currently unable to, as I don't have access to our test hardware.