Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.
Most smart home marketing shows a color bulb responding to a voice command, but a reliable automation is a chain of four things: a trigger, a set of conditions, an action, and a defined failure behavior. This practical guide to Home Assistant automations covers the mechanics; the examples here show that chain running on real hardware.
The typical listicle gives you dozens of ideas with no implementation detail. This article takes the opposite approach: fewer automations, each with the exact devices, the exact condition logic, the protocol path, and what happens if the internet goes down. You will see presence-based lighting with the Aqara FP2, motion-triggered hall lights with Philips Hue, occupancy-aware climate with ecobee, entry lighting from a Schlage lock, laundry detection with Eve Energy over Matter, and multi-protocol orchestration on Home Assistant Green.
It is written for DIY smart-home users who want local control, privacy, and automations that survive a router reboot — not just demos built for a screenshot.
The Four-Part Test for Any Automation
A useful automation is not an idea. It is a concrete chain:
- Trigger — what changes. A presence zone becomes occupied, a lock changes state, a power draw rises above a threshold.
- Conditions — state constraints that make the action appropriate. Room illuminance below a threshold, house mode set to Home, time after sunset.
- Action — the command. Turn on a scene, resume a comfort profile, send a notification.
- Failure behavior — what happens when a sensor drops, the hub restarts, or the internet is unavailable.
The examples below apply all four parts. If an automation cannot answer the fourth part, it is still a prototype.
Local Control Is Not the Same as Cloud Independence
A common marketing shortcut is to call any Matter or Zigbee setup "cloud-free." The useful distinction is narrower: local control means commands and state stay on your LAN; cloud independence means no vendor account or server is required to run the routine. A device can be locally controlled after setup but still require a manufacturer account for commissioning, configuration, or remote access.
| Architecture | Routine control | Setup/configuration | Remote access |
|---|---|---|---|
| Hue Bridge + Zigbee | Local | Hue app / Bridge | Internet/cloud for remote |
| Home Assistant + Zigbee/Z-Wave | Local | Local Home Assistant UI | Optional |
| Home Assistant + Matter | Local | Matter commissioning; vendor app may precede it | Optional / platform-dependent |
| Aqara FP2 → Home Assistant | Local after configured | Aqara app needed for zone setup/editing | Vendor-dependent |
| ecobee native | Thermostat itself continues HVAC locally | ecobee account / cloud ecosystem | Cloud |
| Schlage Encode Plus | Keypad / local ecosystem paths remain | Schlage / Apple configuration | Schlage Wi-Fi service for remote features |
For a deeper protocol breakdown, see Zigbee vs Z-Wave vs Matter and what Matter actually changes.
Example 1: Presence-Based Lighting with Aqara FP2
A PIR motion sensor answers one question: did something move? For a desk, sofa, or reading chair, that is the wrong question. The Aqara Presence Sensor FP2 uses 60–64 GHz mmWave radar to keep reporting an occupied zone even when you sit still. It exposes up to 30 configurable zones across 320 grid cells and covers roughly 40 m² / 430 sq ft. It is USB-C powered at 5 V / 1 A, carries an IPX5 rating, and includes an ambient-light sensor. No Aqara hub is required for the HomeKit-controller path into Home Assistant, but the Aqara app is still needed to create and edit zones.
Automation logic
- Trigger: desk zone changes from clear to occupied.
- Conditions: room illuminance below a chosen threshold; house mode = Home; optional after-sunset window.
- Actions: activate a working-light scene over the desk while leaving the rest of the room unchanged.
- Exit behavior: turn those lights off only after the desk zone has been clear for 60–120 seconds.
- Refinement: create separate sofa, desk, and doorway zones so walking through does not start the same scene as sitting down.
Local path and privacy
After initial zone configuration, FP2 can expose zones locally to Home Assistant through HomeKit Controller. The same physical room can then trigger different scenes depending on where presence is detected — something a single PIR event cannot do. Radar sees position and presence without a camera, which is materially less invasive than vision-based occupancy.
The dominant real-world issue is placement. Ghost presence, zone spillover, and slow absence detection usually improve after changing mounting height, angle, or repositioning the sensor away from heat and airflow.
Example 2: Motion-Triggered Hallway Lighting with Philips Hue
Corridors, stairs, closets, and bathrooms need fast movement detection, not sustained presence. The Philips Hue Motion Sensor is an indoor PIR sensor powered by two AAA batteries, rated IP42 for 0–40 °C, and communicates over Zigbee and Bluetooth. Hue specifies a minimum two-year battery life and a two-year warranty. Full automation requires a Hue Bridge; without one, basic behavior is limited.
Automation logic
- Trigger: motion changes to detected.
- Conditions: ambient light below a threshold; optional time window from 23:00 to 06:00.
- Action: after dark, set hallway lights to a low warm scene instead of full brightness.
- Clear behavior: after several minutes without motion, fade the lights off.
Local path
The motion-to-light chain is Zigbee through the Bridge and does not depend on internet access. Remote Hue access and some third-party cloud functions are separate. This is a mature, predictable automation where most "missed" actions are actually explained by a forgotten illuminance condition, timeout, or cooldown.
For a still-occupied office or sofa, this PIR sensor is the wrong tool — use mmWave presence in those spaces and keep PIR for transitions.
Example 3: Whole-Home Goodnight Scene on a Hue Bridge V2
The Hue Bridge V2 is an Ethernet-connected Zigbee lighting hub supporting up to 50 Hue lights and 12 accessories. It draws around 0.1 W in standby and about 3 W maximum. Hue Zigbee devices keep working if internet or Wi-Fi service is unavailable because the Bridge handles local Zigbee communication. It also exposes Hue devices to Matter, alongside native Apple Home, Alexa, Google, and SmartThings integrations.
Automation logic
- Trigger: fixed bedtime, a smart button, phone bedtime mode, or a Home Assistant household state.
- Conditions: at least one household member home; optionally suppress if guest mode is enabled.
- Actions: turn off kitchen and living room; dim the hallway for several minutes; set bedroom lights warm and low; then turn the hall off.
- Beginner path: configure entirely in the Hue app with rooms, zones, and scenes.
- Advanced path: Home Assistant combines the Hue scene with non-Hue thermostat, lock, and smart-plug actions.
Local path and integration depth
Hue's native Bridge-to-light path remains local. Remote control requires internet. The Home Assistant native Hue integration can expose richer Hue-specific capabilities than the Bridge's Matter representation alone; Matter bridges often expose fewer manufacturer-specific features than native integrations, and Hue is a documented example.
Example 4: Climate Follows Occupancy with ecobee Smart Thermostat Premium
The ecobee Smart Thermostat Premium is model EB-STATE6-01 with a 4.09 × 4.09 × 1.02 in body and a 4-inch 540×540 display. It reads temperature, humidity, proximity, and radar occupancy, includes built-in indoor-air-quality monitoring, and ships with a remote SmartSensor. It uses dual-band Wi-Fi, Bluetooth 5, and 915 MHz communication with ecobee room sensors. HomeKit, Alexa, Google, and SmartThings ecosystems are supported.
Automation logic
- Trigger: occupancy switches from Away to Home, or the included SmartSensor begins reporting an occupied room.
- Conditions: active comfort profile; current room temperature outside the desired range; optional door/window state.
- Actions: use the occupied-room temperature rather than only the thermostat's hallway temperature; resume the comfort profile; delay aggressive heating or cooling until occupancy persists.
- Advanced Home Assistant variant: combine local occupancy/door sensors with thermostat state so the HVAC is not conditioned around a temporarily open exterior door.
Local path and cloud split
Basic thermostat and HVAC operation remains functional at the wall during service outages. Remote ecobee app access, account-based services, and historical reporting depend on ecobee infrastructure. Community reports from ecobee outages consistently show the physical thermostat continuing to control HVAC while app/server access fails — exactly the difference between "the device still works" and "all smart features still work."
Home IQ reporting is part of ecobee's connected service. Some separate Smart Security functions can require a subscription; normal thermostat operation does not. Temperature, occupancy, and air-quality data are more intimate household signals than a light-switch state, so the cloud reporting path matters.
For a full model comparison, see Ecobee Essential vs Enhanced vs Premium and the broader best smart thermostats guide.
Example 5: Entry Lighting from a Smart Lock Without Auto-Unlocking
The Schlage Encode Plus Smart WiFi Deadbolt, model BE499WB CEN 622, has built-in 2.4 GHz Wi-Fi plus Bluetooth, Apple Home and Home Key support for tap-to-unlock, and Alexa/Google Assistant support. It stores up to 100 access codes, runs on four AA batteries, retains a physical key fallback, and carries BHMA AAA ratings plus Commercial Grade 1 classification. Basic remote/app operation does not require a separate Wi-Fi bridge.
Automation logic
- Trigger: front door changes from locked to unlocked, or a recognized household access event occurs.
- Conditions: after sunset; alarm mode is not Away; optionally check whether somebody is already home.
- Actions: switch entry and hall lights to a low welcome scene and restore occupied climate mode.
- Security rule: do not automatically unlock doors solely from generic phone presence or geofence. Arrival presence is appropriate for lighting and climate, but it is a weak sole authorization factor for entry.
Local path and privacy
Local physical keypad/key entry and Apple Home access do not require the same cloud path as Schlage app remote management. Schlage remote app, lock history, and notifications use the Wi-Fi/cloud ecosystem. Smart-lock logs reveal entry/exit patterns and code usage, so use unique codes rather than one shared household PIN and treat access credentials differently from ordinary automation-state data.
For lock selection and local integration, see the Schlage smart lock guide and Home Assistant compatible smart locks.
Example 6: Laundry-Finished Notifications with Eve Energy over Matter
The Eve Energy (Matter) US/Canada model 20EBU4101 is rated for 120 V and up to 15 A / 1,800 W. It uses Matter-over-Thread, requires a Matter controller and a compatible Thread Border Router for Thread operation, and measures power and energy usage. It measures roughly 70 × 39 × 60 mm. Eve emphasizes no Eve cloud or account requirement for core operation.
Automation logic
- Trigger: power rises above an "active" threshold and later falls below a small idle threshold for several minutes.
- Conditions: the cycle has previously been detected as active; suppress duplicate notifications.
- Action: notify the household "Laundry finished."
- Optional action: after a long idle period, switch off a safe standby appliance. Never use automation to interrupt equipment whose power must remain available.
Local path and Matter complexity
Matter command and state exchange occurs locally through the Matter controller, and Thread routes IP packets locally through the border router. Home Assistant labels its Matter integration Local Push. Energy data can reveal occupancy patterns and appliance usage, so local storage and control are meaningful beyond latency.
Matter-over-Thread reliability depends on more than the plug: Thread border-router topology, IPv6, multicast/mDNS behavior, and controller software all matter. VLANs, network filtering, and multicast configuration can interfere with discovery and operation. If Thread devices drop offline after controller or network updates, check the border-router and network layer before blaming the endpoint.
For setup details, see the Home Assistant Matter integration guide.
Example 7: Cross-Brand Local Orchestration with Home Assistant Green
The Home Assistant Green is the official Nabu Casa turnkey appliance. It runs a Rockchip RK3566 quad-core ARM Cortex-A55 up to 1.8 GHz, 4 GB LPDDR4X RAM, and 32 GB eMMC storage. It includes Gigabit Ethernet, two USB 2.0 ports, HDMI for diagnostics, and microSD support for recovery. Typical power use is around 1.7 W idle and 3 W under load, and it is fanless. Home Assistant OS is preinstalled. Zigbee, Thread, and Z-Wave radios are not built into Green; USB or network coordinators are added as required.
Automation logic
- Trigger: Aqara FP2 desk presence.
- Conditions: light level low, house occupied, ecobee not in Away.
- Actions: Hue task lights on; after prolonged absence, return lights to off; allow energy-monitoring state to generate notifications.
- Advanced: one automation can consume Zigbee entities via ZHA, Matter entities locally, Hue Bridge entities through native Hue integration, and Z-Wave entities via Z-Wave JS.
Local path and data ownership
The automation engine, dashboards, database, and supported local-device integrations remain on Green. Home Assistant Cloud is optional rather than mandatory; users can configure other remote-access approaches. The architectural advantage is that you choose which integrations send data outside the network, rather than making cloud connectivity the default requirement.
For a full review, see Home Assistant Green: Full Review & Setup Guide or start at the beginner's guide.
The Radios That Make Local Multi-Protocol Work
A Home Assistant Green alone cannot speak Zigbee or Z-Wave. Two official coordinators fill that gap.
Home Assistant Connect ZBT-2
The ZBT-2 is the second-generation official Zigbee/Thread adapter, using a Silicon Labs MG24 radio SoC with an ESP32-S3 USB bridge. It supports Zigbee 3.0 or Thread, but the same unit is dedicated to one role at a time. It uses USB-C at 5 V / 500 mA, covers 2,400–2,483.5 MHz with a peak antenna gain of 4.16 dBi, and runs a 460,800 baud interface versus 115,200 on the first-generation ZBT-1. It replaces the discontinued ZBT-1/SkyConnect.
Example automation
- Devices: Home Assistant Green + ZBT-2 dedicated to Zigbee + Zigbee bulbs and sensors.
- Trigger: Zigbee motion, contact, or temperature entity changes.
- Conditions: household mode plus time/lux or other local states.
- Actions: control any Home Assistant entity, including compatible Zigbee bulbs paired directly to ZHA.
- Local path: the Zigbee network and automation stay local.
The biggest repeated misunderstanding is expecting one ZBT-2 to handle Zigbee and Thread concurrently. It does not. A mixed Zigbee + Matter-over-Thread home needs separate radios or border routers planned before migrating devices.
Home Assistant Connect ZWA-2
The ZWA-2 is the second-generation official Z-Wave adapter. It uses a Silicon Labs ZG23 800-series Z-Wave SoC plus an ESP32-S3 USB controller and supports conventional Z-Wave and Z-Wave Long Range simultaneously. North American mesh channels include 908.42/916 MHz, with Long Range channels around 912/920 MHz. Peak antenna gain is approximately 3.38 dBi in the North American configuration. It uses USB-C at 5 V / 1 A, and Z-Wave JS is the Home Assistant software stack.
Example automation
- Devices: Home Assistant Green + ZWA-2.
- Trigger: Z-Wave contact, motion, switch, or other entity event.
- Conditions and actions can simultaneously reference Matter, Zigbee, Hue, and other Home Assistant entities.
- Local path: Z-Wave radio, Z-Wave JS, and the automation engine are local.
Home Assistant recommends direct USB for the ZWA-2 because the adapter-to-Z-Wave-JS link is latency-sensitive. If remote placement is required, a remote Z-Wave-JS host is a better design than tunneling latency-sensitive serial traffic.
For the full coordinator landscape, see Best Zigbee Coordinators & Dongles for Home Assistant.
How to Test an Automation's Failure Behavior
A real automation design should survive three tests before you trust it.
- Unplug the internet while leaving the LAN and router alive. Hue Bridge-to-bulb commands, Home Assistant local automations, and Matter local control should continue. ecobee remote app and Schlage remote features will stop, but the physical thermostat and local keypad should keep working.
- Restart the hub or controller. Automations should resume from stored state. Watch for devices that fail to come back online, especially Matter-over-Thread endpoints that may require recommissioning after controller or network changes.
- Make one sensor unavailable. Your conditions and exit logic should leave a safe state — lights should not stay stuck on indefinitely, and security actions should fall back to a known manual path.
If an automation passes all three tests, it is no longer a marketing demo.
Rules That Keep Automations Boring and Reliable
These principles sit underneath every reliable setup above.
- Motion is not presence. PIR answers "did something move?"; mmWave can continue detecting a still person. Corridors use PIR. Desks, sofas, and reading chairs use presence.
- State-aware beats trigger-aware. Add conditions like "only after sunset," "only if someone is home," and "only if heating is actually needed."
- Use hysteresis. Turn on fast, turn off conservatively. A 30–120 second clear delay prevents lights from shutting off during momentary sensor gaps.
- Keep manual controls working. A visitor should be able to operate lights, locks, and thermostat without knowing the app.
- Energy monitoring should change behavior. A live wattage chart is telemetry. Cycle-complete detection, standby-load identification, and suppressing energy-intensive actions when nobody is home are automations.
- Security automations deserve stricter rules than lighting. Presence may turn lights on; it should not grant entry by itself. Access actions need authentication, auditability, and a robust fallback state.
Frequently Asked Questions
Q: Is a smart home automation the same as a scene or routine?
A scene is a predefined state — a set of lights at certain brightness and color. An automation is a trigger plus conditions that applies a scene or runs an action. A routine can be either, but reliable automations also define what happens when a sensor drops or the network fails.
Q: Do I need internet for local automations?
No. Hue Bridge-to-bulb commands, Home Assistant local automations, and Matter local control all run on your LAN. Internet is typically only needed for initial setup, remote access, or vendor cloud features. However, some devices still require a manufacturer account before you can commission them into Matter.
Q: Is Matter the same thing as cloud-free?
No. Matter mandates local IP control between a Matter controller and device, but manufacturers can still put a vendor-account step in front of Matter commissioning. Native integrations can also expose more advanced features than a Matter bridge representation, so "Matter" and "fully cloud-independent" are not synonyms.
Q: Can one ZBT-2 handle Zigbee and Thread at the same time?
No. The ZBT-2 supports Zigbee 3.0 or Thread, but it is dedicated to one coordinator role at a time. If your home needs both, you need another Thread Border Router or a separate coordinator.
Q: Which sensor should I use for a desk where I sit still?
Use a mmWave presence sensor such as the Aqara FP2, not a PIR motion sensor. PIR only detects movement, so it will report the room as clear while you sit still. For maximum reliability, combine PIR for fast response with mmWave for sustained occupancy.
Q: Do I need Home Assistant, or is a Hue Bridge enough?
For lighting-only automations, a Hue Bridge is sufficient and simpler. Home Assistant becomes worth it when you want one automation to combine Hue lighting with a thermostat, lock, energy monitor, or devices from multiple vendors — and when you want the logic engine itself to stay local and under your control.
Conclusion
The difference between a marketing demo and a dependable smart home is failure behavior. PIR detection is not the same as presence, local control is not the same as cloud independence, and Matter does not replace Zigbee or Z-Wave. The examples in this guide all share the same skeleton: a specific trigger, state-aware conditions, a concrete action, and a defined response when something goes wrong.
If you are building a single-vendor lighting system, a Hue Bridge plus Hue motion and presence devices is the most predictable place to start. If you want one local logic engine across Hue, Matter, Zigbee, and Z-Wave, Home Assistant Green with a dedicated ZBT-2 or ZWA-2 coordinator is the stronger long-term foundation.
Start with the beginner's path to Home Assistant, then dig into the protocol comparison, Matter explained, and the full automation guide.