What if the smart lock at your front door could talk to Home Assistant even though your server sits two rooms away and the built-in Bluetooth radio gives up after ten feet? That’s the exact problem a Bluetooth proxy solves, and the fix costs less than a takeout dinner. A small ESP32 board, flashed once, quietly relays Bluetooth Low Energy traffic over Wi-Fi so your Home Assistant instance can reach sensors, locks, and scales scattered across the whole house. This guide walks through the setup step by step, covers the mistakes that trip up most first-timers, and explains when one proxy is plenty and when you need four. (Bluetooth Technology Overview)
What a Bluetooth Proxy Actually Does
A Bluetooth proxy is an ESP32-based device running ESPHome firmware that acts as a remote antenna for Home Assistant. Instead of plugging a USB Bluetooth dongle into the machine running Home Assistant, you place these little boards wherever Bluetooth coverage is weak. Each one listens for BLE advertisements and forwards them to Home Assistant over your existing Wi-Fi network.
The concept arrived with Home Assistant around version 2022.8 in August 2022, and it changed how people build out Bluetooth coverage. Before that, your options were a long USB extension cable or a dongle dangling out a window. Now a $5 to $15 board does the job from a wall outlet in any room.
The key hardware rule: ESP32 variants only. Original ESP32, ESP32-C3, and ESP32-S3 boards all work. The ESP8266 does not support proxying at all, so don’t dig an old NodeMCU out of a drawer and expect it to cooperate.
What You Need Before Starting
Gather these items first so the process runs in one sitting:
- An ESP32 development board (ESP32 DevKit, ESP32-C3, or ESP32-S3). Boards with external antennas or Ethernet ports are worth the small premium.
- A USB data cable that actually carries data. Charge-only cables are the single most common cause of “my board won’t flash” frustration.
- A computer with Chrome or Edge for the browser-based installer.
- Your Wi-Fi network name and password, including the 2.4 GHz band specifically. ESP32 boards do not connect to 5 GHz networks.
- Home Assistant running on the same network, with the ESPHome integration available.
- A USB power adapter for permanent placement once flashing is done.
If you’re still mapping out your smart home backbone, it’s worth reading up on how other always-on devices like best smart speakers for home automation fit into the same network, since both depend on stable 2.4 GHz Wi-Fi.
Step-by-Step: Flashing Your First Proxy
Step 1: Connect the Board
Plug the ESP32 into your computer with the data cable. If the board has a boot button, you may need to hold it while plugging in to enter flash mode. Most modern boards handle this automatically.
Step 2: Use the Web Installer
The ESPHome project page hosts a browser-based installer that flashes a ready-made Bluetooth proxy configuration without any YAML editing. Open it in Chrome or Edge, click connect, and select the serial port your board appears on. The installer writes the firmware, and the board reboots into a working proxy.
This is the path most people should take. It skips the ESPHome dashboard entirely and takes about five minutes from plug-in to connected.
Step 3: Join Your Wi-Fi
During installation, the installer asks for your network credentials and a name for the device. Pick something descriptive like `proxy-living-room` or `proxy-garage` so you can identify it later when you have several. The board connects to Wi-Fi and starts broadcasting itself on the network.
Step 4: Let Home Assistant Discover It
Home Assistant picks up ESPHome devices automatically through the ESPHome integration. Within a minute or two, a notification appears under Settings, then Devices and Services, offering to add the new device. Accept it, assign it to an area, and you’re done.
You do not need to add a separate Bluetooth integration entry for each proxy. The Bluetooth integration handles the radio side, and the ESPHome integration handles the device side. Both need to be present, but the proxy itself slots in with one click.
Step 5: Verify Coverage
Open the Bluetooth integration page in Home Assistant and check the adapter list. Your new proxy should appear alongside any local adapter, showing how many devices it currently sees. Walk a BLE sensor around the house and watch the connection source change as different proxies pick it up.
The Minimal YAML for People Who Prefer the Dashboard
If you flash through the ESPHome dashboard instead of the web installer, the configuration is short. You need the `esp32` block with your board type, the `wifi` block with credentials, `api` and `ota` for Home Assistant communication and over-the-air updates, and the `bluetooth_proxy` block itself.
The option that matters is `active`. Setting it to true lets the proxy make actual connections to devices instead of only listening for broadcasts. Sensors that only advertise work fine in passive mode. Devices that require reads and writes, like many smart locks, blood pressure monitors, and bathroom scales, need active mode.
Each proxy supports a limited number of simultaneous active connections. If you have several devices that need real connections in one area, plan on more than one proxy rather than expecting a single board to juggle everything.
Passive vs. Active Mode: Which Do You Need?
| Mode | What It Does | Best For | Limitations |
|---|---|---|---|
| Passive | Listens for BLE advertisements only | Temperature sensors, plant monitors, beacon tags, presence detection | Cannot read or write to devices |
| Active | Opens connections to devices | Smart locks, scales, fitness trackers, devices needing commands | Limited simultaneous connections per proxy |
Most households end up running active mode on every proxy because the option costs nothing and prevents future headaches. The tradeoff is a slightly higher power draw and a bit more radio traffic, neither of which matters in practice.
Common Mistakes That Waste an Afternoon
Using a charge-only USB cable. The board powers up, the computer sees nothing, and you spend an hour blaming drivers. Swap cables first.
Trying to connect to a 5 GHz network. ESP32 boards only speak 2.4 GHz. If your router merges both bands under one name, the board usually still connects, but a separate 2.4 GHz SSID removes all doubt.
Placing the proxy next to the router. Wi-Fi and Bluetooth share the same radio on ESP32 chips, and a proxy sitting in a strong Wi-Fi signal spends its time managing that link instead of listening for BLE. Put proxies in the rooms where the Bluetooth devices actually live, not next to the access point.
Forgetting mDNS across subnets. Proxies and Home Assistant need to find each other. If you run separate VLANs for IoT devices and your server, mDNS reflection has to be configured on the router, or you’ll need to add the proxy by IP address manually. This trips up people with segmented networks constantly.
Expecting one proxy to cover a whole house. Walls eat 2.4 GHz signals. Two or three proxies spread through a home work far better than one powerful board in the center. The same principle applies to other coverage-sensitive home tech, whether that’s picking the best home generators for reliable backup power during outages or choosing where to mount a mesh node.
Ignoring firmware updates. ESPHome and Home Assistant both release monthly. Option names and dashboard menus shift over time, so check the current documentation for your installed versions rather than following a two-year-old tutorial.
How Many Proxies Do You Need?
The honest answer is “more than you think, but fewer than you fear.” A single proxy in a 1,200-square-foot apartment handles nearly everything. A two-story house with a detached garage typically wants three: one per floor and one near the garage or front door for locks and outdoor sensors.
Placement matters more than quantity. A proxy in a hallway closet with a metal door will underperform one sitting on an open shelf. Elevate them, keep them away from microwaves and cordless phone bases, and avoid enclosing them in metal cabinets.
Ethernet-connected ESP32 boards, such as the Olimex ESP32-POE, sidestep the Wi-Fi and Bluetooth coexistence problem entirely. If you have a network drop near a troublesome area, an Ethernet proxy is the most reliable option available.
Alternatives Worth Considering
A USB Bluetooth adapter plugged into the Home Assistant server works well when the server sits centrally and the devices are close. It’s the simplest option and requires no extra hardware beyond the dongle.
An Ethernet-connected ESP32 proxy wins on reliability for fixed locations with cabling available.
Multiple Wi-Fi proxies win on flexibility and cost when devices are spread across a large space.
For anyone building out a broader home network with always-on devices, the same planning logic used for best espresso machine for home setups applies: match the hardware to the actual usage pattern, not the spec sheet. And if you’re troubleshooting connectivity issues elsewhere in the house, techniques for how to stop snoring at night home remedies share nothing with networking, but the habit of testing one variable at a time does translate to debugging Bluetooth coverage.
Keeping Proxies Healthy Long-Term
Once everything works, a few habits keep it working. Enable over-the-air updates so you can push firmware without unplugging boards. Label each proxy with its physical location in Home Assistant’s area settings. Watch the Bluetooth integration diagnostics page occasionally to spot a proxy that’s dropped offline.
Power delivery deserves attention too. Cheap USB chargers that brown out under load cause random disconnects that look like Bluetooth problems but aren’t. A decent 5V 1A adapter per board prevents a category of ghost bugs.
Finally, expect version drift. Home Assistant and ESPHome both move fast, and menu paths change. The setup you complete today may look slightly different in six months. That’s normal, not a sign you did something wrong.
Conclusion
A Home Assistant Bluetooth proxy setup is one of the highest-value, lowest-cost upgrades in a smart home. A board that costs less than lunch, five minutes with a browser installer, and one click in Home Assistant can turn a dead zone into full BLE coverage. Start with one proxy where your Bluetooth devices actually live, verify it in the Bluetooth integration panel, and add more only when a device drops out. Skip the charge-only cables, keep the boards off the router, and check current docs before following any tutorial, including this one. The result is a quiet, reliable bridge between your Bluetooth gadgets and the automation engine that makes them useful.
Frequently Asked Questions
Can I use an ESP8266 as a Bluetooth proxy?
No. The ESP8266 has no Bluetooth radio and does not support proxying. You need an ESP32 variant, such as the original ESP32, ESP32-C3, or ESP32-S3.
Do I need the ESPHome integration if I already have the Bluetooth integration?
Yes, both serve different roles. The Bluetooth integration manages the radio layer, while the ESPHome integration handles communication with the proxy device itself. Proxies are discovered through the ESPHome integration automatically.
Why does my proxy keep dropping offline?
The usual suspects are an underpowered USB charger, a weak 2.4 GHz signal at the proxy’s location, or Wi-Fi and Bluetooth radio contention. Try a better power adapter first, then move the proxy closer to the devices it serves rather than closer to the router.
How many active connections can one proxy handle?
ESPHome limits simultaneous active connections per proxy, and the exact number has changed across releases. If you have several devices that require real connections in one area, plan on adding a second proxy rather than pushing one board to its limit.
Will a proxy work across separate VLANs or subnets?
Only with extra configuration. Proxies rely on mDNS discovery, which does not cross routed subnets by default. You’ll need mDNS reflection on your router or manual IP configuration for the proxy in Home Assistant.
Is a USB Bluetooth adapter better than a proxy?
It depends on placement. A USB adapter is simpler and cheaper when your Home Assistant server sits centrally among the devices. A proxy wins when the server is far away, in a basement, or in a rack where Bluetooth signals can’t escape.
