Most automation projects that go badly were predictable from the first meeting. Not because the installer was dishonest, but because nobody asked the questions that separate a company doing engineering from a company reselling boxes. Here are the ones worth asking, and what a solid answer sounds like.
You do not need technical knowledge to use this list. You are listening for whether the answer is specific or vague.
On the system itself
1. Will the wall switches work if the internet is down?
Listen for: a straight yes, with an explanation of why. In a properly designed wired system, keypads talk to dimmers directly and the internet is only for remote access.
If the answer is qualified, or you hear that you would use the app instead, understand what that means: an ISP outage becomes a lighting outage.
2. What happens when the power comes back after an outage?
Listen for: evidence they have thought about it per circuit. Good answers mention configuring restore behaviour deliberately. If this has not been considered, you may get every light in the house at full brightness at 3am.
3. Does anything stop working if the manufacturer shuts down a service?
Listen for: honesty about which functions are cloud-dependent. Almost every system has some. The answer you want is that core functions are local and only remote access depends on a service.
On the installation
4. Is there surge protection at the distribution board, and has earth resistance been measured?
Listen for: a number, or a commitment to measure and document one. Surge protection without a verified earth does very little. We wrote about why in designing for Nigerian power realities.
5. What is on backup power, and for how long?
Listen for: the controllers, bus supply, network switch and NVR being named specifically. These are small loads that keep the system alive.
6. Does every automated thing have a manual override?
Listen for: yes, with specifics on curtains, gates and locks. Mechanical override is a safety matter, not a convenience.
On ownership, which is where people get trapped
7. Who holds the programming file, and can I have a copy?
Listen for: that you get a copy at handover. This is the single most important commercial question on this list.
If the configuration lives only on one person's laptop, you are dependent on that person forever. Some installers use this deliberately. A company confident in its service does not need to.
8. If I fall out with you, can another company take this over?
Listen for: yes, with an explanation of what the next company would need. Nobody enjoys this question, and how it is received tells you a lot.
9. Is the hardware proprietary to you, or an open standard?
Listen for: a clear statement. Established standards mean parts remain available and other professionals can work on it. Genuinely closed systems tie you to one supplier's continued existence.
On what happens after
10. What exactly does the warranty cover, and for how long?
Listen for: a distinction between hardware and labour, and a written term. Ask specifically whether a callout in year three costs you anything. Our own installations carry a five year warranty, and we mention it here only because the follow-up question matters more than the headline: get the terms in writing.
11. What documentation do I get at handover?
Listen for: as-built drawings, a device schedule with locations and addresses, the programming file, and credentials. Documentation is what makes the system maintainable by anyone, including you.
The four that matter most
- Do the switches work without internet?
- Do I get a copy of the programming file?
- Can another company take this over?
- What is in the handover pack?
One thing that is not on the list
Price is not among these questions, deliberately. Not because it does not matter, but because you cannot evaluate a price until you know what is included. A quote that omits surge protection, backup power, documentation and a real warranty will always look cheaper than one that includes them, and it is not cheaper. It is smaller.
Get the answers above first. Then compare quotes, and make sure you are comparing the same scope.