Forgive me if I've asked this before, but from what I remember it was the DELAY node, not the TRIGGER node. Here's the part of the flow..... [{"id":"178ae8cd.12b0d7","type":"trigger","z":"15af81c5.64999e","op1":"","op2":"2","op1type":"nul","op2type":"num","duration":"60","extend":false,"units":"mi…

[image] Trying_to_learn: Forgive me if I've asked this before, but from what I remember it was the DELAY node, not the TRIGGER node. I found your previous inquire. At that point in time you asked how to change the interval if using the inject node. Colin proposed a flow using the delay node.…

Yes, but that sends an output at a given interval. This more sends one output (per node) when it is triggered/"stimulated". When an event happens I want a sequence of things happening (once) after then at given times. As is, it is 30 minutes. If I want to change it to 45, I have to edit all the …

I see. Perhaps something like posted in the below post from the old forum ? [r-01] https://groups.google.com/forum/#!topic/node-red/vtvuXaLY0Zk The first function node is where you define the timing. It is easy to modify the amount of "triggers" (virtual triggers) and what data to send for each…

In which case the modified version to suit your needs would be: and you are free to change any delay for each step (in a single place): // Define runtime1 (4 seconds) msg.runtime1 = 4*1000; // Define runtime2 (2 seconds) msg.runtime2 = 2*1000; // Define runtime3 (7 seconds) msg.runtime3 = 7*1000…

Thanks. It loops back and keeps going, but I think I can work out how to make it stop itself after 1 loop. --via edit-- Ok, I am dumb. In the initialize function node I see: //Stop criteria is false global.set("StopFan",false); So, reading that I set "StopFan" to true to stop it. But then whe…

I misread your OP. Only now I realised that you don´t need the flow to keep looping until it receives some command to stop. It is just one loop. In such case the flow could be much simpler. All you need is to make the loop to read the pre set values and then send a msg.reset to the delay node.

I've nearly got it. This is (now) what I have: [{"id":"c5192ec4.39a838","type":"function","z":"6c223db0.773914","name":"Cycle next fan","func":"switch (msg.next) {\n \n case 1:\n msg.delay = msg.runtime1;\n msg.payload = 1; \n msg.next = 2;\n break;\n case 2:\n…

Indeed, you got the idea I had a look in your very first flow, the one that uses the trigger nodes. The behavior of that flow is to first wait for a delay and only then send the first message. The one i suggested behaves differently: it first sends the message and then wait for a delay. Here a m…

I'll look soon. The idea is that an event happens. Say: Sunset. The flow sends a message. Then after a given time, a new message is sent. After that time again, another message is sent. That goes on until I am done. When done, an "OFF" message is sent. The times between the messages is wha…

Thanks for that idea! I didn't think of doing it that way with the reset function/command. case 5: msg.reset = true; break; But..... Don't worry. I'll nut it out.

Node-RED

Node-RED Forum

Trigger node help - please

General

Andrei 31 May 2019 12:48 2

I found your previous inquire. At that point in time you asked how to change the interval if using the inject node. Colin proposed a flow using the delay node. I found it a smart solution and save the flow in my favorites folder.

Topic		Replies	Views
Changing the inject node repeat option from UI General	10	3975	13 April 2023
Triggering on specific message General	37	1683	16 October 2020
Simple pulse generator General delay	8	1756	16 April 2022
Creating a function with a loop with input from Dashboard General node-red-dashboard , function-node	9	328	6 February 2023
Inject node - repeat. Stuck if it can be set externally General	7	5545	9 February 2020

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Trigger node help - please

Related topics