Every remote in the house, absorbed: native IR/RF in Home Assistant

The ceiling fan, the fireplace, the LED strip, the 'dumb' TV in the guest room — an entire class of devices speaks only infrared or RF, and until recently automating them meant cloud gadgets or awkward hacks. Home Assistant's 2026 releases added native IR/RF support: learn a remote's codes once, and those devices become first-class local entities. This is the project guide: the hardware paths, the learning workflow, and the automations that make it feel like magic.

Published Nov 18, 2026

What 'native' changes

Infrared and RF control existed before via integrations and MQTT bridges; the 2026 change (HA 2026.4's RF groundwork, 2026.5's infrared framework, ESPHome's matching proxy support) is that codes are now a first-class Home Assistant concept: learned commands attach to devices as entities you can call from automations, dashboards and voice, learned and stored locally. A learned remote stops being a file of hex you babysit and becomes 'the fan, but smart.' Combined with ESPHome hardware, the whole loop — learn, store, transmit — can live on a $10 board in the room where the device is.

Pick a blaster/RF path→Learn the codes→Codes become entities→Place transmitters→Automate the dumb stuff

Hardware paths

The learning workflow

  1. Set up the transmitter device in ESPHome/HA first and confirm it appears with its learn capability.
  2. Enter learn mode, point the original remote, press one button. Name the code immediately and semantically — 'Fan speed 2,' not 'code_0x3F' — because in six months the names ARE the documentation.
  3. Learn the full remote in one sitting, including the boring buttons. Partial remotes are how projects stall at 80%.
  4. Test each learned command from Home Assistant before building automations on top; a code learned through a dying remote battery is a haunting, not a bug.
  5. Build the device wrapper: group the commands into the entity shape the device deserves (a fan with speeds, a media player with power/volume) so dashboards and voice see a fan, not twelve buttons.

Automations that justify the project

Honest limits

IR is one-way: Home Assistant can command the TV but cannot ask if it is on — state is inferred, and a human with the physical remote can desync it (power-tracking smart plugs are the classic patch for state). Rolling-code RF (some garage and security devices) refuses to be learned, by design. And code libraries vary by brand — budget ten patient minutes per remote. Within those limits, this is the highest delight-per-dollar project in the 2026 Home Assistant catalog: the house's last analog holdouts, joining the system.

Official documentation and references

Frequently asked questions

Can Home Assistant learn any remote?

Infrared remotes, broadly yes. RF depends on frequency and encoding — fixed-code 433 MHz devices are the easy wins via CC1101; rolling-code systems (designed to resist copying) will not learn, and should not.

How does the TV's state stay in sync if IR is one-way?

It is inferred from commands sent, and physical-remote use can desync it. The common fixes: route all control through HA (voice/dashboards), or add a power-monitoring plug so HA can see actual draw and correct its assumption.

What hardware should a beginner buy?

A Broadlink RM4-class device for zero soldering, or an ESP32 + IR transceiver kit if you enjoy ESPHome. For RF fans, the ESP32 + CC1101 combo is the community standard — see our ESPHome chapter for the platform basics.

Related guides