Sorry folks, I’m at it again. I am wanting a “delay” and the DELAY node seems the right one for it. I have read that it can be adjusted with msg.delay and I am trying to set it with a slider. But it doesn’t seem to want to work. [{"id":"b9ea90e8.3238e8","type":"delay","z":"e9882c4e.450a6","name"…

If you want to use a function you don’t need anything as complex as you have. Something like this should do it [{"id":"3edc9f5b.5cfea","type":"inject","z":"6dc690a3.1abc88","name":"","topic":"delay","payload":"2000","payloadType":"num","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":100,"…

There’s something wrong with something. Indulge me: [{"id":"2e93a8b5.1f22d8","type":"inject","z":"e9882c4e.450a6","name":"","topic":"","payload":"Banana","payloadType":"str","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":210,"y":640,"wires":[["920c54cd.f416b"]]},{"id":"920c54cd.f416b","…

[image] Trying_to_learn: Ok, but still your flow wanted two inputs before it on-sent the message. It does require one of each before the first message will be sent out, but only the first time. Thereafter each value message will be delayed by the time from the most recent delay message. I as…

Thanks Colin. While we were both working on the “problem”, I got this: Excuse the mess. But it works. I wouldn’t mind getting rid of the extra junk in the function block, but that’s work in progress. [{"id":"522c2349.6c1c3c","type":"debug","z":"e9882c4e.450a6","name":"","active":true,"tosidebar…

I like your way better. I was NEARLY there with what I was doing. I am still (will I ever?) not confident about the conditional stuff how you did it. Ok to ask my questions now? As we seem both to have written the same function in that node.

Yes, we have ended up with similar results, a case of parallel evolution I think. I don’t think the first three lines of your function are necessary, use msg.topic in line 4 instead. Also I am not sure what effect passing an undefined value to the delay node will be (as is the case if you send the …

Great to hear we are similar in our thinking. I seem to be (still ?) confused with what the context.blah and var things. My thinking is: (excuse the rant) The message comes in. The delay is in msg.delay If the msg.delay is “valid” store this. From what I get this has to be via CONTEXT, as it…

[image] Trying_to_learn: The delay is in msg.delay No, it is in msg.payload if msg.topic is delay. You didn't need the first lines because it set a variable to msg.delay, and msg.delay at this point is not set. You didn't need the second line because it wrote (using the obsolete context for…

Yes, and again: Thanks for the help. Ok, to re-cap: You did what I did in another case where you sent the value in the payload - given - but tagged the message with the topic. I was mistaken for a long time that it was actually msg.delay which is what the node wants. But you “cheated” and until…

[image] Trying_to_learn: Ok, the “default time” part. Yes, ok, if the node has a default value. It is really academic as it shouldn’t really ever be in the state where there is no value set. But to be a good programmer, I probably should put it in there. It will be in the undefined state when…

The DELAY node. Not doing what I want

General

davidcgu 18 June 2018 19:00 28

Just discover something that I think deserves to be pointed… once you set the delay with the msg.delay it doesnt matter anymore what time base you set on the delay node, will works always on miliseconds.

Regards

2 Likes

Topic		Replies	Views
Delay node with variable delay General	5	9527	28 November 2019
Can I have a delay / sleep inside Function node General	34	44136	7 February 2024
Send 1st msg, delay from value in context, send second msg General function-node	1	359	22 June 2022
Delay in function v1.0.2 General	11	3805	29 October 2019
Adding a delay in a for loop in the function node General	11	9324	20 February 2019

The DELAY node. Not doing what I want

Related topics