BT Proxy tied up cant scan for devices

rykm48 · February 19, 2026, 4:06pm

I have two devices, an EP1 Lite with BT proxy enabled and an esp32 chip flashed for BT Proxy. Often all of my bt devices will go to unavailable.

sometimes my bt devices work for a bit and other times not. im not sure whats killing it. LLMs would suggest my nvidia sheild is hogging all the connections and keeping both devices from being able to do discovery but im not sure. I cant disable bt on the shield.

anyone have any ideas whats going on?

Here are screenshots of my bt in ha settings:

EBME2 · February 19, 2026, 10:31pm

I had similar apparently a bug see below with a fix for 2026.1.5 and a few earlier versions. The fix is to add the following to your config though it may be in today’s release of ESPHome but couldn’t find anything in release notes.

esp32:
  framework:
    type: esp-idf
    version: 5.5.2
    release: "260206"

github.com/esphome/esphome

[esp32] Bump ESP-IDF 5.5.2 to release 260206

dev ← bump_espidf_5.5.2_release

opened 01:13PM - 09 Feb 26 UTC

bdraco

+30 -12

# What does this implement/fix? Bumps the default ESP-IDF 5.5.2 framework from …the base `v5.5.2` release (Dec 27) to `v5.5.2.260206` (Feb 8), which includes an updated BT controller binary (`libbtdm_app.a`) that fixes a BLE scanning regression. The base `v5.5.2` contains a broken Bluetooth controller blob that causes BLE scanning to silently die after hours/days of uptime with: ``` BT_HCI: command_timed_out hci layer timeout waiting for response to a command. opcode: 0x200c ``` After this HCI timeout, the BLE controller is dead and only a full device reboot recovers it. This affects all ESP32 Bluetooth proxy users. The `v5.5.2.260206` release from pioarduino includes the upstream fix from `espressif/esp32-bt-lib` commit `06dc4667`: - fix(ble): Fixed BLE enable scan timeout - fix(ble): fixed crash in "btdm_controller_task" Verified by extracting and comparing `libbtdm_app.a` from both tarballs: - Base `v5.5.2`: SHA-256 `dd94003c...` (859,932 bytes) - `v5.5.2.260206`: SHA-256 `c37d869b...` (866,966 bytes) Upstream references: - https://github.com/espressif/esp-idf/issues/18217 - https://github.com/espressif/esp-idf/commit/9b0f6330e8775414892a9c9d49d18ae5fad098bb ## Types of changes - [x] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Developer breaking change (an API change that could break external components) - [ ] Code quality improvements to existing code or addition of tests - [ ] Other **Related issue or feature (if applicable):** - fixes https://github.com/esphome/esphome/issues/13560 **Pull request in [esphome-docs](https://github.com/esphome/esphome-docs) with documentation (if applicable):** - N/A ## Test Environment - [x] ESP32 - [x] ESP32 IDF - [ ] ESP8266 - [ ] RP2040 - [ ] BK72xx - [ ] RTL87xx - [ ] LN882x - [ ] nRF52840 ## Example entry for `config.yaml`: ```yaml # No config changes needed - the default now uses the fixed release. # Users can also explicitly test before this PR merges with: esp32: framework: type: esp-idf version: 5.5.2 release: "260206" ``` ## Checklist: - [x] The code change is tested and works locally. - [ ] Tests have been added to verify that the new code works (under `tests/` folder). If user exposed functionality or configuration variables are added/changed: - [ ] Documentation added/updated in [esphome-docs](https://github.com/esphome/esphome-docs).