RF devices are still common in real homes: ceiling fans, motorized shades, garage doors, fireplaces, projection screens, outlets, and older remotes that still work well. The smart home problem is not that these devices are useless. The problem is that they often sit outside Home Assistant.
This guide gives Home Assistant users a practical RF automation checklist for eHome HA. It is not another product comparison. It focuses on what to check before you add RF devices, how to plan commands, and how to combine RF actions with presence sensors, IR control, and local Home Assistant scenes.
Why RF Automation Needs a Checklist
RF automation feels simple when a remote has only one button. In a real room, it becomes more subtle. A ceiling fan may have separate commands for speed, power, light, and direction. A motorized shade may use open, close, stop, and favorite-position controls. A garage or gate remote may require extra caution because the action affects access and safety.
That is why the right first step is not "learn every button." The right first step is to decide which commands belong in Home Assistant and which commands should remain manual. eHome HA is useful when the RF device should participate in a scene or routine, but every RF command should still have a clear purpose.
Start With the RF Device Inventory
Walk through the home and list RF-controlled devices room by room. For each device, write down what the original remote controls and whether the action is safe to automate. This inventory prevents a common mistake: adding commands because they exist, not because they improve the room.
| Device | Useful Home Assistant actions | Automation caution |
|---|---|---|
| Ceiling fan | Power, speed, light toggle | Keep manual override; avoid rapid repeated commands |
| Motorized shades | Open, close, stop, privacy scene | Confirm travel direction and stop behavior before scheduling |
| Projection screen | Down, up, media-room scene | Coordinate with projector and lighting timing |
| Garage or gate remote | Status-aware manual trigger only | Do not automate access without extra safety checks |
Confirm Frequency and Command Behavior
Before you build automations, confirm that the device is a suitable RF-control target for your region and setup. Many household remotes use common RF ranges, but not every remote protocol behaves the same way. Some commands are simple one-shot actions. Others toggle state, which means Home Assistant may not know whether the device is currently on or off.
Toggle commands need special care. If the same RF command turns a fan on and off, an automation can accidentally reverse the intended state. For toggle-only devices, use Home Assistant helpers to track the last intended state, and keep the routine conservative. For safety-sensitive devices, prefer manual confirmation instead of fully automatic triggers.
eHome HA is best used as the RF action layer. Home Assistant should still own the logic: time, room mode, presence, weather, sunlight, and manual override.
Design Commands Before Scenes
Build a clean command set before creating scenes. A good naming structure saves time later and makes dashboards easier to maintain. Use names that describe the outcome, not only the remote button.
- Living room fan on is clearer than Remote button 1.
- Bedroom shade close is clearer than Shade down RF.
- Media screen down is clearer than Screen command A.
After each command is added, test it from the same location where eHome HA will stay. RF range and direction can matter. A command that works on the desk may behave differently after the hub is moved behind a cabinet or near metal objects.
Pair RF Actions With Room Context
RF control becomes more valuable when it responds to room context. A fan can turn on only when the room is occupied and warm. Shades can close when sunlight is strong and the room is active. A projection screen can lower as part of a media scene only when someone starts the scene manually.
This is where presence sensors and Home Assistant make the RF hub smarter. A basic RF remote can send a command. A Home Assistant routine can decide whether that command should run now.
| Context signal | RF action | Recommended LinknLink path |
|---|---|---|
| Room occupied + warm temperature | Turn on fan or increase speed | eHome HA + presence sensor |
| Afternoon sunlight | Close compatible RF shades | eHome HA + Home Assistant schedule or sunlight rule |
| Movie scene started | Lower projection screen | eHome HA + eRemote HA for projector or AC IR |
| Room vacant for a long delay | Turn off fan or close scene | eHome HA + eMotion Air, eMotion Pro, or eMotion Ultra |
Use RF and IR for Different Jobs
RF and IR are often discussed together because both use remote-style control, but they solve different appliance problems. RF is common for fans, shades, screens, gates, some outlets, and certain legacy devices. IR is common for TVs, AC units, projectors, media gear, and some fans.
For Home Assistant users, the clean setup is to separate the layers. Use eHome HA for RF actions. Use eRemote HA for IR actions. Use a presence sensor or an iSG gateway to provide context and local automation logic. This avoids making one device responsible for every room behavior.
If the same room needs both RF and IR, build one Home Assistant scene that calls both layers. For example, a media room scene can close RF shades with eHome HA, lower a projection screen, turn on the projector through eRemote HA, and keep lights active while presence is detected.
Safety and Manual Override Rules
RF automation should be helpful, not surprising. Keep manual override rules visible in Home Assistant and avoid automating access-control devices without extra checks. A fan speed change is low risk. A gate, garage door, or moving shade requires more care.
- Do not trigger gates or garage doors from simple time schedules.
- Keep access-related RF actions behind a manual dashboard button or confirmation step.
- Add delays between repeated RF commands so the appliance has time to respond.
- Use helpers to track intended state when the original remote only has a toggle button.
- Document each command so future users know what it controls.
Where This Fits in the LinknLink Stack
Use this guide after reading the RF remote hub comparison guide. That page helps choose a hub. This checklist helps turn eHome HA into reliable Home Assistant routines.
If the room also needs IR, compare the Best IR Blasters for Home Assistant guide and the eRemote HA product page. If the room needs occupancy context, start with the best mmWave presence sensor guide.
FAQ
Can Home Assistant control RF remotes?
Yes. Home Assistant can trigger RF actions when a compatible RF hub exposes learned commands or MQTT-friendly actions that Home Assistant can call in automations.
What is eHome HA best for?
eHome HA is best for bringing compatible RF-controlled devices such as fans, shades, screens, and remote-style appliances into Home Assistant scenes and local routines.
Should RF commands run automatically?
Low-risk comfort commands can be automated with delays and overrides. Access-related actions such as gates or garage-style controls should use manual confirmation or extra safety checks.
Do I need eRemote HA if I already use eHome HA?
Use eRemote HA when the room has IR appliances such as TVs, AC units, projectors, or media equipment. Use eHome HA for compatible RF devices. Many rooms benefit from both layers.
Which presence sensor should I pair with eHome HA?
Use eMotion Air when battery placement matters, eMotion Pro when a room also benefits from IR and light sensing, and eMotion Ultra when higher precision 60GHz presence detection is needed.
Conclusion
RF automation works best when it is treated as a room-control layer, not a pile of remote buttons. Start with a device inventory, confirm command behavior, name each action clearly, and let Home Assistant decide when RF actions should run. With eHome HA, eRemote HA, and presence sensors working together, older RF devices can become part of a local smart home without replacing hardware that still works.