Best Home Assistant Bluetooth Proxy Devices for UK Homes in 2026

Affiliate disclosure: this article contains affiliate links. If you buy through them, we may earn a small commission at no extra cost to you. We do not test devices ourselves — every claim below comes from manufacturer specification pages, official documentation, or owner-review consensus in the Home Assistant community. All prices are approximate, hedged, and were checked in 2026.

If your Home Assistant instance keeps losing contact with a temperature display, a plant sensor or a SwitchBot Bot, the problem is very rarely the sensor. It is almost always the single Bluetooth radio sitting inside your Home Assistant host — often a mini PC or Raspberry Pi tucked into a cupboard next to a metal consumer unit. A Home Assistant Bluetooth proxy solves that by scattering cheap ESP32 radios around the house, close to where the BLE devices actually live, and relaying everything back over Wi-Fi or Ethernet. This guide compares the devices that do that job best in the UK in 2026, from a bare board at approximately £5 to mains-powered units at the other end of the scale that need no flashing at all.

Quick picks

What a Bluetooth proxy actually does

A Bluetooth proxy is an ESP32 board running ESPHome firmware that listens for Bluetooth Low Energy traffic and forwards it to Home Assistant over your home network. Home Assistant’s built-in Bluetooth integration treats each proxy as a remote adapter. That means your host does not need a working Bluetooth radio of its own — or, if you run Home Assistant in a container on a mini PC, any radio at all.

Passive versus active scanning

Most BLE sensors in a smart home are passive broadcasters. Xiaomi LYWSD03MMC thermometers, ATC or PVVX-flashed sensors, Inkbird IBS-TH2 probes, Govee H5075 units and MiFlora plant monitors all simply broadcast their readings into the air. A proxy picks those up without ever making a connection, which is why a single proxy can listen to dozens of passive devices at once.

Active connections are a different matter. Devices such as the SwitchBot Bot, some smart locks and a number of BLE trackers need a genuine connection rather than a passive listen. ESPHome’s own esp32_ble_tracker documentation states that the bluetooth_proxy component defaults to max_connections: 3, and that pushing that figure higher degrades Wi-Fi coexistence — the Bluetooth and Wi-Fi stacks share the same 2.4 GHz radio on the chip, so every extra connection takes time away from the network link carrying your data home. Three is a sensible ceiling; if you need more simultaneous active connections, add another proxy rather than raising the number.

What proxies cannot do

Bluetooth proxies handle BLE only. They will not stream Bluetooth audio, pair with your phone, or talk to Bluetooth Classic hardware such as older car kits and some legacy locks. If a device needs a Classic pairing handshake, a proxy is not the answer.

How to choose a Bluetooth proxy for your home

Match the tier to the job. There are three practical tiers: bare boards you flash yourself, ready-made M5Stack devices, and mains-powered products such as Shelly’s Plus range that ship as working smart-home hardware and only need a setting toggled.

Plan against a signal threshold. Home Assistant’s Bluetooth integration documentation recommends targeting at least −80 dBm RSSI at your furthest sensor. RSSI is the received signal strength — the measurement of how loudly a device reaches the proxy. Below roughly that figure, advertisements start arriving late or not at all, which shows up as intermittent “unavailable” states rather than a clean failure.

Keep everything on one subnet. Proxies are discovered over mDNS, so the proxy and the Home Assistant host must share a subnet. VLANs break that discovery unless you have configured an mDNS proxy or Avahi reflector. This catches out a lot of people who have sensibly separated their IoT devices onto a guest network.

Watch out for USB 3.0 interference. USB 3.0 ports are well documented as radiating noise across the 2.4 GHz band, which is exactly where BLE lives. Plugging a proxy into a USB 3.0 port on a mini PC can measurably hurt its range — use a USB 2.0 port instead, or a 1–2 m USB extension cable to move the radio away from the port.

Decide between Wi-Fi and Ethernet backhaul. Wi-Fi is simpler and needs no cabling, but every proxy is sharing one 2.4 GHz radio for both its Bluetooth scanning and its network backhaul. Ethernet removes that coexistence problem entirely.

Check the active-connection budget covered above, and remember that a proxy’s practical reach is also limited by what you are asking it to do: a passive listening job is far lighter than a dual-role device.

The best Home Assistant Bluetooth proxy devices

M5Stack Atom Lite — the best all-round pick

Best for: almost everyone building their first proxy, and most people adding a second or third.

The M5Stack Atom Lite is the board most often recommended in Home Assistant communities, and the specification explains why. It runs an ESP32-PICO-D4 chip on a board footprint of just 24 × 24 mm, is powered purely over USB-C, and carries a small RGB LED and a Grove port. In the UK it is sold by The Pi Hut, Pimoroni and Amazon UK, typically for around £12–£18.

The standout strength is how little friction there is between unboxing and a working proxy. No flashing tool is required: you use the ESPHome web installer, which runs in Chrome or Edge only and needs a USB-C data cable — not a charge-only cable, which is the single most common reason a first attempt fails silently. Because the board draws so little power, owners report it can sit permanently on a spare USB port on a TV or router without anyone noticing it.

The honest caveat is the antenna. A 24 mm board has a compact antenna, and community feedback suggests budgeting one Atom Lite per floor, or one per two large rooms, in a typical UK house with brick internal walls. Treat that as a starting point and check your RSSI figures once deployed.

Verdict: the default choice — cheap, tiny, and the fastest route from purchase to a working Bluetooth proxy.

M5Stack Atom Echo — proxy and voice satellite in one

Best for: buyers who want a Bluetooth proxy and a Home Assistant voice satellite from a single device.

The Atom Echo uses the same ESP32-PICO chip as the Atom Lite but adds a PDM microphone and a speaker, which is what turns it into a voice satellite as well as a proxy. In the UK it is typically stocked by the same ESP32-focused retailers that carry the Atom Lite — Amazon UK, The Pi Hut and Pimoroni — at around £20–£28.

The attraction is obvious: one device, one power supply, two jobs. The trade-off is equally clear. Running proxy duties and voice duties on the same chip increases CPU load, and community consensus on r/homeassistant notes that the Echo runs at a higher idle temperature than the Atom Lite, which is a straightforward consequence of the extra work and the extra hardware in the same small enclosure.

Verdict: excellent value if you genuinely want voice control in that room; if you only want Bluetooth coverage, the Atom Lite does the same job for less.

Generic ESP32-C3 / DevKit boards — the DIY tier

Best for: confident tinkerers happy to flash firmware manually and accept a bare board with no enclosure.

A bare ESP32-C3 mini board is the cheapest way into Bluetooth proxying, at approximately £5–£10 from AliExpress or Amazon UK. ESPHome supports the ESP32-C3 natively, so the firmware side is well trodden.

Two caveats. First, these boards require manual flashing — there is no equivalent of the one-click web installer experience you get with M5Stack hardware — so you need the toolchain working before you begin. Second, most arrive as bare PCBs, with no case and no USB-C connector niceties beyond the basics. Third, and most importantly for UK buyers, a board at approximately £5–£10 against approximately £12–£18 for an Atom Lite is a real saving per unit, but that gap shrinks once you factor in your own time and the cost of any enclosure or cable you add.

Verdict: the right tier if you enjoy the process and are deploying several units at once; the wrong tier if you want a proxy working tonight.

Olimex ESP32-POE — the wired, interference-free option

Best for: larger homes, outbuildings and anywhere you can run a cable and want to remove Wi-Fi congestion from the equation.

The Olimex ESP32-POE uses an ESP32-WROVER module and supports true 802.3af Power over Ethernet alongside Ethernet data. In the UK it is sold through Mouser and RS Components, typically for around £18–£28.

Its standout strength is architectural: because both power and data arrive over the Ethernet cable, the board never has to share a 2.4 GHz radio between Bluetooth scanning and a Wi-Fi backhaul. That removes the Wi-Fi/BT coexistence issue entirely — the single biggest source of degraded proxy performance — and makes a PoE proxy viable in a loft, garage or outbuilding where Wi-Fi is already marginal.

