création d'un va et vient dans homeassistant entre 2 interrupteurs intégration avec Blueprint

2-way-ha.yaml

blueprint:
  name: 2 way simulate
  description: Bind two switches together to act in unison 
  domain: automation
  input:
    switch_1:
      name: Switch 1
      selector:
        entity:
          domain: switch
    switch_2:
      name: Switch 2
      selector:
        entity:
          domain: switch

variables:
  switch_1: !input switch_1
  switch_2: !input switch_2

trigger:
  - platform: state
    entity_id: 
      - !input switch_1
      - !input switch_2

mode: single

condition:
  '{{ trigger.to_state.state != trigger.from_state.state }}'

action:
  # Set to target value
  - choose:
    - conditions:
      - '{{ trigger.entity_id != switch_1 }}'
      - '{{ trigger.to_state.state != states(switch_1) }}'
      sequence:
        - service: 'switch.turn_{{ trigger.to_state.state }}'
          entity_id: !input switch_1

  - choose:
    - conditions:
      - '{{ trigger.entity_id != switch_2 }}'
      - '{{ trigger.to_state.state != states(switch_2) }}'
      sequence:
        - service: 'switch.turn_{{ trigger.to_state.state }}'
          entity_id: !input switch_2

I would add something like :

trigger:

• platform: state
  not_to:
  • unavailable
  • unknown
    As from latest HA update the message related with:

The automation "David Bedroom light 2 way" (automation.david_bedroom_light_2_way) has an action that calls an unknown service: switch.turn_unavailable.

came out at every Z2M restart.

Your automation calls the service: homeassistant.turn_unavailable which does not exist.

"unavailable" is a valid state for any entity (so is unknown"). The way you wrote service template in your automation, allows for calling:

homeassistant.turn_unavailable
homeassistant.turn_unknown
You need to make sure the "to_state" is either "on" or "off" to ensure you are not calling a non-existing service (and thus you automation will fail running).