core: Bluetooth LE Tracker no longer scanning or doing anything
The problem
Bluetooth LE Tracker no longer scans or appears to be operational.
This was working in versions prior to 2022.8 but now there is nothing, no log entry, no update to entities. Documentation and release notes state nothing about any changed config parameters.
What version of Home Assistant Core has the issue?
2022.8.2
What was the last working version of Home Assistant Core?
2022.6.x
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Bluetooth LE Tacker
Link to integration documentation on our website
https://www.home-assistant.io/integrations/bluetooth_le_tracker/
Diagnostics information
No response
Example YAML snippet
- platform: bluetooth_le_tracker
track_new_devices: false
interval_seconds: 30
Anything in the logs that might be useful for us?
No log output at all, nothing even to say it is performing a scan as normal
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 37 (11 by maintainers)
Commits related to this issue
- Switch to bluetooth_le since bluetooth is broken But LE is also broken: https://github.com/home-assistant/core/issues/76634 — committed to PW999/home-assistant-config by PW999 2 years ago
- Bump bleak to 0.16.0 Fixes #76634 — committed to bdraco/home-assistant by bdraco 2 years ago
Good news.
There is a PR open to resolve the issue in bleak https://github.com/hbldh/bleak/pull/967#pullrequestreview-1089529970
It should be released in the next version of bleak
Once its released all we need to do it update the version in Home Assistant and do a new release
Buhito81, I have the exact same issue. If a tag is “away” at reboot of HA, the entity shows as away. As soon as the tag is “in range” it is detected and shows as home.
However, once a tag is identified as home (be it at startup or sometime thereafter) the entity never gets updated to “away.”
Any solutions?
https://github.com/custom-components/ble_monitor is what I use and what works perfectly with full device/mac/etc configuration from ui as I imagined native HA integration would, but it doesn’t. Just spent 2 hours trying to convert device tracker from the custom integration to native ha bluetooth_le without any luck.
I do appreciate all the work ha team is doing on the BT integrations into ha recently, however as a layman end user I have to say the way you release it bit by bit in half broken non working state is very confusing to me. Everything I try to convert to the new native ha bluetooth integration is a massive undertaking and effort and doesn’t work for half my devices still anyway and when I search for the issue the usual answer is oh it’s broken we have to wait for this or that or it’s not released yet.
Again, I do appreciate the work, I’m just saying this as a layman end user not understanding the programming effort involved underneath.
It means we have to wait for the bleak issue to be fixed before we can move forward any fix. The workaround won’t work.
Regardless of the work needed to fix some of the underlying issues, and update to be config entry / UI based, the reason the devices never go not home is documented here: https://github.com/hbldh/bleak/issues/942
Whilst I appreciate the work that goes into this and work you’ve personally done. Still unsure why a feature improvement has been given the go ahead to the detriment of another? Surely an integration shouldn’t be moved forward until all the integrations it impacts have been resolved, or its deemed the other integrations will be dropped due to not being upgradeable?
I wouldn’t exactly say Bluetooth lte integration is working, it just doesn’t completely error, or die out, but it definitely doesn’t do what it’s supposed to.
Is there a time line as to when this integration will be fixed? Would be great if it was hotfix this month now it’s been noted as a legit issue, but understand if it folds over into next month.
Since you yourself reply here: thanks for all the work you’ve (and others have) done on Bluetooth
This integration needs to be overhauled and converted to use the new device tracker config entry based platform instead of the legacy one. That will likely resolve the issues here
https://github.com/home-assistant/home-assistant.io/pull/23734