Rule with time between not working if it spans midnight?

I have a rule that only operates between a certain time period when an event fires. But the time test shows false in the log even though the log timestamp shows it should be true:

2023-04-11 02:15:45.163 PM Event: Doorbell Camera smartDetectType waiting
2023-04-11 02:15:10.881 PM Action: END-IF
2023-04-11 02:15:10.879 PM Action: END-IF
2023-04-11 02:15:10.877 PM Action: Notify SM-N960U, SM-T837V, SM-S908U, SM-G996U, SM-G975U, SM-T817V, SM-T867V: 'Got the cat!' (skipped)
2023-04-11 02:15:10.872 PM Action: Off: Bhyve Flower Beds --> delayed: 0:00:15 (skipped)
2023-04-11 02:15:10.868 PM Action: On: Bhyve Flower Beds (skipped)
2023-04-11 02:15:10.865 PM Action: IF (Time between 9:00 PM and 11:59 PM(F) OR Time between 1:00 AM and 4:00 AM(F) [FALSE]) THEN (skipping) <---- shouldn't this piece be TRUE???
2023-04-11 02:15:10.814 PM Action: IF (Bhyve Driveway Corner, Bhyve Driveway. Right, Bhyve Flower Beds, Bhyve Front Yard, Near, Bhyve Driveway, Left, Bhyve Front Yard, Middle, Bhyve House, Left Front, Bhyve House, Back Right, Bhyve House, Back Left(off, off, off, off, off, off, off, off, off) all off(T) [TRUE]) THEN
2023-04-11 02:15:10.452 PM Triggered: Doorbell Camera reported smartDetectType(Human) = Human
2023-04-11 02:15:10.431 PM Event: Doorbell Camera smartDetectType Human

No, 2:15 PM is not between 9:59 PM and 11:59 PM or between 1 AM and 4 AM. Did you mean PM in that last expression? Then it would be.

OOPs I Posted the wrong log entry. I'll update this with a new log entry in the morning.

Sorry for the wasted time.

Hal

While you're on that, make sure you're also running the latest platform version. There was a fix something related a while back, though I don't think conditional actions the selves were affected.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.