frodovdr/node-red
1
0
Fork 0
mirror of https://github.com/node-red/node-red.git synced 2023-10-10 13:36:53 +02:00
Code Issues Releases Wiki Activity

Update trigger help

Browse Source
This commit is contained in:
Nick O'Leary 2017-06-05 14:01:24 +01:00
parent 6c2de40dba
commit 7502a2b1ff
No known key found for this signature in database
GPG Key ID: 4F2157149161A6C9
1 changed files with 25 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
nodes/core/core/89-trigger.html
View File

@ -63,23 +63,31 @@
</script> </script>
<script type="text/x-red" data-help-name="trigger"> <script type="text/x-red" data-help-name="trigger">
<p>Creates two messages on the output separated by a timeout whenever <i>any</i> <code>msg</code> arrives on the input.</p> <p>Sends a message if nothing is received within a set time interval or until reset.</p>
<p>For example, this can be used to toggle a Raspberry PI GPIO pin on and off.</p>
<p>The two output states can be specified as can the duration of the timer. <h3>Inputs</h3>
Either output can be set to a value, or templated from the inbound <dl class="message-properties">
<code>msg</code> using mustache syntax. <pre>The payload is {{payload}}</pre></p> <dt class="optional">reset</dt>
<p>Or you can pass through either the <i>original msg</i> or the <i>latest msg</i> to arrive.</p> <dd>If a message is received with this property, any timeout or repeat
<p>Optionally the timer can be extended by being retriggered... or not.</p> currently in progress will be cleared and no message triggered.</dd>
<p>By setting the first output to <i>nothing</i>, and selecting extend timer - a watchdog timer can be created. </dl>
No output will happen as long as repeated inputs occur within the timeout period.</p>
<p>Setting the timer to 0 creates an "infinite" timeout - the first output will happen but the second <h3>Details</h3>
never will, and neither can the first be retriggered - so a true one shot.</p> <p>This node can be used to create a timeout within a flow. By default, when
<p>If a <code>msg.reset</code> property is present, or the <code>msg.payload</code> it receives a message, it sends on a message with a <code>payload</code> of <code>1</code>.
matches the optional reset value, any timeout or repeat currently in progress It then waits 250ms before sending a second message with a <code>payload</code> of <code>0</code>.
will be cleared and the second output will not happen.</p> This could be used, for example, to blink an LED attached to a Raspberry PI GPIO pin.</p>
<p>The node can be set to repeat the input <code>msg</code> at regular intervals until the input changes, <p>The payloads of each message sent can be configured to a variety of values, including
or the node is reset.</p> the option to not send anything. For example, setting the initial message to <i>nothing</i> and
<p>The blue status icon will be visible while the node is active.</p> selecting the option to extend the timer with each received message, the node will
act as a watchdog timer; only sending a message if nothing is received within the
set interval.</p>
<p>If set to a <i>string</i> type, the node supports the mustache template syntax.</p>
<p>If the node receives a message with a <code>reset</code> property, or a <code>payload</code>
that matches that configured in the node, any timeout or repeat currently in
progress will be cleared and no message triggered.</o>
<p>The node can be configured to resend a message at a regular interval until it
is reset by a received message.</p>
</script> </script>
<script type="text/javascript"> <script type="text/javascript">