Skip to main content
The Quantum Dispatch
Back to Home
Cover illustration for Home Assistant Bluetooth Proxy Guide: ESP32 Setup and Tips

Home Assistant Bluetooth Proxy Guide: ESP32 Setup and Tips

A Home Assistant Bluetooth proxy turns a cheap ESP32 into a BLE relay. Learn which boards to pick, why Ethernet allows 4 slots, and where to place them.

Alex Circuit
Alex Circuit★Nov 17, 2026★9 min read

Bluetooth Low Energy is everywhere in a modern smart home: temperature and humidity sensors, plant monitors, smart locks, toothbrushes, scales, presence tags. The catch is range. A single Bluetooth adapter plugged into the machine running Home Assistant can only hear what is near it, and walls, floors and appliances eat BLE signals for breakfast. A Home Assistant Bluetooth proxy solves that by placing small, cheap ESP32 boards around the house that listen for BLE devices and forward everything to Home Assistant over your network. This guide explains how a Bluetooth proxy works, which hardware to choose, how many connections each proxy can handle, and where to put them for the best coverage.

  • What it is: an ESPHome feature that relays BLE advertisements and active connections from an ESP32 (or Pico W) to Home Assistant over Wi-Fi or Ethernet
  • Connection limits: ESP32 proxies default to 3 active connection slots; Ethernet-connected proxies can generally handle 4 reliably
  • Best hardware: an Ethernet ESP32 board with an external antenna; Wi-Fi boards work fine for smaller homes
  • Biggest mistake: placing proxies in racks or right next to routers and switches

Quick Picks: Best Bluetooth Proxy Hardware by Situation

  • Best overall: an Ethernet or PoE ESP32 board with an external antenna. The ESPHome documentation specifically suggests boards like the Olimex ESP32-PoE-ISO-EA, because Ethernet frees the radio from Wi-Fi traffic
  • Best budget pick: any common ESP32 dev board on Wi-Fi, powered by a USB phone charger. Fine for covering a room or two of passive sensors
  • Best for Raspberry Pi fans: a Raspberry Pi Pico W (RP2040/RP2350), which ESPHome now supports as a full proxy with up to 3 active connections
  • Best all-in-one: a multi-function box such as the new Home Assistant Connect AUX-2, which adds a 3-connection BLE proxy alongside audio streaming, RS-232 and PoE
  • Avoid for active devices: BK72xx and LN882x boards, which ESPHome lists as advertisement-only proxies

What Is a Home Assistant Bluetooth Proxy?

Home Assistant's Bluetooth integration supports Bluetooth Low Energy devices (Bluetooth Classic is not supported). Normally it uses a Bluetooth adapter attached to the Home Assistant host. A Bluetooth proxy is a separate device running ESPHome with the bluetooth_proxy component enabled. It listens for BLE traffic and passes it to Home Assistant, which then treats those devices as if they were nearby. Home Assistant combines all of your proxies and local adapters, so adding a proxy simply extends coverage.

There are two jobs a proxy can do:

  • Passing advertisements: many sensors simply broadcast their readings. The proxy hears the broadcast and forwards it. This is cheap, needs no connection slot, and a single proxy can handle a large number of such devices
  • Active connections: some devices, such as certain locks or thermostats, require Home Assistant to open a connection and read or write GATT characteristics. Each active connection occupies one of the proxy's limited connection slots

Understanding that distinction is the key to planning how many proxies you need.

How Many Devices Can One Bluetooth Proxy Handle?

For advertisement-only sensors, the practical limit is mostly radio range and airtime. For active connections, it is the number of connection slots. Per the ESPHome Bluetooth Proxy documentation:

  • ESP32 default: 3 connection slots. Each slot consumes roughly 1KB of RAM, with a hard maximum of 9, but ESPHome recommends not exceeding 5 to avoid stability and memory issues
  • Ethernet ESP32 boards: can generally handle 4 slots reliably, because the radio is not shared with Wi-Fi traffic. Set connection_slots to 4 if you need the extra connection
  • RP2040/RP2350 (Pico W family): 3 slots by default, which is also the platform maximum. Lowering it to 1 or 2 frees static RAM
  • Always-connected devices: a device that stays connected continuously uses one slot the whole time, so two smart locks on one proxy leave only one spare slot on a default ESP32 configuration

A sensible rule: count your active devices per area, keep at least one free slot per proxy, and add another proxy rather than pushing slots higher.

Which ESP32 Board Should You Use as a Bluetooth Proxy?

Any ESP32 with Bluetooth will work, but some choices make life easier. If you are unsure which chip family you have, our ESP32 variant guide breaks down the differences between the classic ESP32, S3, C3, C6 and newer parts.

Wi-Fi ESP32 Boards

The cheapest route is a generic ESP32 dev board flashed with ESPHome, connected over Wi-Fi and powered from USB. The trade-off is that the same 2.4 GHz radio handles both Wi-Fi and Bluetooth, so busy networks can reduce Bluetooth performance. For a handful of passive sensors in one area, that rarely matters.

