With the treshold control you can enable or disable a delayed output when the input passes the on or off threshold.
There are a few values that need configuration before the node can be used:
msg.payload
to send when the on threshold get passed (and the counter reaches zero).msg.payload
to send when the off threshold get passed (and the counter reaches zero).msg.payload
, the onDelay counter counts down to zero. If that hass passed, a "on" msg.payload
gets send to the first output._msg.payload
, the offDelay counter counts down to zero. If that hass passed, a "off" msg.payload
gets send to the first output.The on threshold should be higher than the off threshold.
Note that the delay is in whole seconds. It rounds it to the nearest integer when input is not in whole seconds.
By default the node listens to msg.payload
as input.
It also listens to different messages, which can change the configured values:
msg.onThreshold
- The on thresholdmsg.offThreshold
- The off thresholdmsg.onDelay
- The on delay in secondsmsg.offDelay
- The off delay in secondsThere are three outputs. The first one just gives "on" or "off" (after the delay has passed).
The second output gives the state of the counter for the on delay.
The third output gives the state of the couter for the off delay.
Both second and third outputs also publish a msg.blink
that is 0
or 1
when the counter is even or odd.
The status node tries to show the current state. It can turn red on wrong input and on the "off" state, green on the "on" state and yellow when the on or off counter is running.
When you do a fresh deploy and then inject values within the hysteresis region (between on and off thresholds) the Node status will be displayed as "unknown" with a blue dot.