Predicate that traverses midnight not working

klinquist · July 25, 2021, 2:20pm

I have a rule that turns my porch light on at sunset then turns it off at 11PM.

Between 11PM and Sunrise, I want the light to turn on whenever there is motion - and turn off 5 minutes after motion is inactive.

This is my rule. I expect the light to never turn on after sunrise, but it's turning on whenever there is motion all day long.

bertabcd1234 · July 25, 2021, 5:07pm

What build are you on? A recent hotfix fixed something related to either sunrise or sunset (maybe both?) in predicates, so I'd try updating if you haven't already.

bravenel · July 25, 2021, 5:32pm

In addition to answering the question above, could you also look at the App Status page, in the Application State section, and show what the value is for "stPrimed".

klinquist · July 25, 2021, 5:46pm

Build 2.2.8.141. Updated yesterday.
I got home today to discover that my front porch was on. I just updated the above rule to start at 11:01PM instead of 11:00PM in case there was some race condition. It looks like saving that rule shut off my front porch light

stPrimed is currently false, and the light is currently not turning on with motion (correct behavior).

I will report again tomorrow, but as you can see from today's logs, the front porch light was turned on/off a lot (and there is no other rule or switch that controls it other than "turn on at sunset, turn off at 11:00PM)

dev:142021-07-25 10:37:54.541 am infoFront Porch was turned off

dev:142021-07-25 10:37:35.454 am infoFront Porch was turned on
dev:142021-07-25 10:36:19.554 am infoFront Porch was turned off
dev:142021-07-25 10:32:22.336 am infoFront Porch was turned on
dev:142021-07-25 10:31:25.774 am infoFront Porch was turned off
dev:142021-07-25 10:30:46.422 am infoFront Porch was turned on
dev:142021-07-25 10:28:41.287 am infoFront Porch was turned off
dev:142021-07-25 10:23:10.851 am infoFront Porch was turned on
dev:142021-07-25 10:08:07.289 am infoFront Porch was turned off
dev:142021-07-25 10:02:35.740 am infoFront Porch was turned on
dev:142021-07-25 09:54:05.890 am infoFront Porch was turned off
dev:142021-07-25 09:48:35.422 am infoFront Porch was turned on
dev:142021-07-25 09:40:58.413 am infoFront Porch was turned off
dev:142021-07-25 09:35:10.106 am infoFront Porch was turned on
dev:142021-07-25 09:30:59.920 am infoFront Porch was turned off
dev:142021-07-25 09:25:12.008 am infoFront Porch was turned on
dev:142021-07-25 09:21:46.615 am infoFront Porch was turned off
dev:142021-07-25 09:15:55.922 am infoFront Porch was turned on
dev:142021-07-25 07:33:24.924 am infoFront Porch was turned off
dev:142021-07-25 07:27:52.236 am infoFront Porch was turned on
dev:142021-07-25 07:20:04.393 am infoFront Porch was turned off
dev:142021-07-25 07:14:29.678 am infoFront Porch was turned on

bravenel · July 25, 2021, 6:00pm

Could you show two more things from that page (use screenshot): At the bottom, Scheduled Jobs. In the middle, Event Subscriptions.

klinquist · July 25, 2021, 6:16pm

When I changed the rule from 11:00PM to 11:01, I accidentally chose 11:01AM, which explains the "Prev Run Time"... but the rule is currently set for 11:01PM, so "Next run time" is incorrect it looks like...

Here is the rule right now...

bravenel · July 25, 2021, 7:06pm

All of that looks correct. So, let's see what happens...

klinquist · July 25, 2021, 7:18pm

Looks like the rule is still firing... went outside and saw the light on...

Name	Value	Description Text	Source	Date
switch	on	Front Porch was turned on	DEVICE	2021-07-25 12:15:10.638 PM PDT
switch	off	Front Porch was turned off	DEVICE	2021-07-25 12:08:58.496 PM PDT
switch	on	Front Porch was turned on	DEVICE	2021-07-25 12:03:20.679 PM PDT

I turned on debug logging for this device, we'll see if that gives me any more info...

bravenel · July 25, 2021, 7:32pm

Please turn on Event, Trigger and Action logging for the rule. You don't really know that this is the rule turning on the lights, just that they are turning on. Use screenshots for logs please. Look at the Front Porch device page, at the bottom, where it says In Use By, and take a screenshot of that.

klinquist · July 25, 2021, 7:36pm

Where do I turn on those logs?

Here you can see the Front Porch & Uplights Off/On rules

bravenel · July 25, 2021, 7:47pm

Alexa has "hunches", where she watches for patterns and fulfills them for you. That might be the source of this. Check the Alexa App. But, the logs for the motion rule are critical to see.

On the rule page:

klinquist · July 25, 2021, 7:52pm

There are no hunches set up... will let you know what the logs say next time.

klinquist · July 28, 2021, 5:13pm

Well... since I re-saved the rules, this hasn't recurred... so ... fixed!

klinquist · July 28, 2021, 9:56pm

I'd like to mention that I moved all of my rules (there weren't many of them) over to RE 5.0.

One of my rules had a predicate that was (Sunset-30min to Sunrise+30min).

That rule was incorrectly firing during the day, and it was the only rule (with a predicate) that DIDN'T say (Predicate False) after it. So presumably it incorrectly thought it was true.

I went in and edited the predicate, but didn't make any changes. I also turned on logging. When I re-saved it, it now shows predicate false.

So - I still think there is a bug somewhere- that perhaps only occurs on initial rule creation, but fixes itself if you re-save?

jtp10181 · July 28, 2021, 10:05pm

Just FYI I did this exact same thing in the Motion and Lighting app, was pretty simple in there. Not sure if there is an advantage to using the predicate conditions?