Home automation handover checklist: what should you test?

Before accepting a home automation installation, test the controls people will use every day, check predictable failure conditions and make sure the owner receives the accounts, configuration and records needed to operate it. A guided demonstration with every service online is not an acceptance test.

Run the checks after the final equipment is installed. Record each result, then give every failed item an owner and a completion date. Handover creates an agreed baseline. It cannot prove that a system will never develop a fault.

Test complete routines rather than isolated devices

Switching every light on proves that each output responds. It does not prove that an everyday routine works from start to finish. Test the command, the physical result, the status shown to the user and any effect on connected systems.

Prioritise the routines with the greatest daily impact:

• Leaving and returning, including lighting, blinds, climate and the alarm.
• Wall controls in every room, without requiring a phone.
• Schedules and sensors under realistic light, occupancy or temperature conditions.
• Gates, intercom and access control, including safe exit from inside.
• Meaningful alerts such as leaks, intrusion or equipment failure.

Exceptions matter as much as the normal path. Should an open window stop climate control? Can a night scene close a blind beside an open terrace door? There is no universal answer. The expected behaviour should come from the agreed requirements, not from a vague promise of a smart home.

If those rules are not yet written down, the home automation design should turn them into a function list before programming begins.

Check failure behaviour deliberately

Ask the technician to simulate an internet outage and restart the controllers and network equipment safely. Do not experiment by switching random circuits off. A poorly planned interruption can affect alarms, gates, recording or other building equipment.

The test should establish:

• Which local controls keep working without internet access.
• How lights, blinds, climate and access behave after a restart.
• Whether schedules resume correctly and retain the right time.
• Which notifications stop when a remote service is unavailable.
• The safe state of gates, locks and alarms.

Not every feature needs to work offline. Remote access, push notifications and externally hosted services may be unavailable. The important decision is which functions are allowed to depend on them and what local fallback the property requires.

Verify ownership and permissions

The owner or facilities team should have its own administrator account. Other users should receive only the permissions their role needs. One shared password for residents, maintenance staff and the installer makes changes difficult to trace and access difficult to revoke.

Confirm who owns every account, licence and remote service. Create and remove a test user, and enable two-factor authentication where the system supports it. Temporary installer access should either be removed or explicitly retained under the support agreement.

In a multi-unit development, repeat this check for each apartment. A standard configuration by unit type reduces accidental variation, but it does not prove that the devices, credentials and sensors in a particular unit were assigned correctly.

Take delivery of a recoverable configuration

The handover records should explain what was installed and allow the system to be restored without relying on one person's memory. Depending on the project, ask for:

• An as-built plan and equipment inventory with locations and identifiers.
• The delivered functions, scenes, schedules and integrations.
• An exportable configuration backup and restoration instructions.
• Relevant software versions and changes made at handover.
• Warranty, licence, subscription and support information.
• Test results and the remaining defects list.

The exact format depends on the technologies used. In a KNX installation, for example, the official project report documentation identifies certificate reports as customer handover material and the security report as a last-resort backup if the project is lost.

A file without a date, version or known restoration process is only half a backup. Keep another copy away from the commissioning computer, as supported by the platform's project archive, and decide who updates it after future changes.

Close handover against observable results

A minor defect need not hold up the entire project, but it should be written as a result that can be retested. “Adjust away scene” is vague. “When Away is selected, switch off indoor lights and keep the external light on for five minutes” has a clear pass condition.

Agree when the warranty starts, where faults are reported and which responsibilities move into ongoing support. The maintenance agreement should use the inventory and configuration accepted at handover rather than reopen the question of what was delivered.

Plan the handover of my installation. Include the property type, installed systems and expected test date.