-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After counter down is stopped by sending payload = 0 or false, the count down output continues! #10
Comments
hello dachshund-digital, I can not recreate the behavior you are reporting. Using the flow I pasted in below, once I send "false" the countdown stops and a final msg.payload "0" is output.
|
That is ok, I changed the flow so I don't need the count down node. When I get a bit of time, I will try to give you example of the issue... if I can recreate it again. Thanks for looking into my issue/question. Appreciate it. |
I am having a similar "issue": but I think its how its currently supposed to work. |
NODE-RED 3.0.2 Counter doesnt stop on demand, i have imported your code from this post to be sure, but no reaction on stop. |
I'm having the same issue. I can't stop the countdown with either 0 or false. The example code doesn't work when imported into Node Red (3.0.2) running on Home Assistant (2023.1.7). Am keen to make use of it if possible. Thanks, |
I also am unable to stop the timer once it has started. I copied in the sample with two different stop buttons and neither of them works to stop it. |
After counter down is stopped by sending payload = 0 or false, the count down continues reporting a payload message over and over, endlessly. This does not make any sense, if the count down is complete, either termination or completion of count, output should not continue endlessly.
The text was updated successfully, but these errors were encountered: