-
-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
Bluetooth enabled, causes constant writing to disk from bluetoothd process #76540
Comments
bluetooth documentation |
Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration ( |
Can you get an |
strace.log |
It looks like its writing the cache over and over again
Seems like a bug in bluetoothd I'd suggest opening an issue with bluez |
ok I will get onto the newest bluez first since I am running several version behind... Then I will re test and see if it continues... |
fatrace -t -f W
|
Please open an issue with bluez. There isn’t anything Home Assistant can do about the system Bluetooth stack. |
Please read the documentation |
Bluez 5.65, enable 'experimental'
Home Assistant 2022.11.1
When "active scanning" is disabled, "BTHome" does not work, but "Qingping" and "Xiaomi BLE" work successfully. |
The problem
After upgrading to 2002.8.2 and enabling bluetooth I started seeing constant disk writes from /usr/libexec/bluetooth/bluetoothd I disable bluetooth module and the disk writes stop. With bluetooth enabled I then disabled the Govee devices and the disk write still were occurring.
I am not seeing this issue with Bluetooth Low Energy Monitor.
What version of Home Assistant Core has the issue?
2022.8.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
No response
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
The text was updated successfully, but these errors were encountered: