This rule works about half of the evenings and other times it does not. It used to be reliable until the most recent HE updates. Has anyone else experienced this type of issue?
Notwithstanding the fact that your rule should work and it is clean and simple. Rules are cheap, have you tried breaking them up so it's one rule to turn on and another to turn off to see if that is more reliable? Based on other's experience you may find that opening and re-saving the rule may help, too.
What triggers the mode to evening and what triggers the mode to night?
Hopefully you set up modes?
Yes, I have mode manager running and the logs show the mode changes at the correct time.
1 Like
Why not do this in Simple Automations? I think this is how you would set it up. My modes are different than yours, but same idea.
I took your lead and created a simple automation. Not sure why RM was not working. Give me a couple days and I will see if this fixes things. Thx.
1 Like
I was kind of hoping there was an issue with the mode changes but the only other thing I could think of is the amount of time that passes for that wait command.
The good/bad of rule machine is there are a million ways to do this. Don’t know if it’s any better at all but if it was me, this is how I would personally write the rule. (See screenshot above.
Below is a link to download the json if you want to import into rule machine and see if it works for you.
https://www.icloud.com/iclouddrive/07_lRhRiA8lJVFLflTwnG1htQ#Modetest
I tried the simple rule and it too was flaky. I crafted an RM rule following your suggested approach and I will see how it works. Thanks so much for the help.
1 Like
I wanted to get back to you and thank you for your approach. It seems that testing the mode as a trigger and then running actions according to which mode was a much better way to do this than I initially had. The routine appears to be very reliable now. Thanks again for your help.
