3/28/2024 0 Comments Set timer 1 minuteWhat does that mean? A couple of examples will help here. If you ENABLE it (check the checkbox) then if the stoptimer is running and you re-Deploy the flow, or restart Node-RED, then the timer will automatically restart itself where it should be. For the purposes of the node status and output 3, except in theĬase where Reporting is set to None, the milliseconds are not displayed or provided on the 3rd output as it wouldn't make sense based on the available While you can set Milliseconds, I would not rely on the accuracy for anything critical. In the case of an unknown string, a warning message will appear in the Debug logs. In the absense of a 'msg.units', or an unknown string in msg.units the units configured within the node will be used. If the input contains 'msg.units', with a value of "Milliseconds", "Seconds", "Minutes" or "Hours" then that will over-ride what is defaulted in the node. If the value of 'msg.delay' is less than 0, then 0 is used. In the absense of a 'msg.delay', or a value in 'msg.delay' that can not be converted to an int, the value configured within the node will be used. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |