node-red-contrib-looptimer2 0.0.2
Sends msg to the first output continually, once per specified time, till a msg with any topic of 'stop' or 'STOP' is received on input.
Loop Timer 2 for node-red
This node fixes a loop timer node problem. When you send "stop" as an msg string to the node and then run the loop again, it will execute as expected, unlike the original node.
Sends the msg through the first output, then continues to do so in a loop, once per the timer duration specified, until a payload of stop or STOP is received, at which time the second output will automatically send a payload of stopped.
Sends msg to the first output continually, once per specified time, till a msg with any topic of stop or STOP is received, at which time the second output will automatically send a payload of stopped.
You can also stop the loop by specifying a maximum number of loops, which when reached, will stop the loop and timer, as well as sending a payload of max loops reached through the second output. Keep in mind, the first msg simply passes through, and is therefore not part of the loop. So if you set the max loops to 5, you will get 6 messages, which is 1 original message, and 5 messages from the loop.
Finally, to ensure you do not end up with an infinite loop, you can set a maximum timeout in seconds, minutes or hours, and when that time is reached, the loop and timer will also be stopped.
Setting the Max Loops and Max Timeout settings to high values can, for all intents, ensure that the loop can only be stopped by an incoming stop payload, however, the stability of the loop has not been tested over an extended number of hours.
