I'm wondering whether this is because sunrise is set for tomorrow once it happens, so at 8:30am the condition of between 1am and sunrise is actually true?
This seems to back up my theory.... With a bit of creative thinking... you will see that at sunrise (6:23am this morning for me) sunrise is set to 7:24pm UTC, which, if you add 11 hours (we're in daylight savings) becomes 6:24am tomorrow. So if, 2 hours later my fictional children turned on the TV I would think a 1am to sunrise expression may resolve as true...
I'm thinking you need some rule or similar setup to set a variable / switch at sunrise that stops the rule from firing.... Hang on, I might have that round the wrong way.... Maybe you need a mode or time restriction.... Too hard to think about at this time of night.... 
Can you not tell them it will be fixed in the next platform release..... 
Except RM clearly shows that it evaluated as false
1 Like
It depends when sunrise is for Lewis (I think)
Well, the first trigger of the rule was when we were putting the kids to sleep so I don't think it should have even evaluated the triggers by that point.
That is "live" when you are viewing / opening the page for the rule. It all depends on the value of sunrise when the kids turn on the TV and how RM evaluates 1am to Sunrise at that point.
The rule has been in place for a while now, it just freaks out every now and then for no observable reason. But the required expression was false so it shouldn't have even looked at the triggers. I switched it to 7am just to rule out some weird sunrise bug. We'll see how it goes.
2 Likes
How did it go? It's been a couple weeks now, did it do it with the end time at 7 am?
There seems to be a lot of small bugs regarding dates or times in the required expression. Your log shows there is obviously a problem, hope this can be reported and fixed. Required expression is a useful feature, but not so good if it's got intermittent problems.
Worked for me changing to time instead.
