Hello everyone... I am working on a project with a countdown/timer. I call a function every second via setInterval(). When I edit the node in the editor an deploy, cleaInterval() is not stopping the function. The function is called two times per second. One Instance is out of context. The log outp…

[image] wangenkuesse: I would expect So would I. [image] Paul-Reed: Is it because you are not storing the timer handle I don't think that is the case - that code will be live while Node-RED is live. A deploy will restart that outer function once the inner on-close has finished. Though…

Shouldn't that be - node.on("close", function () { if (tick) { clearInterval(tick); } // Corrected clearIntervall to clearInterval });

Ups... you are right... But clearInterval() without the second german "l" didn't solve the problem. node.on("close", function () { if (tick) { clearInterval(tick); } }); the same: two ticks per second.

[image] wangenkuesse: cleaInterval() is not stopping the function. The function is called two times per second. One Instance is out of context. Sorry, maybe I'm tired but I can't see an issue with that. I think you need to switch to a better code editor. When I pasted that code into VScode an…

Is it because you are not storing the timer handle? see my previous posted example - [image] clearTimeout not function General Like this @wilson2517 ... var entrada = msg.payload; var testset = context.get("testset"); // Retrieve the stored timeout reference if (entrada…

[image] Paul-Reed: Is it because you are not storing the timer handle? I would expect node.on("close", function () { if (tick) { clearInterval(tick); } }); to be executed when stopping the flow on deploy???

Just my 2c Use a let variable outside the init block and assign it the interval object within the init block later. I wonder if the var is falling out of scope after the init has executed, and being Garbage Collected? Just a guess

[image] wangenkuesse: // Parser for boolean Input const BOOL_INPUT_PARSER = { By the way, I use a small function for that rather than a big long list: /** Returns true/false or a default value for truthy/falsy and other values * @param {string|number|boolean|*} val The value…

Add some console logging so you can see what is being executed. See whether the problem is with the variable or if on close is not being called.

now it is: // run ticker every second const tick = setInterval(ticker, 1000, node.status); // kill the ticker node.on("close", function () { console.log("onClose") if (tick) { console.log("onClear") clearInte…

Maybe put a log into the ticker fn - make sure you include the node.id in the debug output.

Node-RED

Node-RED Forum

clearInterval() not working

Developing Nodes

Paul-Reed 21 September 2024 20:13 5

Is it because you are not storing the timer handle? see my previous posted example -

Topic		Replies	Views
Javascript clearInterval in if statement General function-node	6	474	4 November 2022
Interval in IF-loop is 'deaf' for injecting input General	8	558	15 July 2020
How to convert to a function General	92	5242	4 January 2019
Where to store handle of setInterval? Developing Nodes	5	613	23 November 2021
Start (setinterval) / stop (clearinterval) depending on msg.payload General	7	358	10 October 2022

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.

clearInterval() not working

Related topics