-
Notifications
You must be signed in to change notification settings - Fork 4
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
Stop funktion does not work #4
Comments
I agree with you. I had to go back to version 1.4.1. This version works fine. |
Same here, stop function is not working in 1.4.2 Edit: I figured it out. If you send a payload of 0 or false and the topic 'control' it isn't working. If you send the payload of 0 or false without a topic it is working. Good to know. |
Same here! Workaround proposed by @pow4all does not seem to work either. I don't believe it is related to this issue, but I noticed a typo error at line 101.
I guess you meant canceled instead of cancled. |
Stop function in node red dont work. |
I confirm it's not working neither here. |
Got hit with the same problem. Quick skim through the code and it appears a |
Indeed, "cancelling" the timer might be a functional workaround for some use-cases, but actually there is a difference between "stopping" and "cancelling" the timer. The "stopping" function stops the timer and emits a "Timer Off" payload (if configured on the node) on the first output of the node, while the "cancel" function just stops the timer without emitting any output. As @MKaiser96 has stated in this thread above: if you downgrade from 1.4.2 to 1.4.1, the stopping function will work as intended. |
Any chance of this being fixed in the release version? |
When is this problem going to be fixed!!!! I am using this countdown node very much! |
Not working |
No description provided.
The text was updated successfully, but these errors were encountered: