Problem with automation between KNX and light.turn_on

Configuration
,
1

Hello,

i have the following problem.

I have an automation to turn on a Shelly switch from KNX

For example:

in configuration.yaml:

binary_sensor:
    - name: "knx_beleuchtung_test_schalten"
      state_address: "0/1/1"

This is my Trigger for automation

Here the automation for switching on and off.

 alias: Sophie_Bett_WLED_schalten_AN
  description: ''
  triggers:
  - entity_id:
    - binary_sensor.knx_beleuchtung_test_schalten
    to:
    - 'on'
    trigger: state
  conditions: []
  actions:
  - data: {}
    action: light.turn_on
    target:
      entity_id: light.sophie_wled_sophie
  mode: single
- id: '1786544827265'
  alias: Sophie_Bett_WLED_schalten_AUS
  description: ''
  triggers:
  - entity_id:
    - binary_sensor.knx_beleuchtung_test_schalten
    to:
    - 'off'
    trigger: state
  conditions: []
  actions:
  - action: light.turn_off
    target:
      entity_id:
      - light.sophie_wled_sophie
    data: {}
  mode: single.

Works so far.

But my problem is that this automation doesn’t run reliably.

As long as I control everything solely via KNX, it works well; however, whenever I control it via Home Assistant or directly through the Shelly app, the On/Off command no longer works reliably.

The problem is, for example:

If I switch it on via KNX and then switch it off in the Shelly app, I cannot immediately send another “on” command via KNX—it simply doesn’t work. I first have to switch it off via KNX before I can switch it on via KNX again.

I think it’s because of that.

- binary_sensor.knx_beleuchtung_test_schalten
    **to:**
    - 'on'

When I control it via Home Assistant or the Shelly app, the value of the entity “knx_beleuchtung_test_schalten” does not change, and unfortunately, the command only works when that value changes.

Is there a way to work around this—or to ensure the command always executes whenever the entity “knx_beleuchtung_test_schalten” sends a value of “1”?

I would be grateful for any help.

.

2

Hi :waving_hand:!
You’d need to send state updates back to Knx so the switch knows to send an ON or OFF when you tap it. That’s a common Knx practice mostly done via a separate status group address.

If you use the knx.telegram trigger, you can remove the binary sensor.

There are some blueprints that do all of that for you Topics tagged knx