Home Assistant RF Proxy: Turn Old Remote Controls Into Smart Home Devices

This article contains affiliate links. We may earn a commission from qualifying purchases.

Some content on this site is AI-assisted and reviewed by our editorial team.

Home Assistant’s 2026.5 release added native RF proxy support — meaning those old remote-controlled blinds, fans, and garage doors you thought were “dumb” can now join your smart home automations. No cloud, no replacements, no new hardware to buy (beyond a $15 transceiver).

The Problem: Millions of RF Devices Left Behind

If you have motorized blinds, a ceiling fan with a remote, RF-controlled outlets, or a wireless doorbell, you’ve probably noticed something frustrating: these devices work fine with their included remotes, but they’re invisible to your smart home. Apple Home, Google Home, Amazon Alexa — none of them can see a 433 MHz radio signal.

The result? People either live with “dumb” remotes for perfectly good hardware, or they throw away working devices and buy Wi-Fi/Zigbee/Matter replacements. The Open Home Foundation put it bluntly in a recent editorial: “the most sustainable smart home device is the one you already own.”

Home Assistant’s May 2026.5 release takes that seriously. It introduced a native RF entity platform that brings sub-gigahertz RF devices into full smart home automations — no cloud account, no new device purchase, no replacement hardware.

How the RF Proxy Architecture Works

The key design decision in Home Assistant 2026.5 is decoupling: the RF transmitter hardware and the device-specific logic are completely separate components that communicate through a shared platform interface.

Here’s what that means in practice:

1. A transmitter entity — either an ESPHome microcontroller with a CC1101 transceiver chip, or a Broadlink RM4 Pro hub — registers itself in Home Assistant as a radio frequency transmitter.
2. A consumer integration for a specific device (e.g., “Somfy blinds,” “Hampton Bay fan,” “generic RF outlet”) pulls encoded RF command sequences from an external protocol library.
3. The consumer integration routes those commands through whichever transmitter entity you select during setup.

The benefit of this separation: when a new RF device integration is added to Home Assistant, it automatically works with every existing compatible transmitter. No reconfiguration needed. And a single ESPHome proxy anywhere on your local network can serve as the radio relay for every RF-controlled device in your home simultaneously — blinds in the living room, a fan in the bedroom, a garage door at the far end of the house.

What Hardware You Actually Need

You have two options for the transmitter:

Option 1: ESPHome + CC1101 Transceiver (~ dollars 15)

The cheapest path. You need:

• An ESP32 or ESP8266 microcontroller (~$5)
• A CC1101 sub-gigahertz transceiver module (~$8–$10)
• Some jumper wires and a USB power source

Flash the ESP32 with ESPHome firmware, configure it as an RF transmitter entity, and it registers with Home Assistant over your local network. Total cost: under $15. No subscription, no cloud.

The CC1101 chip covers the common sub-GHz bands: 315 MHz (common in North America for garage doors and older outlets), 433 MHz (universal — most RF blinds, fans, and European devices), 868 MHz (European smart home devices), and 915 MHz (North American IoT).

Option 2: Broadlink RM4 Pro (~ dollars 70)

If you don’t want to solder anything, the Broadlink RM4 Pro is a ready-made RF + IR transmitter. It supports both 433 MHz and 315 MHz RF, plus infrared for TV/AC control. Home Assistant has a native Broadlink integration.

The trade-off: the Broadlink requires its cloud for initial setup (though after that it works locally), and it doesn’t support 868/915 MHz. For most North American homes with 433 MHz devices, it’s fine.

What Devices Can You Control?

The RF platform in Home Assistant 2026.5 supports any device with a known protocol in the rf-protocols library. Common supported categories:

• Motorized blinds and shades: Somfy, Rollease, and many generic RF blinds
• Ceiling fans: Hampton Bay, Harbor Breeze, and most fans with RF remotes
• RF outlets: Etekcity, GE, and generic 433 MHz outlet remotes
• Garage door openers: Older Chamberlain/Liftmaster models (pre-myQ)
• Wireless doorbells: Most 433 MHz doorbell buttons
• Wireless wall switches: Many battery-powered remote switches

If your device came with a remote and you can find its protocol in the rf-protocols library (or capture the signal with an SDR), it can join your smart home.

3 Automations That Make This Worth It

1. Blinds That Follow the Sun

If you have RF-controlled blinds, you can now automate them based on sun position:

• Close west-facing blinds when the sun angle exceeds 30° in summer (reduces AC load)
• Open all blinds at sunrise, close at sunset
• Close blinds in the room where a movie is playing (triggered by TV power state)

2. Fan Schedules That Actually Make Sense

Most RF ceiling fans have three speed settings and a reverse switch — all on the remote. With Home Assistant RF proxy:

• Set fan to medium when bedroom temperature exceeds 75°F
• Turn fan off when you leave home (presence detection)
• Run fan on low overnight with a 2-hour auto-off timer

3. Garage Door in Automations

Older garage door openers that predate Chamberlain’s myQ subscription wall can now participate:

• Auto-close after 15 minutes if left open and no one is home
• Trigger porch lights when garage door opens after dark
• Notify phone if door opens unexpectedly

Capturing Unknown RF Signals

What if your device isn’t in the rf-protocols library? Home Assistant supports signal capture:

1. Put the RF transmitter into “learn” mode in Home Assistant
2. Press the button on your existing remote
3. Home Assistant captures the raw RF signal and stores it as a command
4. Assign that command to a button entity or automation

This works for most fixed-code RF devices. Rolling code devices (like some modern garage door openers) are more complex and may require an SDR (software-defined radio) for capture, but the majority of consumer RF remotes use fixed codes.

Recommended Hardware for RF Proxy

• ESP32 Development Board (for ESPHome) →
• CC1101 Sub-1GHz Transceiver Module →
• Broadlink RM4 Pro (no-solder alternative) →
• Home Assistant Green (plug-and-play HA server) →

The Bottom Line

Home Assistant’s RF proxy architecture is a quiet but significant upgrade. It takes a category of devices that smart home platforms have ignored for a decade — older RF remotes, blinds, fans, outlets — and brings them into full automation without requiring you to replace anything.

If you’ve been living with “dumb” remotes for hardware that still works perfectly, this is the update that lets you keep it. Spend $15 on an ESP32 and CC1101, spend an afternoon setting it up, and every RF device in your house becomes a smart home entity.

The most sustainable smart home device is the one you already own. Home Assistant just made that true.

Do you have RF-controlled devices you’ve been wanting to smartify? What’s your setup?

nn

My take: The RF proxy is Home Assistant at its best — a $15 transceiver pulls your existing blinds, fans, and garage remotes into real automations instead of a landfill. If you’ve got RF gear collecting dust on a shelf of remotes, this release is the reason to finally install it.

Related guides

• Ring Intercom: Smart Home Security for Apartment Renters
• Smart Home Fire Safety: Smoke Detectors, CO Monitors, and Kitchen Automations That Prevent Disasters
• Matter Smart Home: 7 Devices That Work With Every Platform (2026 Guide)
• Smart Home Bathroom: 7 Upgrades That Make Sense
• How to Know the Mail Arrived Without the 50 Dollar Bridge