A smart home is not smart because of how many devices it contains, but because of the quality of the automations that connect them. A good automation goes unnoticed: the hallway light comes on at night at low brightness and switches itself off. A bad automation is noticed immediately, because it turns the light off while someone is still in the room or starts the sprinklers in the rain.
The basic structure: triggers, conditions, actions
Almost every home automation platform uses the same three-part pattern.
- Trigger: what starts the automation. A sensor detects motion, a door opens, a certain time arrives, the phone leaves an area.
- Conditions: checks that must be true for the automation to continue. Is it dark? Is anyone home? Is it a weekday?
- Actions: what gets done. Turn on a light, send a notification, close a shutter.
The most common mistake is confusing triggers and conditions. "When it gets dark" is not a good trigger for turning on the bathroom light: the trigger is motion, darkness is the condition.
An example written in readable form:
when: the hallway motion sensor detects presence
if: illuminance is below 20 lux
and the time is between 23:00 and 06:30
then: turn the hallway light on at 15%
turn it off after 2 minutes without motion
Designing for the unexpected
What happens if a sensor stops working?
Batteries run down, networks drop, devices disconnect. A robust automation accounts for these cases. If the light turns off "after two minutes without motion" and the sensor goes offline, the light might stay on forever. A maximum safety timeout, for example thirty minutes, avoids the problem.
What if the automation fires twice?
Many sensors send several events in quick succession. If the action is "send a notification", you risk a burst of messages. Platforms let you choose the execution mode: ignore new triggers while the automation is running, restart it or queue it. For a switch-off timer, "restart" is almost always the right mode.
Does it work without the internet?
Critical automations, such as night lights, flood alarms or heating, should run locally. If they depend on a manufacturer's cloud, a line outage makes them useless exactly when they are needed.
Always leave manual control
One rule I consider non-negotiable: every automation must be easy to override for whoever is at home. The wall switch must keep working, and a manual command must take priority.
Some useful techniques:
- if someone turns a light on manually, suspend for an hour the automation that would turn it off;
- provide a "guest" or "holiday" mode that disables automations tied to daily habits;
- avoid irreversible or annoying actions without confirmation, such as opening the gate automatically.
Presence sensors: motion is not presence
Passive infrared motion sensors detect movement, not people sitting still. Someone reading motionless on the sofa for ten minutes is treated as absent and ends up in the dark. There are several solutions:
- lengthen the switch-off delay in rooms where people sit still;
- combine several signals, such as motion, a closed door and the TV being on;
- use millimetre-wave presence sensors, which also detect micro-movements such as breathing.
Use cases that work well
| Situation | Trigger | Condition | Action |
|---|---|---|---|
| night light | motion | dark, night | low light with auto-off |
| water leak | flood sensor | none | notification and shut-off valve |
| leaving home | last phone leaves the area | nobody home | lights off, notify open windows |
| open window | window contact | heating on | turn off the room thermostat |
| irrigation | time of day | no rain forecast | start the cycle |
Document and review
After a few months there are dozens of automations and nobody remembers why a light comes on at seven. Clear names, a short description and a periodic look at the execution history show what works and what does not. The more advanced platforms display a trace of each run, with the exact point where a condition blocked the action: it is the best debugging tool there is.
In short
- Every automation consists of triggers, conditions and actions: do not confuse the first with the second.
- Safety timeouts and the right execution mode prevent lights left on forever and floods of notifications.
- Critical automations must run locally, without depending on the cloud.
- Manual control must always take priority over automatic control.
- Clear names and reviewing the history keep the system understandable months later.
