WTH Why Please fix these old Bluetooth errors

Bluetooth has been unusable for me since I started with HA back in late 2022.
Here is the main offender :wink:

92379 - bluetooth integration constant state of initializing / retrying setup (bluetooth is broken with some adapters on newer linux kernels, kernel must be manually patched, workaround is to switch to ESPHome proxies instead) · Issue #92379 · home-assistant/core · GitHub

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

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”? :wink:

I have no idea, but you’re acting like this is HA’s fault when HA is waiting on another software.

2 Likes

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”?

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

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.

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.

:man_shrugging: