![]() ![]() If the input contains msg.delay, then the delay will be 'msg.delay' units of time, where the units are whatever the units are defaulted to in the node iteself. Overriding the node via incoming messages The default is hh:mm:ss (string), but it can be configured to present that as the total number of reamining seconds or minutes or hours (number). ![]() The format of the 3rd output reporting (and status) are defined by the "Reporting Format" option. (for example: 2.5 minutes will decrement to 2 minutes, then 1 minute, then every second down to zero) In that case, the first update will be for the partial minute, after which it will operate as noted above. The exception to this rule is if your duration is not a minute increment. ![]() At the 1 minute point, it will switch to reporting every second. While there is more than 1 minute remaining, the timer will decrement every minute.The status below the node as well as the third output can be configured to update at a frequency of: The third output will send the time remaining as time ticks away. If the timer is stopped, the second and third output will automatically send a payload of 'stopped'. The second output allows you to send an additional payload of a number, string or boolean when the timer completes. If a new msg is received before the timer has ended, it will replace the existing msg and the timer will be restarted, unless the new msg has a payload of 'stop' or 'STOP', in which case it will stop the timer. Sends the received msg through the first output after the set timer duration. Npm install node-red-contrib-stoptimer-varidelay General usage It can be configured to be persistent across reboot/restarts/redeploys. It also allows the node to stop the output. This node allows for pre-configured, or dynamic delay. Node-red-contrib-stoptimer-varidelay 0.5.3 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |