Light switch through motion and switch, with timer resetted by timer

pidewo481 · September 10, 2023, 7:15am

Hi,

I have a motion sensor in my toilet, and the light and ventilation after a Shelly switch behind the conventional light switch…

I am very new to HA, and just bought the motion sensor and raspberry PI last week.

What I want to have set up:
A) When someone manually switches on the switch Light → activate the light, for 10 minutes (for ventilation purposes, and because my kids keep forgetting to switch the light off)
B) Parrallel to A, the light also has to be switched on through the motion detector, without having to use the switch, also starting the timer for 10’.
C) In combination with A & B, the timer has to be reset if the motion detector detects motion during one of the 10’ runs.This is particularly handy when someone enters the toilet with the light on but with the timer at the end of its run, to avoid getting in the dark.

A & B I have managed to program with to automations as seen below. Where triggering B, also triggers A and sets the timer. But C I am struggling to integrate. I have installed eEntity controller via HACS but my YAML knowledge is not yet enough to programm this?
Any thoughts on how to code? Or does anyone has a tip for an extensive visual editor which can help me with more difficult automations?

Much appreciated in advance!

Automatisation A=

alias: toilet_switch_off_10minutes
description: ""
trigger:
  - platform: state
    entity_id:
      - switch.shelly1_40f520016bda
    to: "on"
    for:
      hours: 0
      minutes: 10
      seconds: 25
condition: []
action:
  - service: switch.turn_off
    data: {}
    entity_id: switch.shelly1_40f520016bda
mode: single

Automatisation B=

alias: Toilet light on through motion
description: ""
trigger:
  - type: motion
    platform: device
    device_id: 6827037dad6dd6817cc889a4d5d8e59a
    entity_id: c9243c6ce23330f53b6239500f96d844
    domain: binary_sensor
    for:
      hours: 0
      minutes: 0
      seconds: 0
condition: []
action:
  - service: switch.turn_on
    data: {}
    target:
      device_id: 82477961aeda7b644a171ad88ef24470
mode: single

thusassistint · September 10, 2023, 9:31am

One approach could be to create one automation with both A and B as trigger (it then responds to A or B), and switching the switch on for 10 minutes as action (switch on → wait for 10 minutes → switch off).
When you then set the automation mode to restart (instead of single) you also tackle C.

Personally I never used this, but Node-RED might be what you are looking for.

Korenwolf · September 10, 2023, 9:44am

node-red is how I approached the problem. My use case is slightly different, I wanted motion triggered lighting but a way to “lock on” the light if needed, using countdown-3000 (this allows for resetting the counter) I’ve got the motion state wired into the counter to start / reset as needed and set a “triggered by motion” flag (helper). However it’ll only set that if the light is off.

Motion clear will start the timer to turn off, but only actually fire if the motion flag is true.

There’s a separate but linked flow which triggers on light off, starts a 10 second timer, clears the motion flag, this gives me 10 seconds grace to turn off and turn on the light, which blocks the motion flow as the light is already on.

Put another way, go play with node-red, use helpers / injection nodes as placeholders for the motion sensor & switch to get the logic right before rolling out.

Korenwolf · September 10, 2023, 9:55am

For what it’s worth, my automation, the “meta” is a fake motion sensor which is based off two door sensors and one motion, presented as a single element which is clear only if all three are clear.

Stiltjack · September 10, 2023, 11:13am

Have a look at Entity Controller from HACS - it will do what you want in half a dozen lines. Here’s mine:

  - bathroom_light:                               
      sensor: 
      - binary_sensor.bathroom_motion_sensor_motion  
      entities: 
      - light.bathroom_1
      delay: 600
      block_timeout: 600

If the motion sensor detects movement, the light comes on for ten minutes. (If movement is detected in that time the period is extended for another ten minutes.) If the light is turned on or off manually it stays in that state for ten minutes, then goes off if there is no movement.

PS… Avoid device triggers if you can…

pidewo481 · September 10, 2023, 6:53pm

I downloaded entity controller indeed a couple of days ago, but I haven’t ‘grasped’ how to write and where to put the code.

I copied this code (based on yours) in my configuration.yaml, but it doens’t seem to work

wclicht

bathroom_light:
sensor:
- binary_sensor.lumi_lumi_motion_ac02_motion
entities:
- switch.shelly1_40f520016bda
- to: “on”
delay: 600
block_timeout: 600

Stiltjack · September 10, 2023, 7:06pm

Sorry, my fault - it should begin with entity_controller:

entity_controller:
  - bathroom_light:                               
      sensor: 
      - binary_sensor.bathroom_motion_sensor_motion  
      entities: 
      - light.bathroom_1
      delay: 600
      block_timeout: 600

You only need entity_controller once in your configuration.yaml, followed by all the lights, indented as above. Then do a restart.

Incidentally, when you paste yaml into a post, you need to use preformatted text (</> in the toolbar). This preserves the indentations, which are quite important.

pidewo481 · September 10, 2023, 7:33pm

thx,

This did the thrick

alias: Nieuwe automatisering
description: ""
trigger:
  - platform: state
    entity_id:
      - switch.shelly1_40f520016bda
    to: "on"
  - platform: state
    entity_id:
      - binary_sensor.lumi_lumi_motion_ac02_motion
    to: "on"
condition: []
action:
  - service: switch.turn_on
    data: {}
    target:
      entity_id: switch.shelly1_40f520016bda
  - delay:
      hours: 0
      minutes: 10
      seconds: 0
      milliseconds: 0
  - service: switch.turn_off
    data: {}
    target:
      entity_id: switch.shelly1_40f520016bda
mode: restart

thusassistint · September 10, 2023, 9:20pm

Hmm… are you sure it is working OK like this?
You are using the same entity switch.shelly1_40f520016bda both as a trigger and in the action to turn the light on and off. That can’t be right?

This is a Shelly 1, right?
I also have Shelly 1 devices to control lights, but these have separate entities to be used for the trigger and for the action.
For instance for my Shelly 1 SH02 I have a binary_sensor.sh02_input entity that can be used as trigger (which is the physical wall switch), and a light.sh02 entity (which is the relay that controls the light).
Your switch.shelly1_... entity probably is the relay, but don’t you have a binary_sensor_shelly1... as well, to be used as trigger?