@ajwest wrote:
Hello, I have a Time Trigger automation setup to turn my thermostat down at 22:00, but sometimes I am still awake and moving around in my apartment. I’d like the action at 22:00 to delay until it hasn’t seen movement for 10 minutes.
My plain Time Trigger looks like this:
- id: '1579145331076' alias: Living Room Temperature Schedule Evening Off description: '' trigger: - at: '22:00:00' platform: time condition: [] action: - data: entity_id: climate.remote_temp temperature: 16 service: climate.set_temperature
I think I could add a “condition” like:
- condition: state entity_id: binary_sensor.living_room_sensor_motion state: 'off'
…but this would just skip the action altogether if there is still movement*. How can I get it to keep checking for movement after 22:00 and when there’s no longer any motion, continue the automation action to turn down the heat?
* Also the motion is only ever “on” for a few seconds every time it detects motion, so there’s still some likelihood that that condition wouldn’t stop it from continuing anyway because there are little windows where motion isn’t detected; it really needs to be “motion hasn’t been detected for x minutes.”
Thanks for any guidance you can help me with here!
Posts: 4
Participants: 3