Emit message on output shortly after the configuration is applied #13
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
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.
This pull requests changes the
confignode's behavior to emit a message with the current timestamp shorty after the configuration is applied.A short delay (100 ms) is needed for Node RED to finish configuring and wiring the node - this behavior mimics the behavior of
injectnode.Reasoning behind the change is as follows: I have several flows where I have to post-process the configuration (e.g. generate a list of MQTT topics to subscribe to - based on the values from the configuration node). I've been successfully handling this by running a periodic
injectmessage every minute or so to trigger the post-processing so far. In one project, though, I need a much faster response times to eventual configuration changes and emitting a message after the configuration is reset seems the most appropriate way to achieve this.