Your TV, air conditioner and soundbar only listen to their plastic remotes, and you want Home Assistant pressing those buttons. Until this year that meant learning codes into a Broadlink and replaying them from scripts. Now that Home Assistant has a native infrared entity, the best IR blaster for Home Assistant is one whose integration exposes that entity, because the LG, Samsung and Gree integrations can then drive the appliance by name.
We sorted seven IR blasters by their path into Home Assistant: ESPHome proxies (Seeed XIAO IR Mate, M5Stack AtomS3 Lite, Athom), Broadlink, a Zigbee coordinator with IR, Tuya Zigbee blasters on ZHA, and SwitchBot hubs. Specs and prices come from the makers and live Amazon US listings, as we had no blasters on the bench. The software ran in our lab: we built the proxy firmware and drove LG Infrared end to end against the built-in demo emitter. We confirmed that chain working in November 2026 on Home Assistant 2026.11.1 and ESPHome 2026.10.2.
Compare the best IR blaster for Home Assistant by path
Read the “Infrared entity” column first. A blaster with one can be picked as the emitter when you add LG Infrared, Samsung Infrared or any of the other brand integrations, while a blaster without one stays on its own code-learning path. Prices are Amazon US bands from November 2026 unless the row says direct, so check the live price before you buy.
| Job | Blaster | Path into Home Assistant | Infrared entity | Price band |
|---|---|---|---|---|
| Best overall | Seeed XIAO IR Mate | ESPHome, local push | Emitter and receiver | about $30 on Amazon, less direct from Seeed |
| Learned codes plus 433 MHz RF | Broadlink RM4 Pro | Broadlink, local polling | Emitter only | about $45 |
| DIY proxy, no soldering | M5Stack AtomS3 Lite | ESPHome, local push | Emitter only | about $15 |
| Pre-flashed IR plus RF | Athom RF433 IR remote | ESPHome, local push | Emitter and receiver | about $20 to $26, direct |
| Coordinator with IR built in | SMLIGHT SLZB-Ultima | SMLIGHT, local push | Emitter and receiver | no maker price |
| Zigbee blaster | Tuya TS1201 (ZS06 type) | ZHA, local polling | Emitter, plus a receiver class | about $24 to $29 |
| Already on SwitchBot | SwitchBot Hub 3 | SwitchBot Cloud, cloud polling | None | about $100 |
The IoT class in the third column is what the Home Assistant manifests say, read straight out of the container in our lab. Local push and local polling never leave your network. Cloud polling means the SwitchBot servers sit between Home Assistant and the hub, and the integration needs a token and secret from the SwitchBot app.
Pick the integration before the hardware
The infrared entity platform arrived in Home Assistant 2026.4 with LG Infrared as its first brand integration, and the Broadlink and SMLIGHT emitters followed in 2026.5, so run 2026.5 or newer for every pick below. The entity is a building block. You never add it by itself. A brand integration such as LG Infrared knows the codes for a TV. It turns a button press into raw mark and space timings and hands them to the emitter you picked at setup. The provider integration (ESPHome, Broadlink, ZHA, SMLIGHT) then fires those timings out of its LED. So the brand never talks to the hardware, and any blaster with an emitter works with any brand integration.

To see which providers exist today, we listed every integration in the Home Assistant container that ships an infrared.py platform. The release notes only tell part of the story here: the ZHA infrared platform for Tuya blasters is not called out anywhere we could find, but it’s in the build:
docker exec homeassistant sh -c 'cd /usr/src/homeassistant/homeassistant/components && ls -d */infrared.py */radio_frequency.py'
Six real providers came back, plus kitchen_sink, which is the Home Assistant demo integration. Only Broadlink and ESPHome also carry a radio_frequency platform for 433 MHz devices:

The other side of the handshake is the brand list. A short script over the manifests printed twelve integrations that depend on infrared, from lg_infrared and samsung_infrared to gree_infrared for air conditioners and dyson_infrared for fans. Every one of them is assumed_state, because infrared is one way: Home Assistant remembers what it last sent, not what the TV is actually doing.

