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
72.06k stars 30.18k forks source link

RPi4 Bluetooth Adapter passive scan captures only one event every 2 minutes #121207

Open MacrosorcH opened 3 months ago

MacrosorcH commented 3 months ago

The problem

Until HA 2024.6.4, I have been successfully using the RPi4 Bluetooth Adapter with the Bluetooth integration and passive scan enabled to act as proxy for a Shelly BLU Button integrated via BTHome.

Since 2024.7.0, the RPi4 Bluetooth Adapter is only capturing one event every 2 minutes. Basically, I click the button and the related event is correctly captured and reported in HA, but, after that, the system is blind for 2 minutes and any other button press within those 2 minutes is lost. After 2 minutes, a new button press is again correctly captured, but then it causes another 2 minutes of complete blindness, and so on... In a nutshell, it can manage only one event every 2 minutes.

Note that, by using another Bluetooth proxy like another Shelly device in BLE proxy mode, the Shelly BLU Button works perfectly and no events are lost.

What version of Home Assistant Core has the issue?

core-2024.7.0

What was the last working version of Home Assistant Core?

core-2024.6.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Bluetooth

Link to integration documentation on our website

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

Diagnostics information

config_entry-bluetooth-0a3f3482427f0030745db6fa67955521.json

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 3 months ago

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

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


bluetooth documentation bluetooth source (message by IssueLinks)

bdraco commented 3 months ago

Sounds like a hardware or driver issue. Try powering down the device, leaving it off for 2 minutes, and powering it back on

MacrosorcH commented 3 months ago

@bdraco I have just tried as you suggested but it didn't help. Happy to test any other suggestion you might have.

bdraco commented 3 months ago

Sorry, I don't have any other suggestions. The code code to scan relies on dbus and bluez working as expected and that doesn't seem to be the case for you which means its an OS level problem

issue-triage-workflows[bot] commented 2 days 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.