Bluetooth BLE in Home Assistant: Sensors and Proxies

Bluetooth is already in your pocket, your car, and probably several other devices scattered around your home, and its specific low-energy variant has quietly become a genuinely useful, remarkably low-cost way to add real sensors to a smart home setup. This lesson covers exactly how Home Assistant handles Bluetooth natively, and how a small handful of cheap ESP32 boards can genuinely extend its effective range across your entire house for just a few dollars total.

Classic Bluetooth versus BLE: two different protocols

Classic Bluetooth, the protocol behind wireless headphones and car audio systems, and Bluetooth Low Energy, often shortened to BLE, share a brand name and radio frequency but are genuinely different protocols under the hood, designed for very different jobs. Classic Bluetooth prioritizes continuous, higher-bandwidth streaming, exactly what audio needs, at the cost of meaningfully higher power draw. BLE instead prioritizes brief, infrequent bursts of data at extremely low power, exactly what a small battery-powered sensor needs to run for months or years on a single coin cell battery. Nearly everything covered in this lesson refers specifically to BLE, the variant that matters for smart home sensors.

How Home Assistant handles Bluetooth natively

Home Assistant includes built-in Bluetooth support that can use a Bluetooth adapter directly attached to your server, either a built-in radio on hardware like a Raspberry Pi or Home Assistant Yellow, or a small USB Bluetooth dongle on a mini PC or thin client that doesn't have one. Once enabled, Home Assistant automatically scans for and identifies many popular BLE sensor brands without any manual configuration at all, a device simply appears in your integrations list the moment it's detected broadcasting nearby, genuinely one of the smoothest zero-configuration experiences anywhere in this entire course.

Bluetooth Proxy: extending range through ESP32 boards

Bluetooth's biggest practical limitation is range, a single adapter on your server typically covers only the room it sits in and maybe an adjacent one, genuinely limiting for a sensor in a bedroom or garage on the other side of the house. Home Assistant's solution is Bluetooth Proxy, a small piece of ESPHome firmware that turns a cheap ESP32 development board into a relay, forwarding any BLE broadcasts it hears back to Home Assistant over WiFi. Scatter a handful of these inexpensive boards, often costing only a few dollars each, throughout your home, and Home Assistant automatically stitches their coverage together, picking the strongest available signal for each sensor without any manual configuration needed on your part.

Popular BLE devices worth buying

Xiaomi and Govee both sell inexpensive BLE temperature and humidity sensors, widely available on Amazon in the US and UK, with active community support in Home Assistant despite neither brand officially endorsing the integration. SwitchBot's BLE-based buttons, curtain motors, and other actuators integrate well and solve a genuinely useful niche, adding smart control to existing switches and blinds without any wiring at all. Several BLE-based plant moisture sensors and presence-detecting key fobs round out the category, all sharing the same core appeal: genuinely low cost and zero-wiring installation, in exchange for the range limitations Bluetooth Proxy exists to solve.

Setting up a BLE sensor in Home Assistant, step by step

Confirm Home Assistant's Bluetooth integration is active through Settings, Devices and Services, it's usually enabled automatically if a compatible adapter is detected during setup. Power on your new BLE sensor within range of your server or a Bluetooth Proxy, most devices begin broadcasting immediately with no button press needed. Within a minute or two, Home Assistant should surface a new device discovery notification, confirm it, and the sensor's entities appear ready to use in dashboards and automations exactly like any other integration covered elsewhere in this course.

BLE versus Zigbee: when to choose which

Zigbee devices, covered in their own dedicated module, generally offer better range through genuine mesh networking, mains-powered Zigbee devices repeat signal for battery ones the way Lesson 1 described for Z-Wave, something BLE fundamentally lacks without Bluetooth Proxy's WiFi-based workaround. BLE devices tend to be noticeably cheaper per unit though, and for a small apartment or a sensor placed close to an existing proxy or your server itself, that range disadvantage rarely matters in practice. As a rough rule, BLE suits budget-conscious households with a compact footprint, while Zigbee scales more gracefully to a large home with sensors spread across many rooms.

Common problems with Bluetooth in Home Assistant

A sensor that never appears usually means it's simply out of range of any adapter or proxy, the most common fix by far is adding a Bluetooth Proxy board closer to that specific sensor's location rather than troubleshooting the sensor itself. Intermittent, flaky readings often point to interference from a crowded 2.4GHz environment, the same congestion concern that applies to WiFi and Zigbee elsewhere in this module, worth spacing proxy boards away from routers and other radio-heavy equipment where possible. And a server's built-in Bluetooth adapter that seems to stop working after a period of uptime is a known quirk on some hardware, a quick add-on or Home Assistant restart typically resolves it without needing any deeper troubleshooting.

A real story: covering a whole house for a few dollars

One reader with a three-story townhouse found their server's built-in Bluetooth adapter, sitting in a basement utility closet, could barely see sensors on the same floor. Rather than replacing any hardware, they flashed three cheap ESP32 boards with the Bluetooth Proxy firmware and placed one on each floor, plugged into an ordinary wall outlet with a small USB power adapter. Every existing BLE sensor in the house, previously unreliable or entirely invisible to Home Assistant, started reporting consistently within minutes of the proxies coming online, a total hardware cost of under twenty dollars solving a problem that might otherwise have pushed them toward a much more expensive, far more involved Zigbee retrofit across the entire house instead.

Presence detection through Bluetooth

Beyond fixed sensors, Bluetooth's ability to detect a phone or key fob's presence and rough signal strength makes it a genuinely useful tool for room-level presence detection, knowing not just that someone is home, but roughly which room they're in, covered in more depth in this course's later automation modules. Multiple Bluetooth Proxy boards spread through the house each report the same phone's signal strength independently, and Home Assistant can triangulate a rough room-level location from those readings, a genuinely clever use of infrastructure you've likely already set up purely for sensor coverage.

What this looks like for your mini smart home

For this course's starter kit, a single inexpensive BLE temperature sensor is a genuinely good, low-risk way to see this protocol in action, and if your home is more than a room or two, a Bluetooth Proxy board or two costs very little indeed and meaningfully improves overall reliability right from day one. This is one of the cheapest ways to add real sensor coverage anywhere in this entire module, worth keeping firmly in mind as your own device wishlist naturally continues to grow over the coming weeks and months still genuinely lying just ahead of you here.

Building your own Bluetooth Proxy: what it actually takes

Building a Bluetooth Proxy is genuinely one of the simplest DIY projects covered anywhere in this course, requiring nothing more than a cheap ESP32 development board, a USB power source, and roughly five minutes with ESPHome's web-based installer, no soldering, no custom wiring, and no programming knowledge needed at all. ESPHome maintains a ready-made Bluetooth Proxy configuration specifically for this purpose, you simply select it, connect the board to your computer via USB for the initial flash, and once it's on your WiFi network, every subsequent update can be pushed wirelessly. This genuinely approachable entry point makes Bluetooth Proxy a great first DIY project for anyone who hasn't yet tried flashing their own hardware, a confidence-building warm-up before the more involved ESPHome projects covered in a later module.

Choosing where to place proxy boards

A Bluetooth Proxy board's range is roughly comparable to a phone's Bluetooth range, meaningful but not enormous, typically covering one floor of a moderately sized home reasonably well from a central location. For a multi-story house, one proxy per floor is a sensible starting point, placed centrally rather than in a corner, and near an ordinary wall outlet since these boards need continuous USB power rather than running on battery. Avoid placing them inside metal enclosures or directly behind large metal appliances, radio signal loses strength quickly through metal, the same physical principle that applies to WiFi and Zigbee coverage covered elsewhere in this course.

Battery life expectations for BLE sensors

A well-designed BLE temperature or humidity sensor, broadcasting its reading only periodically rather than continuously, commonly runs for a year or more on a single small coin cell battery, genuinely impressive for a device this cheap and this easy to deploy. Colder locations, an outdoor sensor or one in an unheated garage, tend to drain batteries meaningfully faster than a sensor kept at normal indoor room temperature, a real-world battery chemistry limitation worth factoring into placement decisions for anything you don't want to be swapping batteries on every few months. Most sensors report their current battery level as a standard entity in Home Assistant, worth adding a simple low-battery automation alert once you have more than a handful deployed around the house.

BLE security considerations

Most consumer BLE sensors broadcast their readings in the clear, unencrypted, readable by any Bluetooth receiver within range, not just your own Home Assistant setup, worth knowing if you're placing sensors somewhere genuinely sensitive rather than a general concern for a typical temperature sensor in a hallway. Some newer BLE devices, particularly those from brands prioritizing security, do support encrypted broadcasts, requiring a device-specific bind key to decode in Home Assistant, a small extra setup step but a real security improvement for anything more sensitive than an ambient temperature reading. As with WiFi IoT devices covered earlier in this module, research a specific device's security posture before trusting it with anything you'd genuinely mind a stranger being able to read.

Bluetooth and your server's other radio needs

If your server also has a Z-Wave or Zigbee USB stick attached, as covered in earlier lessons, it's worth spacing radios physically apart where your hardware allows it, several 2.4GHz-adjacent radios crammed into adjacent USB ports on the same small device can occasionally cause minor interference with each other. A short USB extension cable for your Bluetooth adapter, the same trick recommended for Z-Wave controllers back in Lesson 1, is a cheap, genuinely easy way to reduce this risk considerably, giving each individual radio a little more physical breathing room rather than stacking every single one directly against your server's own metal case where interference tends to be at its worst.

A quick glossary for this lesson's terms

BLE: Bluetooth Low Energy, the low-power variant of Bluetooth used by most smart home sensors. Bluetooth Proxy: an ESPHome-based relay that extends Home Assistant's Bluetooth range over WiFi. Coin cell: the small, flat, long-lasting battery type common in BLE sensors. Bind key: an encryption key some BLE devices require to decode their broadcasts securely. Presence detection: using a phone or fob's Bluetooth signal to estimate someone's location within the home. This vocabulary will come up again and again as later modules build real automations around the sensors this lesson has just introduced, so it's worth taking a moment now to make sure each of these five terms genuinely feels familiar before moving on to the next lesson in this module.

Key takeaways

Lesson 5 turns to a handful of niche, more specialized protocols, mBus, Modbus, KNX, and several others, that each solve genuinely specific problems the more mainstream protocols already covered in this module simply don't quite address on their own.