Rule Suddenly Not Triggering

I have a rule set up to turn off a lamp in my office when either the illumination exceeds a preset amount for a certain period of time OR when there is no motion detected in the office after another period of time. This was previously working fine, but something broke and I'm not exactly sure what.

Here's my rule:

The required expression is expecting a hub variable (flagOfficeLampSensorActive) to be True. This is set by a button so that I can override the light turning on/off. As far as I can tell this is working fine.

As you can see in the example, the condition is met for the boolean and the illumination has exceeded the threshold (100 lux) for greater than the specified two minutes, but the rule is not getting triggered.

I'm seeing the following in the logs:

Is there something obvious preventing the rule from getting triggered by the illumination levels, or is there a better way to write this? I'm at a bit of a loss.

Based on the logs, it looks like at 5:12:48.200 pm it should have run, but you’re saying it didn’t? I wonder if the trigger events might be conflicting with each other somehow?

What happens if you separate it in 2 rules, each with one of the triggers?

Thanks, Sebastien. And correct -- it didn't run at that 5:12:48.200 pm.

I was also curious whether the trigger events may somehow be conflicting. I went through and refreshed all my devices and manually triggered the rule and some other stuff, and it looked like it started working again, but now I have a new theory: I think it may somehow be ANDing the rules instead of ORing. So it only triggers specifically when the two conditions are met (no motion for >10 mins AND lux>100 for >2 mins).

Separating into two rules makes a lot of sense. I'll try that and see if it results in a fix.

Appreciate the help!

1 Like

Are you up to date with hub updates?

Download the Hubitat app