Automation stopps triggering after addition of condition

I have automation created to perform the following:

  • Trigger on motion detection
  • Check if the state of Boolean switch is false then turn on lights (I have created a boolean switch)

I have experienced that after adding condition automation stops triggering after removal of condition automation works flawlessly

Anybody having similar issue?

alias: Living room - Turn off lights on no motion
description: ''
trigger:
  - device_id: 984226a30fb543f4960b51dd76f6e2b0
    domain: binary_sensor
    entity_id: binary_sensor.living_room_sensor_motion
    for:
      hours: 0
      minutes: 3
      seconds: 0
    platform: device
    type: no_motion
condition:
  - condition: state
    entity_id: input_boolean.living_room_master_override
    state: 'off'
    attribute: friendly_name
action:
  - type: turn_off
    device_id: 40ff4edfc28c4dc8aa7f1e7473b066d4
    entity_id: light.living_room_ceiling
    domain: light
mode: single

I don’t understand why you use the choose here, when all the choices execute the same action?

Also I don’t see your boolean anywhere in the autonation?

That was quick edit copy to show problem. anyway i have updated thread with condition.

Remove the line attribute: friendly_name from the condition.