Dragnet
(Hans)
December 5, 2024, 11:31am
1
Bluetooth has been unusable for me since I started with HA back in late 2022.
Here is the main offender
petro
(Petro)
December 5, 2024, 12:19pm
2
If you look at that issue, we are waiting on kernal updates for linux. I.e. It’s out of HA’s control.
2 Likes
Dragnet
(Hans)
December 6, 2024, 11:42am
3
Fair enough but for how long have we been waiting now?
I started with HA in the late summer of 2023. Back then I got lots of errors for Bluetooth so I just disabled it (I had no BT devices then). Then in the beginning of 2024 I bought some nice outdoor sensors with BT. Thinking that the early issues were fixed long ago I re-enabled the BT integration and promptly got the same/similar errors.
Should there be a list with “outstanding gremlins that are hard to fix and our hands are tied”?
petro
(Petro)
December 6, 2024, 11:43am
4
I have no idea, but you’re acting like this is HA’s fault when HA is waiting on another software.
2 Likes
Dragnet
(Hans)
December 8, 2024, 10:48am
5
No, I am not. But it would be prudent to mention this in one of the “glowing” status letters and not just focus on the positives.
Or put another way, I should refrain from mentioning here at “WTH”?
And I ask again: ‘Should there be a list with “outstanding gremlins that are hard to fix and our hands are tied”? ’
petro
(Petro)
December 9, 2024, 6:04pm
6
What’s the point when we can’t do anything about it other than wait. You’re basically just wasting your own time, and now mine
1 Like
Dragnet
(Hans)
December 10, 2024, 10:09am
7
One could communicate that you are waiting for another party. Instead it is here that this information is disseminated and in a somewhat blunt fashion.
Yes, I will stop using the WTH initiative. Sounded like a good idea at first. Sorry for the time wasted.
petro
(Petro)
December 10, 2024, 11:59am
8
It was communicated… in the PR you linked. That’s where I got the information from. I just read the comments that you seemingly did not read. I was investigating why this would be a WTH and I found the post from the developer in your posted issue. You don’t even need to load comments in order to see it. It’s the last loaded comment before github truncates things, so it’s very easy to see.
opened 10:55PM - 02 May 23 UTC
waiting-for-upstream
integration: bluetooth
# Mod Issue Summary - Read First
See https://lore.kernel.org/linux-bluetooth/… [email protected] /T/#mb094e06d495879436ce9a8722ad7ad87527ea74b
A summary:
- Bluetooth initialization is unreliable/broken on newer linux kernels for a large sample of adapters
- No fixes are available without patching the kernel and it will likely be a LONG time before debian updates the kernel, if you want to manually compile and patch your kernel, see https://lore.kernel.org/linux-bluetooth/CABBYNZ+5RMqNVMyYKi+gOVaV+K6k8Z-C37KnfGa=qRUORc3dWg@mail.gmail.com/ https://github.com/home-assistant/operating-system/pull/2714
- Newer Home Assistant OS has some patches that solves the problem for some adapters so be sure you have the latest HAOS: https://github.com/home-assistant/operating-system/issues/2485 https://github.com/home-assistant/operating-system/issues/2535
**- The recommended workaround if you can't run HAOS or patch the kernel manually is to use an ESPHome proxy instead https://esphome.github.io/bluetooth-proxies/**
---
### The problem
Bluetooth integration in perpetual state of initializing / retrying setup.
Deleting integration, restarting HA and configuring after auto discovered, several times, does not resolve.
### What version of Home Assistant Core has the issue?
core-2023.4.6
### 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
bluetooth
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/bluetooth
### Diagnostics information
[home-assistant_bluetooth_2023-05-02T22-28-03.303Z.log](https://github.com/home-assistant/core/files/11378180/home-assistant_bluetooth_2023-05-02T22-28-03.303Z.log)
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
```txt
Retrying setup: hci0 (XXXXX): Failed to start Bluetooth: [org.bluez.Error.InProgress] Operation already in progress
Logger: bluetooth_auto_recovery.recover
Source: components/bluetooth/util.py:78
First occurred: 5:36:41 PM (28 occurrences)
Last logged: 5:52:42 PM
Bluetooth adapter hci0 [XXXXXXXX] could not be reset due to timeout
Logger: homeassistant.config_entries
Source: config_entries.py:1242
First occurred: 5:44:58 PM (4 occurrences)
Last logged: 5:51:51 PM
Config entry 'XXXXX' for bluetooth integration not ready yet: hci0 (XXXXX): Failed to start Bluetooth: [org.bluez.Error.InProgress] Operation already in progress; Retrying in background
```
### Additional information
Home Assistant Yellow
## System Information
version | core-2023.4.6
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.10.10
os_name | Linux
os_version | 6.1.21-v8
arch | aarch64
timezone | America/Chicago
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4929
Installed Version | 1.32.1
Stage | running
Available Repositories | 1278
Downloaded Repositories | 10
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | true
-- | --
subscription_expiration | May 3, 2023 at 7:00 PM
relayer_connected | true
relayer_region | us-east-1
remote_enabled | true
remote_connected | true
alexa_enabled | false
google_enabled | false
remote_server | us-east-1-7.ui.nabu.casa
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 10.1
-- | --
update_channel | stable
supervisor_version | supervisor-2023.04.1
agent_version | 1.5.1
docker_version | 23.0.3
disk_total | 234.0 GB
disk_used | 9.6 GB
healthy | true
supported | true
board | yellow
supervisor_api | ok
version_api | ok
installed_addons | Mosquitto broker (6.2.1), Studio Code Server (5.5.7), Terminal & SSH (9.7.0), Network UPS Tools (0.11.2)
</details>
<details><summary>Dashboards</summary>
dashboards | 3
-- | --
resources | 6
views | 6
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | April 24, 2023 at 3:54 AM
-- | --
current_recorder_run | May 2, 2023 at 5:36 PM
estimated_db_size | 652.32 MiB
database_engine | sqlite
database_version | 3.38.5
</details>