expose an esp32 running esphome as a bluetooth proxy for home assistant's bluetooth integration

domain: esphome.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Add the esp32_ble_tracker component to the device's YAML, since bluetooth_proxy depends on it.
  2. Add a bluetooth_proxy: block to the configuration; active: true (default) enables proxying active GATT connections in addition to passive scanning.
  3. Optionally tune connection_slots (each slot uses ~1KB RAM, max 9, but more than ~5 risks stability/memory issues) based on how many simultaneous BLE connections you need proxied.
  4. Leave cache_services: true (default) so GATT service discovery results are cached in NVS flash, speeding up repeat connections.
  5. Flash the device and confirm it appears as a Bluetooth proxy source under Home Assistant's Bluetooth integration.

Known gotchas

Related routes

provision an esphome device's wifi credentials over ble or serial using the improv standard
esphome.io · 5 steps · unrated
Configure ESPHome with native API and integrate a custom sensor device with Home Assistant using device substitutions and packages
esphome.io · 6 steps · unrated
Enable Noise-protocol encryption on an ESPHome device's native API connection and pair it with Home Assistant
esphome.io · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans