Here is the screenshot. The playroom light turns on, but the light won’t tyrn off after 10 min.
The logs show the sensor going inactive.
When I setup mine, the line for delay is “delay by 10 minutes”. Why does yours say “delay by 10 minutes cancel”?
The rule will cancel on truth change (if the sensor becomes active again).
I believe it’s because you are using a trigger. This rule may not execute when motion is inactive and may require a second rule. Use motion lighting instead. I have several rules like this one that work great.
You have it setup to trigger on Active, not on Inactive. So of course it won’t do anything upon the inactive event. You are using a Triggered Rule. You could just use a plain rule for this.
Condition: Playroom Motion Sensor active
Rule: ditto
Actions for T/F: your actions
Restrictions: Only when mode is your modes
2 Likes
I’m using this as a base to create a more complex rule (thus RM). The second part of this is to disable motion detection if the TV is on.
Check out Motion Lighting for this instead of RM. I will give you the basic motion-activated lighting logic and the disable logic. It specifically has the ability to disable motion activation based on a switch being on.
You can do it with multiple rules and Private Boolean, but that’s a pain compared to Motion Lighting.
How are you using your TV as a trigger? I have an android TV box (Shield TV) I would love to integrate more in to my home control system. I currently have tasker running commands locally but I’d like to centralize.
For the TV as a trigger, I will (eventually) setup a local Harmony Hub. I have it working in ST now using Core that motion is disabled if the TV is on. This allows someone watching a movie in the dark to move and the light remain off.
Maybe I can eventually just have a hubitat app on the shieldtv and have it relay screenOn and screenOff triggers to the hubitat. @bravenel
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
