search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.14k stars 29.82k forks source link

[XIAOMI BLE] YLYK01YL BT Remote does not trigger every button press - "M" Button not working in automation #114081

Closed elbman closed 2 months ago

elbman commented 5 months ago

The problem

I am very happy that the remote control YLYK01YL is finally supported by the Xioami BLE integration. Unfortunately, the events are not reliably recognized. I would say that on average only 7 out of 10 actions are recognized. I use Bluetooth Proxy with Shelly devices throughout the house. It's not a range problem, the remote control sends reliably.
An ESP32C3 in the same room with Tasmota BLE recognizes every keystroke, HA not! Alternatively, I also tested an M5Stack AtomLite with ESPHome BTProxy, unfortunately no improvement. A direct BT dongle connection for testing is not possible on my HyperV HA instance.

After researching, I came across a similar problem with BTHome in connection with the Shelly BLu button, which was apparently solved by an update last year. https://github.com/home-assistant/core/issues/93502

Could it be that there is a similar problem in XIAOMI BLE Integration?

I testet with all button, long & short, same behavior

in addition i noticed "M" Button does not work for automations, nothing happens.

What version of Home Assistant Core has the issue?

2024.3.3

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

XIAOMI BLE

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 5 months ago

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

Code owner commands Code owners of `xiaomi_ble` 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 xiaomi_ble` 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)

xiaomi_ble documentation xiaomi_ble source (message by IssueLinks)

issue-triage-workflows[bot] commented 2 months ago

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.