HomeKit Device (HomeKit Controller) devices lose their automation triggers

[briangunderson]

The problem

Every month or two, automations triggered by various HomeKit Device keypads lose their triggers. This happens to automations referenced by devices from different brands and models, including Leviton D2SCS and ONVIS HS2)

What version of Home Assistant Core has the issue?

core-2024.4.0b6

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

HomeKit Device

Link to integration documentation on our website

https://rc.home-assistant.io/integrations/homekit_controller

Diagnostics information

homekit_controller-27ae728df77dccb56fb2bd270b102057-LEVDS-ScnCtl-CBAC-251eaa31a14b7bce163cd5c563d64949.json

Example YAML snippet

alias: Basement Remote Buttons
description: ""
trigger:
  - platform: device
    device_id: 251eaa31a14b7bce163cd5c563d64949
    domain: homekit_controller
    type: button1
    subtype: single_press
    id: "1"
  - platform: device
    device_id: 251eaa31a14b7bce163cd5c563d64949
    domain: homekit_controller
    type: button2
    subtype: single_press
    id: "2"
  - platform: device
    device_id: 251eaa31a14b7bce163cd5c563d64949
    domain: homekit_controller
    type: button3
    subtype: single_press
    id: "4"
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - "1"
        sequence:
          - service: scene.turn_on
            target:
              entity_id: scene.basement_workday
            metadata: {}
      - conditions:
          - condition: trigger
            id:
              - "2"
        sequence:
          - service: scene.turn_on
            target:
              entity_id: scene.basement_evening
            metadata: {}
      - conditions:
          - condition: trigger
            id:
              - "3"
        sequence:
          - service: scene.turn_on
            target:
              entity_id: scene.downstairs_on
            metadata: {}
      - conditions:
          - condition: trigger
            id:
              - "4"
        sequence:
          - service: scene.turn_on
            target:
              entity_id: scene.downstairs_off
            metadata: {}
mode: single

Anything in the logs that might be useful for us?

No response

Additional information

Whenever this happens, the automations attached to the HomeKit Device get borked up, showing "Unknown Trigger" in the trigger field in the GUI. See Screenshot, and see attached YAML version of config. YAML view of broken homekit device automation.txt

[home-assistant[bot]]

Hey there @jc2k, @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit_controller) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homekit_controller 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 homekit_controller 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)}}

---

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

[loadamasta]

I have the same problem. Event is reckoginized in HA, but automation is not startet. It has to be the fault of 2024.4 as before the automations run flawless.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[briangunderson]

Please do not auto-close this. It's still a problem.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[briangunderson]

Still having the problem. Happy to provide logs etc.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[briangunderson]

Still having the problem. Happy to provide logs etc.

[jcrvlh]

I have the same problem.

[srueberg]

Same here. It‘s still an open problem. (Interestingly, in my case, this doesn‘t happen to all of my three Onvis switches but only to two of them.)

[briangunderson]

My Leviton scene controllers stopped exhibiting the behavior once I temporarily allowed them to access the internet to download firmware updates. I’ll keep the issue open though since clearly there are others having issues. Might be worth checking your firmware versions. I didn’t attempt to determine what changed between versions.

On Tue, May 20, 2025 at 3:46 AM Sven @.***> wrote:

srueberg left a comment (home-assistant/core#114660) https://github.com/home-assistant/core/issues/114660#issuecomment-2893506970

Same here. It‘s still an open problem. (Interestingly, in my case, this doesn‘t happen to all of my three Onvis switches but only to two of them.)

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/114660#issuecomment-2893506970, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOO7SUP7KRD6E26N7ID7ZL27LTVNAVCNFSM6AAAAABFT26JV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOJTGUYDMOJXGA . You are receiving this because you authored the thread.Message ID: @.***>

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.