core icon indicating copy to clipboard operation
core copied to clipboard

Homekit Devices - Aqara: wall switch are become useless!

Open loadamasta opened this issue 2 years ago • 3 comments

The problem

Sionde the update to 2024.4 all Aqara switch events are no longer able to start automations: clicks are recognized by home assistant (on the device page the clicks are shown) but events do not start any automation. Event listender does not show any entry on that entities while listening. Worked flawless on 2024.3 before the update to 2024.4. Thus, something of the updates 2024.4 did kill something with the event listening in connection with home kit devices.

What version of Home Assistant Core has the issue?

core-2024.4.1

What was the last working version of Home Assistant Core?

2024.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Homekit device - Aqara hub

Link to integration documentation on our website

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

Diagnostics information

--

Example YAML snippet

alias: Weinkeller Schalter 1
description: ""
trigger:
  - platform: device
    device_id: 96632216c91b27f54ad416b2d8724d92
    domain: button
    entity_id: d5a963a38232ebbb711157312346dfe2
    type: pressed
condition: []
action:
  - service: switch.toggle
    data: {}
    target:
      entity_id: switch.shellyplus2pm_5443b23eadd8_switch_1
mode: single

Anything in the logs that might be useful for us?

--

Additional information

--

loadamasta avatar Apr 14 '24 16:04 loadamasta

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)

home-assistant[bot] avatar Apr 14 '24 16:04 home-assistant[bot]

I have a similar problem with the Aqara button. When I press the button I see the click in the device page, but my automation stopped working. I was able to fix it by switching from:

trigger:
  - platform: device
    device_id: 98ebf8209fb7543ca82b957c3d694f6c
    domain: homekit_controller
    type: button1
    subtype: single_press
condition: []

To:

trigger:
  - platform: state
    entity_id:
      - event.entrance_entrance_button_2
condition:
  - condition: template
    value_template: "{{ trigger.to_state.attributes.event_type == 'single_press' }}"

liorfranko avatar Jun 23 '24 18:06 liorfranko

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.