KNX Device trigger - Telegram sent or received not working after reload of knx integration or restart

[DarkWarden85]

The problem

Hi,
I noticed since a few weeks that automations using the KNX Device trigger with the option "Telegram sent or received" do not trigger anymore. The only fix is to disable and then re-enable the affected automation. This always happens after a manual reload of the knx integration.
Oftentimes the automation in question even shows that it was triggered, but the actions are never executed and it doesn't show any trace for that moment.
Below is an example of an automation that never triggers:

alias: >-
  Jalousie Wohnzimmer - Sonnenschutzautomatik deaktivieren bei manueller
  Steuerung
description: ""
trigger:
  - platform: device
    domain: knx
    device_id: 70488ff10d01ac0ba236b7056cdf6acf
    type: telegram
    destination:
      - 2/0/0
      - 2/0/1
      - 2/0/18
      - 2/0/19
      - 0/2/0
      - 0/2/1
condition:
  - condition: state
    entity_id: switch.sonnenschutz_automatik_jalousie_wohnzimmer
    state: "on"
action:
  - service: switch.turn_off
    target:
      entity_id: switch.sonnenschutz_automatik_jalousie_wohnzimmer
    data: {}
mode: single

What version of Home Assistant Core has the issue?

2023.12.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

KNX

Link to integration documentation on our website

https://www.home-assistant.io/integrations/knx/

Diagnostics information

No response

Example YAML snippet

alias: >-
  Jalousie Wohnzimmer - Sonnenschutzautomatik deaktivieren bei manueller
  Steuerung
description: ""
trigger:
  - platform: device
    domain: knx
    device_id: 70488ff10d01ac0ba236b7056cdf6acf
    type: telegram
    destination:
      - 2/0/0
      - 2/0/1
      - 2/0/18
      - 2/0/19
      - 0/2/0
      - 0/2/1
condition:
  - condition: state
    entity_id: switch.sonnenschutz_automatik_jalousie_wohnzimmer
    state: "on"
action:
  - service: switch.turn_off
    target:
      entity_id: switch.sonnenschutz_automatik_jalousie_wohnzimmer
    data: {}
mode: single

Anything in the logs that might be useful for us?

There is no error in the logs of any kind

Additional information

No response

[home-assistant]

Hey there @Julius2342, @farmio, @marvin-w, mind taking a look at this issue as it has been labeled with an integration (knx) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of knx can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign knx Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

knx documentation
knx source
_{^{(message by IssueLinks)}}

[farmio]

Hi 👋!
I'll try to recreate this. Until now, reloads always worked fine for device triggers.

Oftentimes the automation in question even shows that it was triggered, but the actions are never executed and it doesn't show any trace for that moment.

Oftentimes, or always?
Is the entity in the condition also a Knx entity?

[DarkWarden85]

Oftentimes, I also had the case were the device triggers did not indicate that they were triggered.
The entity in the condition is also a knx entity:

knx:
  switch:
    - name: "Jalousie Wohnzimmer Automatik Sonnenschutz"
      address: "2/0/5"

[farmio]

Found the issue. Thank you for reporting this bug! 👍

[DarkWarden85]

@farmio Thank you for your support and making this great integration possible in the first place :).