Home Automations Worth Building

Most smart homes stop at the app: you tap a phone to do something a wall switch already did. This guide is about the next step, the automations that run without anyone asking. By the end you will know which triggers to build on, have a handful of automations that earn their place, and know how to design them so the house still works when the automation does not.

It assumes you have a hub or platform running with a few devices paired to it. If you are still choosing gear and getting the first bulb online, the smart home starter guide covers that groundwork. Everything below applies whichever platform you use.

Remote control is not automation

Remote control means you are still the trigger. You open an app, find the room, tap the toggle. That is a slower wall switch with a battery and a login. It earns its place in a few cases: turning something off from bed, checking the garage light, warming the house before you get back. Voice commands are the same thing said out loud.

Automation means the house decides. Something happens in the world, a rule notices, and the right thing occurs without a phone involved. The test is simple: if the automation works, nobody in the house should have to know it exists. They just notice the hall is never dark and the bathroom stops fogging up.

The four things that can start an automation

Every rule has the same shape: when something happens, if some conditions hold, then do these actions. The "when" is the trigger, and there are four kinds.

Time. A clock time, or a solar time like sunset or sunrise with an offset. Solar triggers beat fixed times for anything involving light, because "20 minutes before sunset" stays correct all year while "18:30" is wrong for nine months of it.

Presence. Whether a person, or anyone at all, is home. This comes from phone location, from the phone joining the home network, or from a Bluetooth tag. All three are approximate, which matters later.

Sensor. A physical reading crossing a line: motion detected, a door contact opening, humidity above 65 percent, a power meter dropping under 5 watts. These are your most reliable triggers, because they measure something real rather than inferring intent.

State. Another entity changing: a light turning on, a media player starting, a mode switching from Home to Away. State triggers let automations build on each other.

Conditions are the filter that keeps a good trigger from firing at the wrong moment. Motion in the hallway and the sun is down and nobody has set Guest mode is an automation you will keep.

Automations that earn their keep

Lights that follow the sun

Outside lights and the front hall on at sunset, off at a fixed time or at sunrise. This is the first automation almost everyone builds and it stays one of the best, because it replaces a chore nobody does reliably.

Add an offset. Sunset is when the sun touches the horizon, and it stays light for another 15 to 30 minutes after that. Trigger 20 minutes after sunset outdoors and 20 minutes before for rooms with small windows.

Away mode

One rule, triggered by the last person leaving: lights off, thermostat down a few degrees, a notification if a door is unlocked. The reverse runs when the first person comes home. Build it on "nobody home" rather than on one person, or you will turn the heating off on whoever is still in the house. Add a delay of five to ten minutes; presence detection drifts, and the delay absorbs false departures.

Humidity-triggered extractor fan

This one is better than a human. A humidity sensor in the bathroom, a switched fan, and a rule: when humidity rises more than 10 points above the reading elsewhere in the house, run the fan; when it comes back down, stop. Comparing against another room beats a fixed threshold, because 70 percent is normal in a damp August and alarming in January. Add a maximum runtime of 30 minutes, so a stuck sensor cannot leave the fan running for a week.

Laundry-done notification

A smart plug that reports power draw, sitting between the wall and the washing machine. The rule: when power stays below a few watts for five continuous minutes after having been above 20 watts, send a phone notification.

The two numbers are the trick. The threshold has to sit above the machine's standby draw, and the five minute window stops a pause in the spin cycle from reading as the end; watch one cycle and pick the numbers from that. This is the class of automation that suits an alert: something finished, and only a person can act on it. Resist wiring alerts to everything else, because an alert you learn to ignore is worse than none.

A morning routine

On weekdays at your alarm time, bring the bedroom light up over ten minutes, set the heating to the daytime target, turn the kitchen lights on low. Keep it to lights and heating; automations that make noise or start appliances get vetoed within days. Condition it on someone being home, so it does not run through a week you are away.

Design for the moment it fails

Every automation can break. The internet drops, a hub reboots, a firmware update renames a device, a battery dies in a sensor you forgot existed. What matters is what the house does when that happens.

Failure should land in the safe state. A dead automation should leave the lights working and the heating running. Prefer a rule that turns something on over one that has to keep running to keep something on.

Anything with a safety role gets a hardware fallback. Heating keeps a sane schedule on the thermostat itself, not only in your hub. Locks still open with a key. Smoke and water alarms are alarms in their own right, with the smart part as an extra notification.

Run the rules you rely on locally. An automation executing on a hub in your hallway keeps working when the connection drops. One that round-trips through a vendor's cloud does not, and it stops the day that service changes. Cloud suits remote access and notifications, and makes a poor foundation for your hallway lights.

One cheap habit catches most of this: once a quarter, check which devices last reported. A flat battery does not announce itself. The sensor quietly stops triggering, and you assume the automation was never that good.

Keep the wall switch working

The fastest way to make a household hate a smart home is to break the switches. A smart bulb needs power at the socket to stay reachable, so someone flipping the switch leaves it dark and unreachable, and the automation cannot fix it either.

Two clean ways out. Put the intelligence in the wall, with a smart switch or an in-wall module behind the existing one, so the switch still cuts the light and reports the change to the hub. Or keep smart bulbs permanently powered and replace the switch with a battery-powered control that sends a command instead of cutting the circuit.

Either way, hold to three things. Every light needs a physical control that works with the hub off, and it belongs where people already reach. Manual action wins: if someone turns a light on by hand, skip the rule for a while afterwards. And tell the people you live with what you built, because an automation nobody understands reads as a fault.

Local, cloud and what leaves the house

Devices vary a lot in how much they send outside your walls, and the box does not tell you. Zigbee, Z-Wave and Thread talk to a hub in your house, and Matter allows local control across brands, though a product may still lean on its vendor's cloud for parts of what it does. A cloud-first device sends every event to a vendor server and takes every command back, so your sensor history is a log on someone else's machine and your light switch depends on that company continuing to run the service.

A few decisions cost little and help a lot. Prefer devices that work with a local hub, and check before buying whether they still function with the internet unplugged. Know what your cameras and microphones record, where it is stored and who can see it, and keep them out of bedrooms and bathrooms. Put smart devices on their own network segment or guest network if your router supports it. Use unique passwords and two-factor authentication on any account that can unlock a door or view a camera. Tell guests what is listening. The question worth asking of any device: what stops working, and what keeps a record, if you unplug the router for a day?

Where to go next

• Smart home basics for choosing a hub, pairing devices and the groundwork this post builds on.
• Smart home tutorials for more walkthroughs on sensors, hubs and routines.
• Home repairs for the wiring and switch work behind in-wall modules.

Stuck on a step, or does an automation fire at the wrong moment and you cannot see why? Write to the desk and describe the trigger and the conditions you set.