Home Assistant adds native RF support

Radio frequency is one of the oldest weird corners of the smart home. A lot of cheap remotes, blinds, fans, outlets, and garage accessories use it, but they were never really “smart” in the modern Home Assistant sense. They just blasted out simple sub-GHz commands and hoped the right thing heard them. Home Assistant 2026.5, released on May 6, changes that by adding a native RF platform to the core product — which is a bigger deal than it sounds. (home-assistant.io) ### What kind of RF are we talking about? This is not Wi‑Fi, Bluetooth, Zigbee, or Thread. It’s the older radio-frequency gear that often lives around 433 MHz or nearby sub-GHz bands — the stuff behind bargain-bin remotes, motorized blinds, RF outlets, some doorbells, and a lot of “dumb but wireless” home gadgets. Home Assistant’s own release notes frame it as a way to bring a huge device category into the platform natively. (home-assistant.io) ### What actually changed in 2026.5? Home Assistant added a new Radio Frequency integration, but the important detail is that it works as a platform other integrations can use. Basically, Home Assistant now has an official abstraction for an RF transmitter. You don’t add every gadget by hand at the radio layer. Instead, device-specific integrations can tell that transmitter wha(home-assistant.io)ssistant added in 2026.4. (howtogeek.com) ### Why does that matter? Because the old way was messy. If you wanted RF control, you were usually mixing custom components, vendor apps, bridge boxes, or one-off hardware projects. Some of that still works, and some setups will still need tinkering, but native support means the official product now understan(howtogeek.com)ing around. (howtogeek.com) ### What works first? Right now, the first device-specific integrations called out are Honeywell String Lights and Novy cooker hoods. So this is not “every RF device now works.” It’s the foundation plus a couple of concrete examples. But that foundation is the interesting part — once the RF transmitter exists as a first-class entity, more integrations can target it. (howtogeek.com) ### What hardware do you need? At launch, Home Assistant highlights two transmitter paths. One is ESPHome paired with compatible sub-GHz transmitter hardware. The other is the Broadlink RM4 Pro, specifically the Pro model, because the rest of the RM4 line does not include RF support. That means the new feature is native in software, but it still needs physical radio hardware in your setup. (howtogeek.com) ### Does this mean sensors and car fobs too? Not automatically. Sending RF commands is the easy half. Reading random RF devices reliably is harder, and secure devices like car remotes or many garage openers often use rolling codes specifically to stop replay attacks. So the big win here is control of simple tr(howtogeek.com)and from Home Assistant’s launch examples. (howtogeek.com) ### Why now? Home Assistant has been on a run of pulling “legacy” protocols into the main product. April 2026 added native infrared. May adds radio frequency. The pattern is pretty clear — absorb the weird edge cases that used to require community workarounds, then let official integrations build on top. For a platform built around local control and long-lived hardware, that’s exactly the right direction. (home-assistant.io) ### Bottom line This release does not instantly make every RF gadget smart. But it gives Home Assistant an official RF layer, and that is the part that matters. Once the plumbing is native, the ecosystem can move a lot faster. (home-assistant.io)