Describe the outcome in one sentence
Begin with a household outcome: “Light the hallway gently when someone walks through after dark.” That sentence is easier to test than “make the home smarter.” Separate the trigger, conditions and action. Motion is the trigger; darkness and a household quiet-hours setting are conditions; a low brightness level is the action. Add an explicit way to pause or override the routine. If you cannot explain the behaviour to another resident, reduce the number of dependencies before adding more devices.
Choose where the logic lives
A routine may run in a device, a local controller or a cloud service. That location affects what happens during a network or internet outage. Home Assistant, Apple Home, Google Home, Amazon Alexa and vendor apps have different execution paths depending on the integration and devices involved. Do not assume every automation in one platform is local. Check the particular trigger and action, then test the actual installation. Keep essential heating schedules in a supported thermostat or heating controller rather than relying entirely on an unrelated service.
Begin with reversible actions
Lighting is often a sensible first experiment because a mistaken brightness level is usually easy to correct. Start in one room and avoid busy sequences that change several systems at once. A smart plug can control an appropriate lamp, but it should not be used to interrupt a refrigerator, medical device or heating appliance simply because a routine editor allows it. Electrical ratings, inrush loads and manufacturer restrictions still apply. Software flexibility does not make an unsuitable load safe.
Routine pattern: a hallway that respects quiet hours
Trigger: motion detected. Conditions: after sunset, quiet mode active, no manual pause. Action: set a supported low brightness. Exit: switch off after a suitable vacancy period, with a wall control available throughout. Test for people moving slowly and for pets.
Routine pattern: a window reminder before heating
Trigger: a window remains open. Conditions: heating is scheduled and the sensor is reporting normally. Action: show a reminder or request a manufacturer-supported temporary adjustment. Exit: restore the normal schedule when appropriate. Preserve frost protection and never cut boiler power through a generic plug.
Routine pattern: an explicit away mode
Trigger: a household member deliberately selects away. Conditions: check for remaining occupants and essential loads. Action: turn off nonessential lights and request a supported thermostat setback. Exit: a clearly labelled home control. Phone location alone should not determine safety-sensitive actions.
Resolve conflicts before they become mysteries
Two routines can compete over the same device. A motion rule may turn a lamp on while a bedtime scene turns it off. Define priority and duration: a manual choice might pause automatic changes until the next morning, for example. Avoid loops in which one device's state triggers another rule that reverses the first. Use readable names, record who owns each automation and disable old experiments. When troubleshooting, inspect event history and change one rule at a time rather than rewriting the whole system.
Build an energy baseline
Power, measured in watts, describes a rate at a moment. Energy, often measured in kilowatt-hours, accumulates over time. A steady 100-watt load running for ten hours uses one kilowatt-hour. That arithmetic does not mean a real appliance has a constant load: heaters cycle, refrigerators start and stop, and electronics change behaviour. Compare totals over a useful period and make sure your monitor measures the value you want rather than estimating it from an on/off state.
Plug-level monitors cover only the connected appliance. Whole-home monitors may require professional installation and can have measurement limitations of their own. Do not open an electrical panel to install equipment unless you are qualified and authorised to do so. Match plug monitors to the load and consult their accuracy specifications. Export data if the service supports it, label gaps clearly and distinguish a true zero from an offline device. A missing reading is not evidence that the appliance stopped consuming energy.
Put thermostat changes in context
Heating use depends on weather, building fabric, occupancy, ventilation and the heating system as well as the thermostat setting. Record those factors before comparing weeks. Avoid promising a fixed saving from a single automation. Different systems respond differently to setbacks, and heat pumps may need a different strategy from other heating arrangements. Follow the installer and manufacturer's guidance, preserve safe minimum temperatures and make comfort complaints part of the review rather than treating them as inconvenient data.
Test failures, then simplify
Once a routine works, test what happens after a controller restart, a sensor battery warning or an unavailable cloud service. Do this safely and avoid disabling alarms or essential equipment. Confirm that the household can still operate the home manually. Keep a brief recovery note with device names and the location of controls, but store pairing codes and passwords separately. Review routines when schedules, residents or devices change. If the measured benefit is small and the maintenance burden is high, retiring the automation is a successful decision too.