An automation system needs maintenance in the same way a pool or an air conditioner does: small, regular attention prevents most problems, and good records make the rest easier to fix. This guide covers what to maintain, how to handle updates and backups, what to document, who should own the accounts, and how to troubleshoot and recover when something stops working.
What does routine maintenance include?
Routine maintenance covers software, power, people, and records. The table below is a starting point; the right schedule depends on the system and how the property is used.
| Task | Suggested rhythm | Why it matters |
|---|---|---|
| Review offline or unavailable devices | Monthly | Catches weak signals and dead batteries before an automation fails |
| Check low-battery warnings and replace batteries | Monthly, and before long absences | Locks, sensors, and remotes stop working without warning when batteries run out |
| Apply app and device updates | As released, or on a set schedule for the hub | Security fixes and bug fixes; some updates change behavior |
| Confirm backups ran and can be found | Monthly | A backup that doesn’t exist or can’t be decrypted won’t help |
| Review users, codes, and app access | Quarterly, and after any staff or tenant change | Removes people who no longer need access |
| Test key automations and alerts | A few times a year | Confirms notifications still arrive after app or account changes |
| Check UPS status and battery age | A few times a year | UPS batteries wear out and may not carry the load during an outage |
| Clean outdoor camera lenses and check mounts | A few times a year, more often near the coast | Salt film, humidity, and insects blur images |
| Pre-season review | Before hurricane season (which starts June 1) | Confirms remote access, alerts, and backup power before storms |
Illustrative example: An owner of a Key Largo second home has a short checklist that a property manager runs before each arrival: confirm every device is online, replace any lock or sensor battery under 30 percent, test the leak alerts, and check that the thermostat schedule matches the arrival date. Problems found on that visit are fixed before the family arrives.
How should updates be handled?
Install security updates promptly, and turn on automatic updates where they’re available. CISA’s guidance is direct about it: don’t dismiss update alerts, install all updates, and turn on automatic updates. For phones, apps, routers, and most device firmware, that’s the right default.
The central hub or controller deserves a little more care, because one update there can affect many devices and automations at once. Our practice for hubs and controllers:
- Read the release notes for breaking changes, especially to integrations you use.
- Make a fresh backup and confirm it completed.
- Update when someone can check the system afterward, not right before leaving a second home empty or right before a storm.
- Test the key automations and alerts after the update.
- Note the version and date in the system’s documentation.
Firmware updates on battery devices can take longer and use extra battery. If a lock or sensor is already low, replace its batteries first.
What should be backed up, and where?
Back up anything that would take hours to rebuild: the hub or controller configuration, automations, device settings, and the router’s configuration. Store at least one copy off the device itself, and ideally one off-site.
Home Assistant’s documentation is a good example of what a sound backup setup looks like. It describes automatic backups on a schedule, with a recommended setup of daily backups that keep the last three. Backups are encrypted by default, and restoring one requires the encryption key from the emergency kit that Home Assistant has you download during setup. The documentation recommends keeping a copy on another system outside Home Assistant, and ideally also one off-site. Other platforms have their own tools, but the same principles apply.
Points that are easy to miss:
- Save the key with the plan, not with the backup. An encrypted backup is useless without its key. Store the key in a password manager or another secure place separate from the backup files.
- Radio networks matter. Zigbee and Z-Wave devices are paired to a specific hub or coordinator. Check whether your platform’s backup includes that network information, because restoring it can save re-pairing every device by hand.
- Router settings. Address reservations, network names, and separate networks for smart devices take time to recreate. Export the router’s configuration where the model supports it, or document the settings.
- Test a restore occasionally. Restoring to spare hardware is the safest way to confirm a backup actually works.
What happens when a vendor or app changes?
Apps get redesigned, features move into subscriptions, cloud services shut down, and older devices lose support. These changes are outside the owner’s control, but their impact can be reduced with planning.
- Know your cloud dependencies. Keep a short list of which devices and automations need a vendor’s cloud to work. Our article on local control vs. cloud automation explains how to tell.
- Prefer equipment with local options for functions you can’t live without, such as locks, lighting, and leak shutoff, where the platform and device allow it.
- Watch for end-of-support notices. When a manufacturer stops updating a device, plan its replacement. The FTC notes that older devices may have outdated security and recommends disconnecting devices you no longer use.
- Re-test after app changes. A redesigned app or a new account login method can quietly break an integration or stop notifications.
When do batteries need attention?
Battery-powered locks, sensors, shade motors, and remotes need replacement on a cycle that depends on the device, how often it’s used, and its wireless connection. Most platforms report battery levels; the habit that matters is acting on those reports.
Practical tips:
- Use the battery type the manufacturer specifies. A different type may report its level differently or last a shorter time.
- Keep spares of each type at the property, labeled by device.
- For second homes, replace low batteries before leaving rather than waiting for an alert while away.
- Know the backup entry method for every smart lock. Many models accept a physical key, and the manual for your model explains what other options it has when the batteries are dead.
What documentation should you keep?
Documentation is what lets anyone, including a future technician, understand and fix the system. Keep it current and somewhere the owner can always reach it.
A complete set usually includes:
- Device inventory. Model, location, connection type (Wi-Fi, Zigbee, Z-Wave, Thread), firmware version, and purchase or warranty date.
- Account list. Every app and cloud service, which email owns it, and who else has access. Store passwords in a password manager, not in the document.
- Network map. Router and access point locations, network names, reserved addresses for hubs and cameras, and where the modem and UPS are.
- Automations in plain language. For example, “At sunset, porch and driveway lights turn on; at 11 p.m., they turn off unless someone is outside.”
- Manual fallbacks. How to operate lights, locks, shades, thermostats, and the water shutoff by hand.
- Recovery items. Where backups are stored, where the encryption key is kept, and who to contact.
Who should own the accounts?
The property owner, or the business, should hold the owner or primary administrator role on every account. Installers, integrators, and property managers should have their own separate access that can be removed without touching the owner’s account.
This matters most when relationships change. If an installer set everything up under their own email, a new owner or a new service provider may not be able to transfer devices without factory resets. For businesses, use an email address the company controls, not an employee’s personal account. Turn on two-factor authentication where offered, as the FTC recommends, and make sure recovery details point to someone who will still be there in a year.
How do you troubleshoot when something stops working?
Start by finding the scope of the problem, then check the basics in order. Most failures come down to power, the network, a recent change, or a battery.
- Define the scope. One device, one room, one platform, or everything? Everything failing at once points to power, the network, the internet connection, or the hub.
- Check power. Breakers, outlets, batteries, and the UPS.
- Check the network and internet. Can other devices browse? Is the hub reachable? See our guide on why networking matters for automation for common network causes.
- Look at recent changes. Updates, a new router, a changed Wi-Fi password, or a new device are frequent culprits.
- Read the logs. Most hubs show when a device went offline or an automation last ran.
- Restart deliberately. Restart one component at a time, starting with the one most likely involved, and note what changed.
- Re-pair or reset only as a last step, because it can remove the device from automations.
- Write down the fix in the system’s documentation.
| Symptom | Common causes to check first |
|---|---|
| One device offline | Battery, weak signal, power at the outlet, device needs re-pairing |
| Several devices in one area offline | Access point or mesh unit issue, Zigbee or Z-Wave repeater unpowered |
| Automations run late | Weak signal, overloaded network, cloud integration delays |
| Remote access and notifications stopped | Internet outage, vendor cloud issue, app logged out, phone notification settings |
| Everything stopped after a power outage | Hub didn’t restart cleanly, devices received new addresses |
What does a recovery plan look like?
A recovery plan answers one question: if the main hub, router, or a key device failed today, how would the property keep working, and how would it be restored? Write the answers down before you need them.
A good plan covers manual fallbacks (keys, wall switches, thermostat controls), backups with their keys, a list of replacement hardware, and who to call. For second homes, it also names someone local who can get inside if remote access is down.
What do support agreements cover?
Support agreements are optional. Their hours, response commitments, remote and onsite scope, and fees are defined in each agreement, so there is no single answer for what “support” includes. Some owners prefer a one-time project with good documentation and call for help as needed; others, especially property managers and second-home owners, prefer scheduled check-ins and updates handled for them.
How AppxSmart can help
The SwayPC team behind AppxSmart documents every system we install, leaves account ownership with the owner, and sets up backups and update practices that fit the platform. If you’d like ongoing help, our support and maintenance service describes how agreements work, and our Wi-Fi and networking service covers the network side. We can also review a system someone else installed. When you’re ready, request a free consultation and we’ll contact you as soon as possible.
Questions people ask
How often should an automation system be checked?
It depends on the size of the system and how the property is used. Many owners do a light check monthly (notifications, batteries, offline devices) and a fuller review a few times a year. Second homes benefit from a check before arrival and before storm season.
Should I turn on automatic updates for everything?
For phones, apps, routers, and most device firmware, automatic updates are a sensible default, and CISA recommends them. For the central hub or controller, we prefer reviewing release notes and backing up first, because an update there can change how many devices and automations behave.
What happens if the installer is no longer available?
If you own the accounts, have the documentation, and keep backups with their encryption keys, another qualified professional can pick up the system. That is the main reason we hand over full documentation and keep owner accounts in the owner's name.