I have a rule in Rule Machine 5.1 that is supposed to trigger after a hub variable changes to true and stays that way for 10 minutes but it seems to fire right away. I can use a virtual switch and set that to trigger only if it stays on for 10 minutes and that works as it should. Is there a bug for hub variables staying on being a trigger? I just updated to 2.3.3.130 but it was happening in 2.3.3.128 as well. That was the version I created the rule in so I don't know when that option worked last.
Thanks!
Can you post a screen shot of your rule?
The only reason I have the zTest switch-2 in there was for testing the "stays that way" with the switch which seems to work fine
You have the same variable, awayRandomMBLights, selected for two triggers with two different "stays" values. It will trigger on the first, so I'm not sure you really need the second. This probably could be handled differently since triggering immediately is a bit unexpected, but this is an unusual setup. There is likely another way to do whatever your goal is if this is intentional.
If that was not intentional, it should work as expected if the triggers are two different variables. I just tested that, and it worked. But by accident, I also happened to make a rule where I used the same variable for two different sticky triggers (I didn't see that yours was like that but also didn't mean to try--just clicked wrong) and found the same behavior as you.
I did confirm that if I delete the 2nd trigger it does work correctly. It is the same variable but one is for staying true and one is for staying false so that is why there are 2 separate triggers. Basically when the variable is true I want the rule to repeat and when it returns to false I want it to stop the repeating but due to other rules I want the variable to stay set for a certain amount of time before starting/stopping the rules hence the "stays" option. I can work around it if that is just how it is. It just seemed odd that it didnt work. Thank you for your quick response!
1 Like
Missed that, too! My triggers were testing for the same values. But I guess that didn't end up mattering.
This seems unexpected, though. Maybe something for @bravenel to look into.
Using the same variable in two stays triggers like this will not work. The code doesn't have the means to disambiguate which is which.
If this is really what you want to do, use two rules, and have one invoke the actions of the other.
Sounds good. Thanks again for the fast response!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
