Home Assistant Button Automation with Zigbee, Presence Sensors and IR Scenes
A Zigbee button is one of the simplest ways to make Home Assistant feel natural. Press once to start a scene, double press to change the room mode, hold to turn everything off. The hard part is not the button itself. The hard part is making the button smart enough to understand whether the room is occupied, which appliance should respond, and whether the command should stay local.
This guide shows how to combine a Zigbee button or switch with LinknLink ZG-808Z, HomeClaw, LinknLink eMotion presence sensors, eRemote HA, and eHome HA. The goal is a button automation that works even when cloud apps are slow, because the logic lives in Home Assistant and the room context comes from local devices.
Why Button Automations Fail in Real Homes
Most button automations fail because they are too literal. A button press turns on a device every time, regardless of room occupancy, time of day, temperature, or current mode. That is why a scene that looks good in a demo becomes annoying at home. A reliable button scene should check context before acting.
Button input
A Zigbee button gives a clean trigger: single press, double press, hold, release, or multi-click.
Room context
Presence, light, temperature, humidity, mode, and time decide whether that trigger should run.
Local output
IR, RF, lights, dashboard cards, and Home Assistant scenes should respond without cloud delay.
Think of the button as an intent signal. It tells the home what the person wants, while Home Assistant decides how to execute it safely.
Recommended LinknLink Stack for Button Scenes
The stack below keeps each job separate. Zigbee handles the physical button and low-power sensors. Presence sensors provide room confidence. IR and RF hubs control appliances that do not speak Home Assistant directly. HomeClaw or another Home Assistant gateway keeps the automation local.
| Layer | Recommended device | Role in button automation | Why it helps |
|---|---|---|---|
| Zigbee input | ZG-808Z | Connects Zigbee buttons, switches, contact sensors, and plugs to Home Assistant. | Keeps low-power button inputs local and visible to Zigbee2MQTT or ZHA. |
| Gateway | HomeClaw | Runs Home Assistant, local logic, dashboards, and private AI planning. | Good fit for no-cloud scenes and local automation orchestration. |
| Presence | eMotion Air, eMotion Pro, eMotion Ultra | Confirms whether a room is occupied before a button scene runs. | Reduces false triggers and makes button presses feel room-aware. |
| IR appliance control | eRemote HA, eMotion Pro, eMotion Ultra | Controls AC, TV, fan, purifier, heater, and other IR appliances. | Turns one button press into appliance scenes without cloud remotes. |
| RF appliance control | eHome HA | Controls compatible RF shades, remotes, switches, doorbells, or legacy RF devices. | Lets Zigbee and RF work together through Home Assistant. |
| Room dashboard | iSG Display Max | Shows manual override buttons, room modes, and device status. | Keeps guests and family members from needing to understand complex automations. |
Choose the Right Presence Sensor for Each Button Scene
A button scene becomes more useful when it knows whether someone is actually in the room. LinknLink gives you several ways to add that context. eMotion Air is flexible for battery placement. eMotion Pro combines mmWave presence with built-in IR for AC and TV style rooms. eMotion Ultra adds 60GHz mmWave sensing, built-in IR, and temperature/humidity data cable support for higher precision room logic.
| Room | Presence choice | Button action | Scene example |
|---|---|---|---|
| Bedroom | eMotion Air or eMotion Ultra | Hold button before sleep. | Turn off overhead light, set AC, close shades, and keep soft night light if presence remains. |
| Living room | eMotion Pro or eMotion Ultra | Single press media mode. | Dim lights, turn on TV through IR, set fan speed, and update dashboard state. |
| Home office | eMotion Air | Double press focus mode. | Turn desk lamp on, disable entertainment scenes, and start presence-based idle timer. |
| Entryway | eMotion Air plus Zigbee contact sensor | Press away mode. | Check no presence, turn off lights, close RF shades, and arm notification logic. |
| Garage or utility room | eMotion Pro plus RF or IR control | Hold emergency override. | Turn on work lights, start fan, and keep controls available on dashboard. |
Blueprint: Single Button, Three Scene Modes
A practical Home Assistant pattern is to map one button to three different scene modes. The button stays simple, while Home Assistant decides the correct output. This keeps the automation understandable for family members and easy to troubleshoot later.
Single press: start the room
If presence is detected, turn on the room scene. If no presence is detected, turn on only a low-power welcome light or do nothing.
Double press: change the mode
Switch from work to relax, bright to movie, or day to night. Use eRemote HA for IR appliances and eHome HA for RF devices when needed.
Hold: shut down safely
Turn off local devices, send IR power commands, close RF shades, and keep a short delay before cutting lights if presence still exists.
Trigger: Zigbee button single press Condition: room presence is active Action: - turn on room lights - set AC mode with eRemote HA or eMotion built-in IR - show "active scene" on the room dashboard Trigger: Zigbee button double press Condition: evening mode is active Action: - dim lights - send TV power through IR - close compatible RF shades through eHome HA Trigger: Zigbee button hold Condition: no presence for 60 seconds OR manual override enabled Action: - turn off scene devices - stop fan or AC if safe - reset room dashboard card
How to Avoid Accidental Button Triggers
Buttons are easy to press accidentally. A good automation should treat every button event as a request, not a guaranteed command. Add a small amount of context before high-impact actions. This is especially important for AC, heaters, curtains, locks, and away mode.
- Use presence as a safety check: if no presence is detected, avoid turning on high-power appliances unless the scene is explicitly an away or arrival scene.
- Use time windows: a bedtime button should behave differently at 10 PM than at 10 AM.
- Use room modes: map the same button to different actions for work, movie, sleep, guest, or away mode.
- Use confirmation for risky actions: require double press or hold for AC, heater, curtain, garage, or away scenes.
- Use dashboard override: show the active scene on iSG Display Max or LinknLink App room cards so people can cancel mistakes quickly.
IR and RF Scene Examples
Many homes still rely on appliances that do not expose clean local APIs. IR and RF are useful because they can bridge those devices into Home Assistant. The key is to keep the button event local, then use IR or RF only as an output layer.
| Scene | Input | Context check | Local output |
|---|---|---|---|
| Movie mode | Zigbee button double press | Living room presence active, evening mode active. | Dim lights, TV power through IR, RF shades closed, dashboard card updated. |
| Sleep mode | Bedside button hold | Bedroom presence active, phone charging or night mode active. | AC sleep temperature through IR, lights off, fan low, curtains closed. |
| Focus mode | Desk button single press | Office presence active and calendar/work mode enabled. | Desk lamp on, purifier/fan adjusted by IR, entertainment scenes blocked. |
| Guest mode | Entry button double press | Guest mode helper enabled. | Only safe lights and dashboard controls; no hidden appliance sequences. |
| Away mode | Exit button hold | No presence after delay and doors closed. | Lights off, compatible RF shades closed, IR appliances off, notification sent. |
Button Naming and Dashboard Design
Button automations become hard to maintain when entity names are vague. Name each button by room, device, and purpose. A good name helps future troubleshooting, dashboard design, and family handoff. Pair the automation with a room dashboard so people can see what happened after pressing the button.
Recommended naming pattern: room_device_action. Examples: living_button_movie_mode, bedside_button_sleep_hold, entry_button_away_hold, office_button_focus_double.
For dashboards, show the current room mode, last button press, presence state, and manual override buttons. The LinknLink App Room Dashboard Guide explains how to organize room cards so button scenes are visible instead of mysterious.
Troubleshooting Checklist
If a button scene behaves unpredictably, troubleshoot from the input layer to the output layer. Do not rewrite all automations first. Confirm the physical event, confirm the Home Assistant state, then confirm the action output.
| Problem | Check first | Likely fix | Related guide |
|---|---|---|---|
| Button press not detected | Zigbee2MQTT or ZHA event log. | Move button closer, check battery, add router device, verify ZG-808Z path. | Zigbee2MQTT troubleshooting with ZG-808Z |
| Scene runs but appliance does nothing | IR or RF command history. | Relearn IR/RF command, check emitter line of sight, confirm eRemote HA or eHome HA entity. | Home Assistant remote control guide |
| Scene runs when room is empty | Presence sensor state and timeout. | Increase absence delay, use eMotion room zones, add occupancy helper. | Best mmWave presence sensors for Home Assistant |
| Scene feels slow | Automation trace and local network path. | Keep logic local, reduce cloud calls, simplify condition chains. | Local control smart home guide |
| Family members forget the button actions | Dashboard labels and room mode cards. | Add LinknLink App room dashboard or iSG Display Max room controls. | LinknLink App Room Dashboard Guide |
Related LinknLink Products
These products are the recommended building blocks for local button scenes, presence-aware automation, IR control, RF control, and dashboards:
- LinknLink ZG-808Z Zigbee 3.0 USB Dongle for Home Assistant
- HomeClaw private AI gateway for Home Assistant
- iSG Display Max smart home hub and dashboard
- eMotion Air battery-powered mmWave presence sensor
- eMotion Pro mmWave presence sensor with built-in IR
- eMotion Ultra 60GHz mmWave presence sensor with IR and temperature humidity cable
- eRemote HA local IR remote hub for Home Assistant MQTT
- eHome HA RF smart hub for Home Assistant MQTT
Related Guides
- Home Assistant Zigbee2MQTT Troubleshooting Guide with ZG-808Z
- Home Assistant Remote Control Guide: IR, RF, MQTT, eRemote HA and eHome HA
- LinknLink App Room Dashboard Guide for Home Assistant Automation
- Recommended mmWave Presence Sensors for Home Assistant in 2026
- eMotion Air vs Pro vs Ultra Home Assistant Presence Sensor Guide
- Best Home Assistant Integrations for Local Smart Homes in 2026
- Raspberry Pi vs HomeClaw Home Assistant Gateway Guide
FAQ
Can a Zigbee button trigger IR scenes in Home Assistant?
Yes. A Zigbee button event can trigger a Home Assistant automation that sends IR commands through eRemote HA, eMotion Pro, or eMotion Ultra, depending on the room and appliance.
Why should presence be part of a button automation?
Presence lets the automation confirm whether someone is actually in the room before running lights, AC, TV, fan, shades, or away-mode scenes.
Which LinknLink device should I use for Zigbee buttons?
Use ZG-808Z as the Zigbee coordinator, then connect it to Home Assistant through Zigbee2MQTT or ZHA depending on your preferred setup.
Can one button control both IR and RF devices?
Yes. Home Assistant can receive one Zigbee button trigger and then run separate local actions through eRemote HA for IR devices and eHome HA for compatible RF devices.
How do I stop accidental button presses from triggering big scenes?
Use double press or hold for high-impact actions, add presence and time checks, and show the active scene on a room dashboard for quick override.
Does this setup require a cloud subscription?
No. The recommended architecture keeps button input, presence context, IR/RF output, and Home Assistant logic local whenever possible.
Build Button Scenes That Understand the Room
Start with ZG-808Z for Zigbee input, use HomeClaw for local Home Assistant logic, add eMotion presence sensors for room context, then route IR and RF control through eRemote HA and eHome HA.