That gives three rules for choosing, in order of how much they change what you can automate:
- Check that the integration for the blaster provides an infrared emitter, or the brand integrations cannot use it.
- Check for a receiver entity if you want Home Assistant to notice the handheld remote, which Gree Infrared, OSRAM Infrared and LG Infrared air conditioners use to keep their state in step.
- Check the IoT class, and skip anything cloud only unless you already run that vendor’s app.
Placement matters as much as the brand. Infrared is line of sight, so one blaster covers one room. A cabinet door between the LED and the receiver window on the TV is enough to break it. Plan on one cheap proxy per room rather than one expensive hub for the house. The proxies are light work for Home Assistant itself, so the mini PC you run Home Assistant on needs no extra headroom for them.
Start with the Seeed XIAO IR Mate
The XIAO IR Mate is the device the Home Assistant team pointed at when infrared landed, and it is still the only IR proxy on the ESPHome Ready-Made Projects page. You flash it from the browser, Home Assistant discovers it, and you get both an infrared emitter and an infrared receiver entity with no YAML of your own.

Inside is a XIAO ESP32-C3. The official ESPHome config we pulled from the esphome/infrared-proxies repo drives the IR LED on GPIO3 at a 50% carrier duty and reads an inverted receiver on GPIO4, both through the experimental ir_rf_proxy component. Seeed lists three high-power IR LEDs for 360-degree coverage and one high-sensitivity receiver, plus a touch pad, a vibration motor and a status LED, and says it learns up to 10 commands from a standard remote. The puck is 65 mm across and 19 mm tall, powered over USB-C.
We compiled that exact config in our lab. The first build took 3 minutes 12 seconds because ESPHome downloads the ESP-IDF toolchain, and an unchanged rebuild took 1.8 seconds. The firmware uses 52.1% of flash and 33.8% of RAM, so there’s room for a few sensors if you fork the YAML later.

Who it’s for: anyone starting fresh who wants the brand integrations working on day one. The receiver also serves integrations that read the handheld remote. Skip it if you need RF as well, or you’re wary of early hardware. Seeed sells it as an Early Build with a 3D-printed case. Buy it direct from Seeed at $10.90 if you can wait for shipping, because the Amazon listing is a third-party reseller charging nearly three times that, with a handful of units left in November. It runs about $30 (check the price on Amazon).
Reuse a Broadlink RM4 Pro for learned codes and RF
If a Broadlink is already on your shelf, do not replace it. The Broadlink integration now creates an infrared emitter entity next to its old remote entity, so the same box serves LG Infrared and your existing remote.send_command scripts. The RM4 Pro also gets a radio_frequency entity for 433 MHz devices such as blinds and fans. It has no 315 MHz radio, which matters in the US, where plenty of blind and fan remotes use that band; the 315 MHz range on the integration page applies to other RM pro hardware.
Broadlink rates the RM4 Pro at 38 kHz IR plus 433 MHz fixed-code RF on 2.4 GHz Wi-Fi, in an 84.4 mm square body powered at 5 V 1 A. Home Assistant talks to it locally, but it polls, and it only offers an emitter. There’s no infrared receiver entity, so integrations that follow the handheld remote cannot use it for that half. Learning still happens through remote.learn_command, which is where the RM4 stays better than any proxy for oddball devices no brand integration covers.
Best fit: households with RF blinds or fan remotes, and anyone with a library of learned codes. Go smaller when you only need IR in one room: the RM4 mini is IR only for about $26 and gets the same infrared emitter entity. The RM4 Pro runs about $45 from the official Broadlink Amazon store (check the price on Amazon).
Flash an M5Stack AtomS3 Lite for a DIY proxy
The AtomS3 Lite is a 24 mm square ESP32-S3 module with an IR LED already soldered on, so it becomes an infrared proxy with a dozen lines of YAML and no wiring. It’s transmit only, which covers TVs and most air conditioners, and at about $15 it costs a fraction of a hub, though the XIAO IR Mate bought direct from Seeed is cheaper still.
M5Stack’s docs page only says the board has an IR transmitter LED. The pin is on its pin map image and in the official AtomS3 IR example. Both put it on G4, and that is what our config uses. The full build is in the ESPHome section further down: it compiled in 2 minutes 36 seconds to 39.2% of flash.
Get it if you’re comfortable with ESPHome YAML and want several rooms covered cheaply. Pass on it when you want a receiver or a case that looks finished on a TV stand, since the LED on the Atom points out of one face and you’ll be propping it up. It is about $15 from the official M5Stack Amazon store (check the price on Amazon).
Buy the Athom remote for IR and RF pre-flashed
Athom ships its RF433 IR Remote Controller with ESPHome already on it, and it’s the only pick here that pairs an IR transmitter and receiver with a 433 MHz RF transceiver in one ESPHome device. That makes it the ESPHome answer to the RM4 Pro, local push instead of polling.

Athom lists an ESP32-WROOM-32E, a 38 kHz IR transmitter and receiver, a 433 MHz transceiver, a Bluetooth proxy and USB-C power. Its store showed a sale price near $20 against a $26 regular price when we checked, and it isn’t sold on Amazon US. Whether the stock firmware already exposes ir_rf_proxy entities depends on the build Athom flashes, so plan to adopt it in ESPHome and add the infrared: block yourself.
Right for ESPHome households that also run 433 MHz gear. Wrong for anyone who wants Amazon returns, or who would rather not edit YAML, because the ready-made XIAO IR Mate firmware is the less fiddly start.
Fold IR into your coordinator with the SMLIGHT SLZB-Ultima
The SLZB-Ultima is a Zigbee and Thread coordinator first, with an IR transmitter and receiver on the same board. The SMLIGHT integration exposes both as infrared entities, so a coordinator that sits in the living room for range can double as the blaster for that room. It is local push, and the receiver entity arrived a few releases after the emitter.

We’re linking SMLIGHT’s own page rather than Amazon on purpose. The US listings we found come from a reseller, don’t name the Ultima variant, and don’t mention IR in the title, so you can’t be sure you’re getting the IR board. SMLIGHT doesn’t publish a price on its product page either. If you’re still choosing a coordinator, our Zigbee coordinator guide covers the radio side.
Worth it when you’re buying a coordinator anyway and it can sit near the TV. Not worth it when your coordinator lives in a closet or a rack, because IR needs line of sight and a second blaster then makes the Ultima’s IR pointless.
Pair a Tuya TS1201 Zigbee blaster through ZHA
Zigbee IR blasters are the cheap option, some of them battery powered, and they now reach the infrared entity through ZHA. The quirk inside our Home Assistant build matches ten Tuya TS1201 signatures, including a dedicated ZS06 class, and the ZHA infrared platform defines emitter and receiver entities for them. Zigbee2MQTT supports the same hardware as the Moes UFO-R11 and Tuya ZS06, but out of the box it exposes learned codes as MQTT text rather than Home Assistant infrared entities.
The quirk source also explains the one trade-off you’ll feel. A comment marks the battery TS1201 as a sleepy device that only collects each frame when it next polls its parent, so ZHA allows 60 seconds for a send to finish against 10 seconds for a mains-powered blaster. A battery unit is fine for an air conditioner you set once an evening, and slow for flipping TV inputs.
We aren’t linking a product for this path. Amazon US listings for Zigbee IR blasters in November didn’t name the UFO-R11 or ZS06 model, sell for about $24 to $29, and some are marked as needing a Tuya gateway. Buy one with a return window, pair it to ZHA, and check that the device signature reads _TZ3290 with model TS1201 before you rely on it. Our ZHA vs Zigbee2MQTT comparison helps if you haven’t picked a Zigbee stack yet.
Keep SwitchBot hubs for the SwitchBot app only
SwitchBot hubs are good IR blasters inside the SwitchBot app, but they do not provide an infrared entity, so none of the Home Assistant brand integrations can use them. What you get instead is the SwitchBot Cloud integration: cloud polling, a token and secret from the developer options in the app, and the IR appliances you learned in the app as entities whose state is guessed from the last command.
The Hub 3 adds a display and a dial, and the Hub Mini at about $35 does the IR job without them. The Home Assistant docs list both Hub 2 and Hub 3 as sensor-only devices themselves, while the IR appliances behind any hub still get on/off, and air conditioners get temperature and mode.
Makes sense for homes already running SwitchBot curtains, locks or bots that want their IR remotes in the same app. Avoid it if you want local control or the native brand integrations, which covers most readers of this guide. If a SwitchBot lock is why you run the app, our smart lock guide covers locks that reach Home Assistant locally over Z-Wave, Matter and Zigbee. The Hub 3 runs about $100 (check the price on Amazon).
Build an ESPHome infrared proxy
On the ESPHome side, the job is to declare a remote_transmitter on the pin of the IR LED and point an infrared entity of platform ir_rf_proxy at it. We ran ESPHome and Home Assistant as containers on an Ubuntu 26.04 VM; on Home Assistant OS, the ESPHome Device Builder app does the same two steps with the Validate and Install buttons on the device card. This is the AtomS3 Lite config we built, saved as atoms3-ir-proxy.yaml next to a secrets.yaml holding your Wi-Fi details. Both go in the directory mounted at /config in the ESPHome container, which is ~/hass/esphome in our compose file:
esphome:
name: atoms3-ir-proxy
friendly_name: AtomS3 Lite IR Proxy
esp32:
board: m5stack-atoms3
framework:
type: esp-idf
logger:
api:
ota:
- platform: esphome
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
remote_transmitter:
id: ir_tx
pin: GPIO4
carrier_duty_percent: 50%
infrared:
- platform: ir_rf_proxy
name: IR Proxy Transmitter
id: ir_proxy_tx
remote_transmitter_id: ir_tx
The secrets.yaml beside it needs the two keys the config asks for. These are the placeholder values from our lab, so put your own network in:
wifi_ssid: "lab-ssid"
wifi_password: "lab-password-123"
Validate it before you spend minutes compiling. A clean run prints INFO Configuration is valid! plus a warning that non_blocking isn’t set, which the official XIAO config triggers too and which is safe to ignore:
docker exec esphome esphome config /config/atoms3-ir-proxy.yaml
Then compile it. The first build for a new chip family downloads its toolchain, so expect a few minutes:
time docker exec esphome esphome compile /config/atoms3-ir-proxy.yaml
The tail of our build shows the firmware sizes and the three images ESPHome writes. The factory.bin is the one you write over USB the first time, for example with ESPHome Web in Chrome or Edge, and later updates go over the air:
RAM: [=== ] 30.3% (used 103519 bytes from 341760 bytes)
Flash: [==== ] 39.2% (used 718419 bytes from 1835008 bytes)
INFO Creating factory.bin...
INFO Created: /config/.esphome/build/atoms3-ir-proxy/build/firmware.factory.bin
INFO Created: /config/.esphome/build/atoms3-ir-proxy/build/firmware.ota.bin
INFO Created: /config/.esphome/build/atoms3-ir-proxy/build/firmware.elf
INFO Build Info: config_hash=0x4688ea92 build_time_str=2026-11-11 12:54:52 +0000
INFO Successfully compiled program.
real 2m36.269s
We had no board on the bench, so the build is as far as our lab went on this side. Once the board is flashed and on Wi-Fi, Home Assistant discovers it, and adopting it in the ESPHome integration creates the infrared entity that the brand integrations list.
Error: “Transmitter ‘ir_tx’ must have ‘carrier_duty_percent’ configured with an intermediate value”
An IR LED needs a modulated carrier, so ir_rf_proxy refuses a transmitter whose duty is 0% or 100% unless you mark it as RF with a frequency. We set the XIAO config to 100% to see the exact message, and leaving the line out fails earlier with 'carrier_duty_percent' is a required option for [remote_transmitter]. Put it back to 50% (anything from 30% to 50% is normal) and the config validates.

The same rule runs the other way for RF hardware: a 433 MHz transmitter under the radio_frequency platform must be at 100%, because the RF module does its own modulation.
Point LG Infrared at the emitter
On the Home Assistant side, you add the brand integration and pick the emitter, and that’s the whole handshake. With no blaster attached, we enabled the built-in Home Assistant demo integration (kitchen_sink: in configuration.yaml), which creates a demo device called IR Blaster with a real emitter and receiver entity. A real proxy shows up in the same picker under its own device name.
- Open Settings, then Devices & services, select Add integration and search for
infrared, then choose LG and LG Infrared. - Choose TV (or Air conditioner) as the device type.
- In Infrared emitter, select the emitter entity of the blaster in the same room as the TV, leave Infrared receiver empty unless the blaster has one, and select Submit.

The picker only lists entities in the infrared domain, which is why a SwitchBot hub, or a Zigbee2MQTT blaster with its default MQTT text entities, never appears in it. Pick the IR Blaster emitter and submit:

- 1Infrared emitter
- 2IR Blaster emitter entity
- 3Submit
Home Assistant creates an LG TV device with a media player that reads On, which is an assumed state. It also adds 29 button entities, from Power, Power on and Power off to HDMI 1 through 4, the arrow keys and the number pad. Pressing Power shows up in the activity log of the device straight away:

To confirm the command actually reached the emitter, press a button over the REST API and read the state of the emitter. Run it on the Home Assistant host with TOKEN set to a long-lived access token from your profile’s Security tab. We first used the token from our scripted login, and 30 minutes later every call came back 401: Unauthorized, because those tokens expire. An infrared entity has no on or off state; its state is the timestamp of the last command it sent, so it should match the button press to the millisecond:
curl -s -X POST -H "Authorization: Bearer $TOKEN" -d '{"entity_id": "button.lg_tv_power"}' http://127.0.0.1:8123/api/services/button/press | python3 -m json.tool | grep -E 'entity_id|"state"'
Both the button and infrared.ir_blaster_infrared_emitter changed at 13:09:21.427 UTC, and the emitter reports device_class: emitter:

Settings, Connectivity, Infrared now shows the adapter online. Before any emitter existed the same page read 0/0 devices, and it’s the quickest place to spot a proxy that dropped off Wi-Fi:

A timestamp on the emitter proves Home Assistant sent the code, not that the TV saw it. If the state updates and nothing happens, the problem is in the room: aim, distance, a cabinet door, or sunlight on the TV’s receiver.
Error: “No infrared entities found. Please set up an infrared device first.”
That is what the LG Infrared dialog says before any emitter exists, and Samsung Infrared stops the same way under a different reason key. Over the API, LG aborts with no_infrared_entities and Samsung with no_emitters, which is handy to know if you search logs for one and find the other. Add the integration for the blaster first, check its infrared entity exists, then add the brand.

If your Home Assistant runs in Docker like our lab did, the Home Assistant Docker Compose guide covers the container setup, and the ESPHome container sits next to it on the host network.
Match brand integrations to your appliances
The blaster is only half of it; the brand integration decides what you can control. These are the integrations that build on the infrared entity in our 2026.11 build, grouped by what they drive. Every one of them works with any emitter in the comparison table except SwitchBot:
| Appliance | Integrations on the infrared entity | What you get |
|---|---|---|
| TV | LG Infrared, Samsung Infrared, Philips Infrared | Power, volume and channel control; LG and Samsung add per-button entities |
| Air conditioner | Gree Infrared, LG Infrared, Samsung Infrared | Climate entity; Gree and LG follow the handheld remote through a receiver |
| Audio | Marantz Infrared, Edifier Infrared, Persang Infrared | Amplifier and speaker control, assumed state |
| Lights | OSRAM Infrared, LED Infrared | Light entities for IR-remote bulbs and strip controllers |
| Fans and coolers | Dyson Infrared, SilverCrest Infrared | Fan entities that show the last command sent |
| Bathroom | Alpha Bidet Infrared | Wash, dryer, pressure and temperature controls |
If your appliance is not on that list, the infrared entity cannot help you yet, and a code-learning blaster is still the tool. The Broadlink RM4 Pro covers both cases in one box, which is why it stays on this list even though the ESPHome proxies are the better native fit. For an air conditioner with a temperature sensor built in, our thermostat guide compares the Sensibo-style bridges, and a wall tablet gives the whole household the new TV and AC controls without a phone.


