An energy-saving automation should reduce waste without weakening the alarm, hiding a real alert, unlocking an entry, or switching off equipment that must remain available. This 2026 checklist turns lights, thermostats, plugs, locks, cameras, alarm modes, and occupancy rules into testable operating routes.
The goal is not to automate every device. It is to give each rule one owner, one trigger, one permitted action, one safe fallback, and one rollback method. Treat security and life-safety controls as protected loads. If a routine cannot fail safely, keep that action manual.
Smart-home energy and security at a glance
| Automation area | Energy goal | Security boundary | Acceptance evidence |
|---|---|---|---|
| Lights | Reduce empty-room runtime | Keep safe exits, arrival lighting, and useful presence cues | Trigger time, off delay, manual override, outage behavior |
| Thermostat | Use a safe setback when the property is empty | Protect people, pets, pipes, medicines, batteries, and equipment | Upper and lower limits, recovery time, sensor fallback |
| Smart plugs | Remove avoidable standby or scheduled loads | Never cut routers, alarm hubs, sirens, locks, safety devices, or needed chargers | Approved-load list, wattage check, restoration state |
| Locks and doors | Avoid heating or cooling an open property | Do not make energy rules unlock, close, or obstruct an exit | Direct sensor test, lock state, alert owner, manual recovery |
| Cameras | Limit unnecessary recording or processing where appropriate | Keep required evidence, privacy, and incident coverage | Mode table, clip test, export, power and internet failures |
| Away mode | Set back approved loads when the last person leaves | Prove occupancy, arming, alerts, and return behavior separately | Last-person and first-person tests plus false-away recovery |
1. Separate the energy goal from the security goal
Write the energy problem in plain terms: an empty room remains lit, heating runs after the property is vacant, a nonessential load stays on overnight, or cameras record where privacy rules call for a different mode. Then write the security job beside it: preserve an exit path, detect an opening, keep the alarm online, retain evidence, or notify a named person.
Do not accept “save power” or “make the house safer” as a specification. Record the current runtime or schedule, the proposed rule, the protected devices, who may override it, the expected restoration state, and the evidence needed to approve it. A small operating sheet prevents an energy routine from acquiring hidden security authority.
- Name the room, device, circuit, account, and automation platform.
- Name the trigger: schedule, direct contact sensor, occupancy sensor, alarm mode, geofence, tariff period, weather condition, or manual command.
- Name the exact action and maximum delay.
- Name every state in which the rule must not run.
- Name the person who receives a failure alert and can disable the rule.
2. Inventory devices, loads, and dependencies
Create one table for the alarm hub, router, modem, access points, cameras, doorbells, locks, keypads, sirens, sensors, thermostats, smart plugs, lights, voice assistants, bridges, battery chargers, and monitoring communications. Record power source, backup duration where applicable, network path, account owner, automation platform, shared users, and recovery method.
Mark dependencies that are easy to miss. A Wi-Fi camera may depend on a router, access point, internet service, vendor account, and phone notification path. A lock may use batteries but depend on a bridge for remote status. A thermostat may use a room sensor that can be moved or lose connection. Use the smart-home security network segmentation guide to separate network design from device-control rules.
Assign each load one of three classes:
- Protected: alarm hubs, smoke and carbon-monoxide devices, routers needed for alerts, sirens, locks, medical or accessibility equipment, sump or freeze protection, and any device required by the property safety plan.
- Conditional: cameras, doorbells, displays, exterior lights, thermostats, dehumidifiers, and chargers whose safe state depends on occupancy, weather, privacy, or response policy.
- Eligible: nonessential lamps, entertainment devices, decorative loads, and other equipment the owner has inspected and approved for automated shutdown.
3. Use lighting rules that fail safely
Room lights are a good starting point because their result is visible and usually reversible. Begin with an off delay after verified vacancy, not a complicated chain. Test the sensor from the doorway, desk, sofa, floor, and quiet seated position. A motion sensor that cannot see a person reading should not switch off the only safe light.
Keep arrival lighting, stairs, exits, garages, exterior paths, and alarm-response routes separate from ordinary room rules. Define minimum light levels and a manual override that remains available if the app, cloud service, voice assistant, or internet connection fails. Label the physical control so a guest or responder does not have to guess.
Presence simulation can make a vacant property look occupied, but it is not proof of occupancy and does not replace locks, direct opening sensors, alarm modes, or response. Vary only approved lights and times. Do not expose a predictable daily pattern, illuminate private rooms for no reason, or let a simulation suppress the actual away mode.
4. Put hard safety limits around thermostat setbacks
A thermostat setback is acceptable only inside the property’s safe temperature and humidity range. Record people, pets, plants, pipes, medicines, batteries, electronics, instruments, food storage, and moisture risks before choosing limits. Use local guidance and equipment instructions where needed; this checklist does not set a universal temperature.
Do not let a geofence or alarm mode override freeze protection, high-heat protection, ventilation needed for health, or a manually declared occupied state. If a remote room sensor drives the rule, test loss of that sensor. Record whether the thermostat falls back to its own sensor, holds the last setting, or stops following the schedule.
- Test the away setback and the return recovery time.
- Test a door or window left open, but do not automate a lock or closure to solve it.
- Test internet loss and vendor-service loss.
- Test a low-battery or unavailable room sensor.
- Test a manual override and confirm when automation resumes.
- Record upper and lower limits that no routine may cross.
5. Keep protected equipment off smart plugs
A smart plug is a switch, not a safety controller. Never place the alarm hub, router needed for alerts, siren, smart-lock bridge, smoke or carbon-monoxide device, emergency light, accessibility equipment, medical equipment, sump pump, freeze-protection device, or required battery charger behind a routine that can remove power.
For an eligible load, confirm voltage, current, starting load, heat, ventilation, appliance instructions, and whether remote switching is permitted. Record the device state after a power cut and after power returns. Some equipment stays off, some returns to its last state, and some starts immediately. Each result changes the failure plan.
Use one plug per documented load where practical. Give it a specific name such as “office lamp west,” not “plug 3.” Do not use a broad “all plugs off” action. Keep security and network equipment in a protected group that energy scenes cannot address.
6. Keep locks, doors, and garages outside energy authority
An open door can waste heating or cooling, but an energy rule should not unlock a door, close a garage door without direct safety checks, or create an obstacle in an exit route. Use a direct door or window contact to notify the named operator. Let that person inspect and choose the safe response.
Run the smart-lock auto-lock checklist separately. Prove door alignment, direct closed state, latch engagement, inside exit, temporary credentials, low-battery warning, emergency power, and lockout recovery. A thermostat alert must not be treated as proof that the door is safe to lock.
For garages, record the exact door position source and the person who receives a long-open alert. Do not infer “closed” from motor runtime. Test obstruction protection and the manufacturer’s approved controls. Energy savings do not justify an unattended closing action that has not passed its own safety test.
7. Define camera modes by security and privacy need
Camera power, recording, detection, and notifications are four separate functions. A home mode may reduce interior recording for privacy while keeping an entry camera active. An away mode may enable more detection. Write the table by exact camera, location, account, household role, legal boundary, and incident need.
Do not switch off the only camera needed to verify an alarm, capture a package area, document a forced entry, or protect a remote property merely to reduce a small load. First measure the real energy use and decide whether privacy, bandwidth, storage, alert volume, or power is the actual problem.
Use the security camera privacy guide to set recording boundaries. Test a permitted event in every approved mode: alert arrival, clip start, subject visibility, timestamp, playback, retention, download, and lawful sharing. Then test power loss, internet loss, storage full, account removal, and restoration.
8. Make occupancy and alarm states explicit
Do not use one phone’s location as the sole proof that a property is empty. Phones can be left behind, lose permission, disable background updates, report an old location, or travel with someone who is not the last occupant. Pets, guests, cleaners, carers, and contractors also break simple geofence assumptions.
Define occupied, temporarily empty, away, sleep, guest, service visit, and vacation states. Record who may declare each state and which system is authoritative. If an alarm mode triggers energy changes, the alarm action must complete and report independently. A failed thermostat or lighting command must not block arming.
Use the HomeKit away-mode checklist when Apple Home participates. Test the last-person departure, a person without location permission, a phone left at home, a guest remaining inside, a return through each approved door, and a false-away correction.
9. Write safe rule order and conflict handling
List every automation that can touch the same device. A scheduled setback, a tariff rule, an away scene, a window-open rule, a manual hold, and a weather response can issue conflicting commands. Record priority and expiry. The operator should know why a device changed and which rule will act next.
Prefer small rules with one clear result. Avoid long scenes that arm the alarm, lock doors, switch cameras, change temperature, cut plugs, and turn off lights in one opaque action. Break them into observable stages. Security actions should report success or failure even if an energy action is unavailable.
- Manual safety override beats an energy schedule.
- Life-safety and equipment-protection limits beat savings targets.
- Direct door and window state beats inferred occupancy.
- A declared guest or service-visit state beats geofence departure.
- An incident state freezes nonessential automation changes until closeout.
10. Test internet, power, battery, and service failures
Document what runs locally and what requires the internet or a vendor service. Turn off the test network through an approved method, not by cutting power to the alarm stack. Confirm alarm control, local schedules, physical switches, thermostat safety limits, lock operation, camera recording, alerts, and restoration.
Use the internet-outage test log to capture timestamps and outcomes. Then run the battery maintenance checklist for sensors, locks, cameras, remotes, and backup supplies. Record who receives low-battery alerts and how long replacement takes.
After power returns, verify every protected device before enabling ordinary automations. Check the router, alarm hub, communications, siren, lock bridge, cameras, thermostat, sensors, time settings, schedules, and smart-plug states. A routine that silently resumes in the wrong mode has failed restoration.
11. Assign alerts and operating ownership
Every actionable alert needs a primary owner, backup owner, response time, escalation route, and closeout record. Separate energy alerts from security alerts so a room-light message cannot hide an alarm, failed lock, offline hub, camera outage, or low battery.
Use specific wording: “garage side door open for 10 minutes while away” is better than “device warning.” Include property, device, state, time, and safe next action without exposing a PIN or recovery secret. Test notifications on an invited household phone using cellular data and normal quiet modes.
For changes during an incident, start a home-security incident timeline. Record who changed the automation, why, what the prior state was, what evidence was preserved, and when ordinary rules resumed.
12. Review tariffs, seasons, and household changes
Seasonal temperature, daylight, school schedules, travel, guests, pets, work patterns, utility tariffs, and equipment changes can make an approved rule unsafe or wasteful. Set a quarterly review and an extra review after any move, renovation, router change, alarm change, new lock, new camera, new pet, or account-role change.
Do not copy a utility price event directly into security controls. A tariff window may move an approved appliance schedule, but it must not cut protected equipment, remove needed lighting, defeat a camera evidence route, or exceed thermostat safety limits.
Keep an export of the approved automation inventory and screenshots of rule names, triggers, actions, exceptions, and owners. Do not store master codes, recovery codes, or private video in the operating sheet.
Run a 60-minute smart-home energy and security acceptance test
- Minutes 0–8: verify the inventory, protected-load list, account owners, physical controls, and rollback method.
- Minutes 8–16: test one occupied room and one empty room lighting rule, including still occupancy and manual override.
- Minutes 16–24: test thermostat setback, hard limits, open-contact notification, and manual hold.
- Minutes 24–31: test each approved smart plug, power-return state, naming, and protected-group exclusion.
- Minutes 31–38: test direct door state, lock state, garage alert, and confirm no energy rule has lock authority.
- Minutes 38–45: test camera mode, alert, recording, playback, export, and privacy boundary.
- Minutes 45–52: test last-person departure, guest remaining, false-away recovery, and first-person return.
- Minutes 52–57: test internet loss or service unavailability through the approved test route.
- Minutes 57–60: restore normal mode, verify protected devices, close alerts, save evidence, and assign corrections.
Smart-home energy and security scorecard
| Control | Pass evidence | Owner | Retest date |
|---|---|---|---|
| Protected loads | No energy rule can switch them off | System owner | After any wiring or plug change |
| Lighting | Occupancy, delay, exit light, and manual override pass | Household lead | Seasonally |
| Thermostat | Limits, fallback, return, and manual hold pass | Property lead | Before hot and cold seasons |
| Entry | Direct state, alerts, locks, and safe exit pass | Security owner | After lock or sensor change |
| Cameras | Mode, privacy, evidence, outage, and export pass | Camera owner | Quarterly |
| Occupancy | Last person, guest, false-away, and return pass | Automation owner | After role or phone change |
| Restoration | Protected devices recover before ordinary rules resume | Backup operator | Quarterly |
Do not approve the automation until these blockers are cleared
- A protected device can be switched off by an energy rule or broad scene.
- A thermostat rule can exceed a documented safety limit.
- A single phone location is treated as proof the property is empty.
- An energy routine can unlock a door or close a garage without its own approved safety test.
- A camera needed for alarm verification or evidence is disabled without an equivalent route.
- A security action waits for an unrelated energy action to succeed.
- No physical override works during an internet or service outage.
- Alerts have no named owner or are buried among routine energy messages.
- Conflicting rules have no priority, expiry, or visible explanation.
- Rollback has not been tested and documented.
Smart-home energy-saving automation FAQ
Should an away scene switch off every smart plug?
No. Keep alarm, network, lock, life-safety, medical, accessibility, protection, and required charging equipment outside broad shutdown actions. Approve eligible loads individually.
Can a geofence prove nobody is home?
No. Phones can be left behind, lose permission, or travel while another person remains. Combine declared household states with direct device tests and a guest or service-visit override.
Should an open window automatically turn off heating or cooling?
A direct contact can support an alert or approved setback, but define safety limits, delay, manual override, and restoration. Do not let the rule lock or close an opening.
Can cameras be turned off to save energy?
Only after measuring the benefit and documenting privacy, alarm verification, evidence, and incident needs. Test each exact camera mode, recording route, outage behavior, and return state.
What should happen after a power or internet outage?
Protected devices should recover and be verified first. Then check alarm communications, locks, cameras, thermostat limits, sensors, schedules, and smart-plug states before ordinary automations resume.
