Know the Difference Between “Comfort” and “Critical” Functions Before You Automate Anything
Hi everyone,
after a few years of building out my own smart home (Aqara sensors, Zigbee, Home Assistant, and more), I want to share one planning principle that I wish someone had told me on day one. It’s simple, but it will save you a lot of frustration — and possibly some very dark hallways.
The core idea: Not all automations are equal
Before you automate anything, ask yourself one question:
“What happens if my smart home hub is offline?”
Hubs crash. Updates fail. Wi-Fi routers reboot. Cloud services have outages. Power flickers. It’s not a question of if, but when. Based on the answer, every function in your home falls into one of two categories:
- Critical functions
Things that must always work, even when the hub, network, or cloud is down. Examples:
Hallway and staircase lighting (motion → light on)
Bathroom light
Light switches in general — a wall switch must always turn the light on
Door access
Heating basics
If your family has to use a phone app or wait for a cloud round-trip just to get light in the hallway at 2 a.m., your smart home has failed its most basic job. And nothing kills family acceptance (“WAF”) faster than that. - Comfort functions
Things that are nice to have, but nobody suffers if they stop for a day:
“Movie mode” scenes
Colored ambient lighting
Notifications (“washing machine finished”)
Voice announcements
Presence-based multi-condition logic (“only at night, only if TV is off, only if…”)
These can happily live in your hub/central logic (Home Assistant, Aqara Hub automations, etc.), because a temporary failure is annoying at worst.
How to make critical functions hub-independent
The key technique is direct binding (also called direct association or Zigbee binding). This links a sensor or switch directly to the actuator, device-to-device. The command never touches the hub — so it works even when the hub is powered off.
Practical options:
Zigbee direct binding: Bind an Aqara motion sensor or wireless switch directly to a Zigbee light/relay. Many Aqara devices support this, and coordinators like Zigbee2MQTT or the Aqara hubs let you configure bindings. Once bound, the devices talk peer-to-peer.
Decoupled mode done right: Aqara wall switches (e.g., H1/H2 series) can run in “decoupled” mode so the button triggers automations instead of the relay. Great for comfort logic — but think twice before decoupling a critical light. If you do decouple it, add a fallback (see below).
Keep the physical wiring functional: Use smart relays/switches that still switch the load physically. A smart bulb behind a dumb switch that someone turned off is unreachable; a smart switch controlling a dumb bulb keeps working as a normal switch no matter what.
Local, not cloud: If a function can’t be direct-bound, at least keep the automation local (on the hub itself, not in the cloud). Local automation survives an internet outage; cloud automation does not.
A simple planning workflow for beginners
List every function you want to automate.
Label each one “critical” or “comfort”. Rule of thumb: if it involves basic lighting, safety, or access — it’s critical.
Critical → design for hub failure first. Direct binding, physical switching preserved, local-only logic. The fancy conditions come second, if at all.
Comfort → go wild. This is where the hub, scenes, and complex logic shine.
Test it: Unplug your hub for an evening. Can you still live normally in your house? If yes, you planned well.
TL;DR
Ask “what breaks when the hub is down?” for every automation.
Critical functions (hallway light!) → direct binding / physical fallback / local-only.
Comfort functions → hub logic is fine.
Test by actually pulling the plug on your hub.
Your smart home should degrade gracefully into a normal home — never into a broken one.
Curious how others handle this — do you use direct bindings, or do you rely fully on your hub? Any Aqara-specific binding tips for beginners are welcome below!