@mschaeffler/node-red-msg-resend 2.4.1
A Node Red node to resend flow messages
@mschaeffler/node-red-msg-resend
Node Red nodes for sequencing flow messages.
Install
$ npm install @mschaeffler/node-red-msg-resend
msg-resend
A Node Red node for resending flow messages.
When a new input message arrives, it will be (re)sent to the output port at specified time intervals. This process will repeat until the next input message arrives, or until the maximum number of resends has been reached.
Thanks to Bart Butenaers for the basement I developed this node out of.
Input
| msg. | type | description |
|---|---|---|
| topic | string | topic for the output message |
| payload | payload for the output message | |
| reset | boolean | if true, resets the node; if combined with a topic, only this topic is reseted |
| resend_interval | number | changes the parameter interval for this topic; value is in msec |
| resend_max_count | number | changes the parameter maximum for this topic |
Output
| msg. | type | description |
|---|---|---|
| topic | string | same is in corresponding input message |
| payload | same is in corresponding input message | |
| counter | number | resending counter, if parameter addCounters is set |
| max | number | resending maximum, if parameter addCounters is set |
| ... | same is in corresponding input message |
Parameters
| config | type | description |
|---|---|---|
| interval | number | the intervall between two resends |
| maximum | number | the maximum number of resends; 0 is infinite |
| Contextstore | context store | context store for storing the values; none is no storage |
| byTopic | boolean | shall resending be done on a topic base |
| firstDelayed | boolean | shall the first message be sent after a intervall, or instantly |
| addCounters | boolean | shall a counter be added to the sent mesages |
| clone | boolean | shall the messages be cloned |
| Status | boolean | shows the actual value as a node status |
Example Flow
sequence
A Node Red node for sequencing flow messages into several outputs.
Any incoming message is immeditely routed to the 1st output and then after a delay of intervall to the 2nd and so on.
Input
| msg. | type | description |
|---|---|---|
| topic | string | topic for the output message |
| payload | payload for the output message | |
| reset | boolean | if true, resets the node; if combined with a topic, only this topic is reseted |
| resend_interval | number | changes the parameter interval for this topic; value is in msec |
Output
| msg. | type | description |
|---|---|---|
| topic | string | same is in corresponding input message |
| payload | same is in corresponding input message | |
| ... | same is in corresponding input message |
Parameters
| config | type | description |
|---|---|---|
| interval | number | the intervall between two steps of the sequence |
| outputs | number | the number of outputs of the node |
| Contextstore | context store | context store for storing the values; none is no storage |
| byTopic | boolean | shall resending be done on a topic base |
| clone | boolean | shall the messages be cloned |
| Status | boolean | shows the actual value as a node status |
Example Flow
Author
License
Apache-2.0