Ethernet and PoE ESP32 Boards

ESPHome's documentation is direct about this: using a board with an Ethernet connection offloads the ESP32's radio from Wi-Fi traffic and improves Bluetooth performance. An external antenna helps further. PoE boards are especially tidy because one cable carries data and power, which makes it easy to mount a proxy high on a wall or in a hallway ceiling. One caution from the docs: aggressive scan settings can cause overheating on some PoE-based proxies, so stick with the defaults.

Raspberry Pi Pico W

Raspberry Pi's RP2040 and RP2350 boards with wireless now run as full proxies with active connection support through the BTstack GATT client, up to 3 concurrent connections. If you have a spare Pico W in a drawer, it is a free proxy. Existing advertisement-only Pico W configurations gain connection slots automatically on their next update.

Ready-Made Devices

If you would rather not flash anything, several products ship with Bluetooth proxy support built in. ESPHome maintains a projects list of ready-made devices with proxy support, and multi-function hubs like the Connect AUX-2 bundle a proxy with other features.

Where Should You Place Bluetooth Proxies?

Placement matters more than people expect. A few practical rules drawn from the ESPHome guidance and general radio behavior:

  • Keep them out of racks and away from network gear. ESPHome specifically advises against placing proxy nodes in racks or close to routers and switches, which are electrically noisy and often surrounded by metal
  • Go high and central. A proxy on a shelf or wall in the middle of a room hears more than one tucked behind a TV
  • One per floor, then fill gaps. Start with one proxy per level, check which devices still report weak signal or drop out, and add proxies near those areas
  • Put one near each always-connected device. Locks on outside doors are common trouble spots; a proxy near the entrance usually fixes flaky lock control
  • Mind metal and water. Refrigerators, mirrors, aquariums and metal cabinets block BLE surprisingly well

Should You Use Passive or Active Scanning?

The ESP32 BLE tracker defaults to active scanning, which requests extra scan-response data from devices. According to ESPHome, passive scanning works for most BLE devices and is sufficient for ongoing operation; active scanning is typically only needed when you first add new devices. Active scanning also increases battery drain on battery-powered sensors. If a proxy runs hot, or your sensors seem to eat batteries, switching the tracker to passive scanning is an easy fix. ESPHome also recommends leaving the scan interval and window at their defaults, since changing them typically adds CPU load and network traffic without meaningful benefit.

How to Set Up a Bluetooth Proxy in Home Assistant

The overall flow is short:

  1. Flash ESPHome onto your ESP32 or Pico W, either from a ready-made project page or with your own configuration that includes the BLE tracker for your platform and the bluetooth_proxy component
  2. Adopt the device in Home Assistant, where it appears under Settings, Devices and services once it joins your network
  3. Let discovery run. BLE devices the proxy hears appear as discovered integrations, just as they would with a local adapter
  4. Check memory settings if needed. ESPHome recommends the esp-idf framework over arduino because it uses less memory, and disabling the optional web server component frees additional RAM

If Home Assistant runs in a container rather than Home Assistant OS, note that a local Bluetooth adapter needs extra container permissions and D-Bus access, per the Home Assistant Bluetooth integration docs. Proxies sidestep that entirely because they reach Home Assistant over the network, which is one more reason they are popular with Docker and virtual machine installs.

Do Bluetooth Proxies Work With Every BLE Device?

Not quite. Only BLE devices with Home Assistant integrations are supported, and some devices have quirks with active connections. ESPHome keeps a device compatibility section in its proxy documentation for that reason. Bluetooth Classic devices, such as most older speakers and headsets, are not supported by the Bluetooth integration at all.

Bluetooth Proxy FAQ

Do I still need a Bluetooth adapter on my Home Assistant server?

No. Proxies can provide all of your Bluetooth coverage. Many people keep the server adapter as one more listener, but it is optional.

Can one ESP32 be a Bluetooth proxy and do other jobs?

Yes, within its memory budget. Many people add a temperature sensor or status LED to a proxy. Just remember each active connection slot uses RAM, so heavy combined configurations may need fewer slots.

Is Ethernet really worth it?

For a busy home with several active devices, yes. ESPHome says Ethernet proxies can generally handle 4 slots reliably because they do not share the radio with Wi-Fi. For a few passive sensors, Wi-Fi boards are perfectly adequate.

The Bottom Line

A Home Assistant Bluetooth proxy is one of the best value upgrades in home automation: a few dollars of ESP32 hardware can make distant sensors and locks behave as though they were sitting next to your server. Start with one proxy per floor, prefer Ethernet where you have active devices, keep proxies away from network racks, and leave scan settings at their defaults. If you are still choosing the machine that runs Home Assistant itself, our Home Assistant hardware guide compares the main options, and you can find more ESP32 and SBC projects in our mini computers coverage.

Sources: ESPHome Bluetooth Proxy documentation — accessed November 16, 2026; Home Assistant Bluetooth integration documentation — accessed November 16, 2026; CNX Software on Home Assistant Connect AUX-2 — November 16, 2026.

More Mini Computers Stories