Motion detection on/off mistake

[pepe2 (Pepe)]

Hi I made an automation with a motion detection that put the lights on or off.
It works but now and then the light goes on and immediate goes off again.
So it is like the automation is doing the 2 triggers after each other. => on =>off.

What did I wrong in my automation?

alias: Motion inkom licht aan/uit
description: ""
triggers:
  - trigger: state
    entity_id:
      - sensor.mw_inkom
    to: Detected
    id: inkom aan
  - trigger: state
    entity_id:
      - sensor.mw_inkom
    to: Clear
    id: inkom uit
    for:
      hours: 0
      minutes: 1
      seconds: 0
conditions: []
actions:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - inkom aan
          - condition: sun
            before: sunrise
            before_offset: "+02:00:00"
            after: sunset
            after_offset: "-01:00:00"
        sequence:
          - type: turn_on
            device_id: 4d9e1e905b3f2ca86c6aa19938ac38d6
            entity_id: da7729a830c90b7e7be8fc6ef04e3b62
            domain: switch
      - conditions:
          - condition: trigger
            id:
              - inkom uit
        sequence:
          - type: turn_off
            device_id: 4d9e1e905b3f2ca86c6aa19938ac38d6
            entity_id: da7729a830c90b7e7be8fc6ef04e3b62
            domain: switch
mode: single

[aceindy]

Motion activated lights automation

This gets asked a lot so here is an example for automating a light to come on with movement and go off after there is no movement for a short time. trigger: - platform: state entity_id: binary_sensor.your_motion_sensor_here # change this to: 'on' - platform: state entity_id: binary_sensor.your_motion_sensor_here # change this to: 'off' for: minutes: 2 # adjust as necessary action: - service: "light.turn_{{ trigger.to_state.state }}" target: entity_id: …

[pepe2 (Pepe)]

Thanks, I have a look

[pepe2 (Pepe)]

My detection returns Detected or Clear and not on/off, what do I have to change extra to let that to work?

alias: Motion inkom licht aan/uit
description: ""
triggers:
  - entity_id:
      - sensor.mw_inkom
    to: Detected
    trigger: state
  - entity_id:
      - sensor.mw_inkom
    to: Clear
    for:
      minutes: 1
    trigger: state
actions:
  - target:
      device_id: 4d9e1e905b3f2ca86c6aa19938ac38d6
      entity_id: da7729a830c90b7e7be8fc6ef04e3b62
    action: light.turn_{{ trigger.to_state.state }}
mode: single

[Edwin_D]

The approach in both methods is more or less the same, so that is not your problem. Rewriting it to use your states is possible but Id stick to your old approach. Have you looked at the automation traces and the log to see what caused the off?

I also would advise to steer clear of device actions/triggers/conditions. Stick to light.turn_on and …off with just entity ids.

[aceindy]

@pepe2

My detection returns Detected or Clear and not on/off,

Just FYI:
On the dashboard it will show detected and clear (as the sensor has class motion).
But under the hood (yaml), the motion sensor is ‘just’ another binary sensor
and will use on and off

So while the visual editor shows:

It’s yaml will show: