RM date-driven rules did not change state

Great, thanks Bruce!

Related question for you: Is it better practice to have something with specific dates as a restriction rather than a condition? If a rule is restricted, it won't evaluate at all, correct? Or in the grand scheme of things will it really not matter?

Added day of week, now have midnight scheduled event. Should I see a sunset event here?

**edit - I checked another sunset-to-sunrise rule and it doesn't show sunset or sunrise scheduled events, so this must be ok...

That all depends on whether or not you need to have the rule be evaluated at certain times. For example, if something needs to happen when the date changes, then it would have to be a condition, not a restriction. If you just wanted the rule not to run on certain dates, then a restriction would work.

Okay...makes sense. If a rule is restricted to a specific date range, that restriction comes off at midnight, correct?


@bravenel this same rule had an event at sunrise-1 this morning but did not change state to false correctly. I had to go in and tap done, then it changed correctly. Any idea what's going on? This is the one I added day of week to in order to force the midnight evaluation.

Here's the full rule:

Scheduled jobs, before tapping done:

Events tab shows that something happened at sunrise-1, but the rule state did not change to False:

After tapping Done, rule state changed:

Scheduled jobs after tapping Done;

Not a clue why it didn't go false.

I didn't get screenshots, but it was doing something else weird before I tapped Done to manually evaluate.

Go into rule, tap the settings cog. Title would show [false] (Repeating)
Tap on Events, then tap App Status to go back to settings page, title would show [true] (Repeating)

I noticed this while getting screenshots. It's not doing it now.

Deleted the rule and recreated. We will see a year from now if it works right :rofl:

Having similar issue...
I have a triggered event based on time of day...
It sends http request to turn a light on and then
a few minutes later sends a brighten command...
was working fine... I had it date restricted November 25 to January 10th...

stopped sending the http command on Jan 1... the other commands to that device that are not date restricted continue to work fine...

A post was split to a new topic: Missed sunset event