Be ready to flash it yourself: ESPHome firmware installation is required, so this is not a plug-and-play device in the way a Shelly is. You also need PoE-capable network hardware at the far end, or a PoE injector.

Verdict: the most robust deployment in this guide for anyone willing to run a cable and flash a board.

GL.iNet GL-S10 — Ethernet backhaul for larger homes

Best for: homes that want a wired proxy with an off-the-shelf enclosure.

The GL-S10 is a small cased gateway with Ethernet backhaul, sold in the UK on Amazon UK for approximately £25–£35. Be precise about the variant: the standard GL-S10 SKU is the non-PoE model, so do not assume Power over Ethernet unless you have confirmed that the specific SKU you are buying supports it — check the listing carefully.

Out of the box it ships as a BLE-to-MQTT gateway, which is not the same thing as a Home Assistant Bluetooth proxy. To act as a proxy it requires reflashing to ESPHome, as set out in the official ESPHome installation documentation. Once that is done you get a wired, cased proxy that sidesteps the Wi-Fi congestion problem on the backhaul side.

The caveat, then, is effort and expectation: you are buying hardware and then replacing its stock firmware. If that does not appeal, an Olimex board or a Shelly device may suit you better.

Verdict: a tidy wired proxy for larger homes, provided you are comfortable reflashing it to ESPHome.

Shelly Gen2 / Gen3 Plus devices — the no-flash mains option

Best for: anyone who wants a mains-powered Bluetooth proxy with certification, no soldering and no firmware flashing.

Shelly’s Gen2 and newer Plus devices have confirmed BLE proxy support in three UK-relevant models: the Shelly Plus 1PM, the Shelly Plus 2PM, and the Shelly Plus Plug UK. Shelly’s own knowledge base at shelly.com/support/knowledge-base states that a minimum firmware of 0.14.0-beta or later is required for this capability.

There is no flashing involved. You enable the feature in the Shelly web UI under Settings → Bluetooth, where you switch on both “Enable Bluetooth” and “BT Gateway”. Home Assistant’s Shelly integration then discovers the device automatically, so it appears as a Bluetooth adapter without any YAML work at all — the opposite end of the spectrum from the DIY boards above.

On UK compliance, there is one important distinction. BS 7671 — the wiring regulations — applies to fixed wiring, so a Plus 1PM or Plus 2PM installed behind a light switch or inside an enclosure is notifiable electrical work that should be carried out by someone competent to do it. The Plus Plug UK variant gets around that entirely: it plugs into a standard 13 A socket, so no fixed wiring is touched.

Because Shelly prices vary by model and change frequently, there is no single figure to quote here — the Plus range is typically stocked by Amazon UK and Scan.

Verdict: the best option for buyers who want a certified, mains-powered proxy with zero flashing, especially in the Plug UK form if you would rather not touch fixed wiring.

Using proxies for room-level presence detection

This is the angle that makes Bluetooth proxying more than a reliability fix. Two community projects turn a set of proxies into a room-level presence detection system: Bermuda BLE Trilateration, available through HACS, and ESPresense, documented at espresense.com (Bermuda’s source is on GitHub).

Trilateration works by comparing how strongly the same BLE beacon is received by several proxies at once — the differences in signal strength place the device in a room rather than just “somewhere in the house”. The practical requirement, per both projects’ documentation, is a minimum of roughly three proxies for reliable results, with each proxy having line-of-sight or near-line-of-sight to the tracked area. Walls and floors blur the signal measurements, so a three-proxy setup spread across rooms on one floor will outperform three proxies scattered across three floors.

That requirement is worth planning for at purchase time. If presence detection is your goal, the cheap ESP32-C3 tier becomes much more attractive, because the cost of a three-proxy deployment matters far more than the cost of one.

UK practical and regulatory notes

• Retailers: ESP32 boards and M5Stack hardware are typically stocked by Amazon UK, The Pi Hut and Pimoroni. Olimex boards come through RS Components and Mouser. Shelly hardware is typically stocked by Amazon UK and Scan.
• Wiring: BS 7671 governs fixed electrical wiring in the UK. In-wall Shelly devices such as the Plus 1PM and Plus 2PM fall under that, so plan for a competent installer. The Shelly Plus Plug UK avoids fixed wiring altogether. Mains-powered devices are also the ones most likely to be sited where they are actually useful — near the sensors — rather than wherever a spare USB port happens to be.
• Network: proxies are found by mDNS and must share a subnet with the Home Assistant host. A VLAN that isolates IoT devices will hide them unless mDNS forwarding or Avahi is configured.
• Signal: aim for at least −80 dBm RSSI at the furthest sensor, per Home Assistant’s Bluetooth documentation, and use an RSSI sensor reading in Home Assistant to verify placement rather than guessing.
• Sensor quirks: LYWSD03MMC advertisements are encrypted by default, so you need the device’s bind key or a PVVX/ATC custom firmware flash to decode them passively. MiFlora plant sensors require an active GATT connection for readings — they are not purely passive, so they consume part of your proxy’s active-connection budget.

Frequently asked questions

How many Bluetooth proxies do I need for a typical UK home? Start with one per floor and measure. Community rule of thumb for the Atom Lite’s compact antenna is one per floor or one per two large rooms in a house with brick internal walls, but the only real test is signal strength. Use the proxy’s RSSI reading in Home Assistant and aim for at least −80 dBm at the furthest sensor.

Can a Bluetooth proxy replace the Bluetooth adapter in my Home Assistant host? Yes. Home Assistant’s Bluetooth integration treats a proxy as a remote adapter, so in principle your host needs no Bluetooth radio of its own — useful if you run Home Assistant in a container on a mini PC with no internal Bluetooth. Keep at least one local adapter if you also use Bluetooth for anything outside the proxy’s reach.

My sensors broadcast but never appear. What should I check first? Check whether the device’s data is encrypted or requires a connection. LYWSD03MMC thermometers ship with encrypted advertisements and need a bind key or custom PVVX/ATC firmware, while MiFlora sensors need an active GATT connection rather than a passive listen. If that checks out, move the proxy — poor placement shows up as missing advertisements, not an error message.

Will a Bluetooth proxy work across VLANs or a separate IoT network? Not by default. Proxies are discovered over mDNS and must sit on the same subnet as the Home Assistant host; VLANs break that discovery unless you configure an mDNS proxy or Avahi reflector. If you keep IoT devices on a separate network, plan the mDNS forwarding before you buy.

Do I need an electrician to install a Shelly Bluetooth proxy? Only for the in-wall models. BS 7671, the UK wiring regulations, applies to fixed wiring, so a Shelly Plus 1PM or Plus 2PM installed behind a switch or in an enclosure should be fitted by someone competent to do that work. The Shelly Plus Plug UK plugs into a standard socket and avoids fixed wiring entirely.

Can I run several proxies at once, and will they interfere with each other? Yes, and running several is normal — it is how you cover a whole house and how trilateration projects such as Bermuda and ESPresense achieve room-level accuracy, which needs roughly three well-placed proxies. They do not meaningfully interfere with each other, but every proxy shares its own chip between Bluetooth and Wi-Fi, so Ethernet backhaul removes that bottleneck where you can manage it.

The bottom line

For most UK households, the M5Stack Atom Lite at around £12–£18 is the sensible starting point: tiny, USB-C powered, and flashable through the ESPHome web installer in Chrome or Edge with a proper data cable. Add a Shelly Plus Plug UK if you want a certified, mains-powered proxy with no flashing and no fixed wiring. Step up to the Olimex ESP32-POE or a reflashed GL.iNet GL-S10 if you can run Ethernet and want to remove Wi-Fi congestion from the equation entirely. And if you are chasing room-level presence detection rather than just reliable sensor readings, buy three or more of the cheap ESP32-C3 boards and place them with line-of-sight in mind.