-
-
Notifications
You must be signed in to change notification settings - Fork 32.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unstable Bluetooth Adapter in Home-Assistant #93036
Comments
Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) bluetooth documentation |
I too have the same problem with the built in Bluetooth adapter on my Intel NUC (Beelink Mini PC). I am currently using only the „passive scanning“ option of the hci0 adapter integration. Logger: bluetooth_auto_recovery.recover |
I too have issues with the Bluetooth since a month or so. I am running HA docker. I used to use version 2022.11, now recently upgraded to 2023.5 to try to fix the issues, but alas. The issue, as far as I can see, is that HomeAssistant is constantly scanning for new devices, and overloading the BT dongle. I tested outside of the docker, if I pause the docker, then run
and it goes on and on and on. And from the start I start seeing this scan, then the external script that reads the Airthings Wave BLE device stops being able to read the metrics. In the HA logs, I found only this:
but it seems clear to me that something is wrong with the Bluetooth addon. We need to be able to stop it from scanning for devices and only scan manually. I tried disabling
in the system options, but that does not stop the scanning. |
Is there an progress regarding this issue? It seems there are no updates to get the bluetooth errors fixed. At the end on my side it influence all Bluetooth devices. Especially the Bluetooth Proxies are no longer reliable since weeks. Logger: homeassistant.components.bluetooth.scanner hci0 (C0:FB:F9:61:A9:68): Error stopping scanner: [org.bluez.Error.Failed] No discovery started |
Please follow the issue in the operating system repo |
Well thats happening with ubuntu with docker with ha-container. Not with HAOS in this case. So doing something like rolling back to HAOS 9.5 doesnt work for this. For reference for the others since it wasnt linked. home-assistant/operating-system#2535 |
The problem is with |
So for the time being for anyone else in here this is what I have done to fix it for the time being. Works fine for me. You can find your entry id in /.storage/core.config_entries
|
This fix did not fix my issue. I still have to unplug and reconnect USB Bluetooth dongle physically every couple of days. Is there a way to power cycle the USB port from Home Assistant? |
Is there an open issues for the proxies. I'm not aware of any unsolved problems with them |
Yeea I am getting this now:
|
I opened a PR to handle the case where the device is removed from the bus while we are waiting for a change hbldh/bleak#1329 |
fixes #93036 (comment) fixes #93222 (comment) fixes #93171 changelog: hbldh/bleak@v0.20.2...v0.21.0
The problem
So I have my Intel Nuc Bluetooth Adapter enabled to discover the values of my plant sensors. But the sacnner is always restarting for some reason some times resolving itself but also sometimes not so I have to press reload integration manually for it to work again.
What version of Home Assistant Core has the issue?
core-2023.5.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Bluetooth
Link to integration documentation on our website
https://www.home-assistant.io/integrations/bluetooth
Diagnostics information
config_entry-bluetooth-13ec0f89e00a8353c4df8e7ed7e10e7d.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: