Why does an Automation perform Actions regardless of the condition?

@GoedGeluk wrote:

Hi,

In my configuration I created several Input_Boolean variables that I can turn on or off. Up till release 105 I could use them as conditions in my automations like:

- id: '0020200325004'
  alias: Mi 2 Motion
  trigger:
  - entity_id: binary_sensor.motion_sensor_158d0001e44955
    platform: state
    to: 'on'
  condition:
    condition: state
    entity_id: input_boolean.sendmimot2
    state: 'on'
  action:
  - data: {}
    entity_id: script.mi2_motion_delay
    service: script.turn_off
  - data:
      message: Motion Detected by Mi somewhere
      title: '*Motion Warning*'
    service: notify.tg_sendwarning
  - data: {}
    entity_id: script.mi2_motion_delay
    service: script.turn_on
  initial_state: true

Since I upgraded to release 107 the Actions in this automation are triggered always regardless of the state of the input_boolean used in the Condition.

Did I miss some breaking changes in the Release notes?

Any help would be appreciated.

Regards,

Marcel

Posts: 5

Participants: 3

Read full topic