ESPHome 2026.8.0: Bluetooth Presence Tracking, No Cloud

ESPHome bluetooth presence tracking without cloud just got much more affordable. Today’s release of ESPHome 2026.8.0 brings Bluetooth presence tracking to cheap, ubiquitous hardware — the $6 Raspberry Pi Pico W and the BK72xx chips inside many budget Tuya wall switches and plugs — not just pricier ESP32 boards. For homeowners, that means local, private presence automations: lights that turn on when you walk into a room, away mode when you leave, all without cloud subscriptions or proprietary hubs. The update also fixes a nagging Bluetooth issue for existing ESP32 users. The release follows six betas and bundles 348 pull requests from more than 40 contributors — a good sign for stability if you are upgrading a device you rely on, per the official ESPHome 2026.8.0 changelog. Here is what changed and what it means for your smart home.

How This Was Verified

This update summary is based on the official ESPHome 2026.8.0 changelog, the GitHub release notes, and vendor documentation. We did not test the new hardware hands-on — details come from the official changelog and announcement. All cited URLs were confirmed reachable on August 20, 2026. Last updated: August 2026.

How does ESPHome do Bluetooth presence tracking without the cloud?

ESPHome keeps presence tracking fully local: your own devices scan for nearby phones and beacons and report to Home Assistant over your network, with no cloud service involved. The new platform-neutral BLE layer in 2026.8.0 moves all 39 BLE sensor platforms off the ESP32-only foundation, per the official changelog.

You can now place tiny, cheap trackers around your home and trigger automations without sending data anywhere. That is the appeal of ESPHome: one free firmware that treats your own hardware as the hub, with nothing phoning home — a natural fit with our privacy-first Home Assistant build.

What changed in ESPHome 2026.8.0 for existing users?

Existing ESP32 users get a critical fix: the ESP-IDF 5.5.5 update resolves missed Bluetooth advertisements while WiFi was active, a bug present since 2026.7.1, per the official changelog. There is also one breaking change: the BLE sensor key esp32_ble_id: is renamed to ble_hub_id:.

The old key still works with a warning until 2027.2.0, and builds get faster with ccache and smaller toolchain installs — handy if you run proxies from our ESP32 Bluetooth Proxy for Home Assistant guide.

What can you build with a $6 Pico W or a spare Tuya switch?

You can build a capable Bluetooth presence tracker for about $6. The Raspberry Pi Pico W now supports full active Bluetooth Proxy connections with three slots, matching ESP32 parity, so Home Assistant can read, write, and subscribe to BLE devices through it, per the bluetooth_proxy docs.

Many budget Tuya switches and plugs contain BK72xx chips that now support BLE 5.x scanning via the BK72xx BLE tracker, so a spare device can become a presence sensor for free. See our best presence sensors of 2026 for how this compares with dedicated hardware.

What about the new ESPHome Starter Kit?

The $40 ESPHome Starter Kit, launched August 12, 2026, is the easiest way to start with ESPHome if you are new to DIY gear, and it pairs well with our complete ESPHome setup guide. It bundles an ESP32-C6 board with four snap-in modules, requiring no soldering or coding.

For a full breakdown of what is inside and whether it is worth it, read our ESPHome Starter Kit review — we covered it when it launched.

What should you do this week?

If you run ESP32-based Bluetooth proxies or trackers, upgrade to 2026.8.0 now — the BLE/WiFi coexistence fix is important for reliable presence detection, per the official changelog. New buyers can grab a $6 Pico W or repurpose a BK72xx Tuya device.

Finally, mark your calendar: ESPHome Community Day 2026 was announced on August 13, per the official blog, a good chance to learn from other users.

How to set up a $6 Pico W Bluetooth presence tracker

If you want to try the new low-cost path, the setup follows the standard ESPHome flow (bluetooth_proxy docs):

1. Install ESPHome on your computer or use the Home Assistant add-on, then create a new device for the Raspberry Pi Pico W.
2. Add a bluetooth_proxy: entry with the Pico W platform option so the board exposes its three active BLE connection slots.
3. Flash the firmware over USB. The Pico W needs no external programmer — it appears as a USB drive and accepts the firmware file directly.
4. In Home Assistant, the device shows up automatically via local discovery; add it and enable the BLE tracker entities you need.

From there you can create automations based on who is home, exactly like the ESP32-based trackers covered in our ESP32 Bluetooth Proxy for Home Assistant guide. Because everything runs locally, there are no cloud accounts to configure and no recurring fees (official changelog).

FAQ

Is the new Bluetooth presence tracking compatible with my existing Home Assistant setup?

Yes. ESPHome 2026.8.0 works with your existing Home Assistant installation — no changes needed on the Home Assistant side. The new BLE trackers and proxies appear as standard devices, just like the ESP32 versions did, per the official changelog.

Do I need a subscription or cloud account for Bluetooth presence tracking?

No. ESPHome runs entirely on your own hardware, and presence data stays on your local network. There are no cloud subscriptions, no vendor accounts, and no data leaving your home — all BLE processing happens locally on your devices.

What other new components are in ESPHome 2026.8.0?

Beyond Bluetooth, this release adds an LD6002B 60 GHz presence radar (mmWave, detects stationary presence) and a Hörmann garage-door cover, plus multi-interface networking (Ethernet + WiFi in one config) and multi-key OTA signature verification for security, per the official changelog.

📖 Related Reads

• ToolBrain — tool reviews, LLM comparisons, and AI workflow guides

Cross-links automatically generated from SmartHome Field Guide.

← Back to guides