A person opens a hallway closet that holds a small network rack.

Most smart-home buying decisions get made from a product page. Lumens, resolution, which assistant it speaks to, whether the app is any good.

Those are fine questions. They are also the wrong ones to lead with, because none of them tell you what happens on a bad day.

A smart home is not really a pile of devices. It is a set of dependencies you have agreed to, most of which nobody wrote down. The useful test is not how impressive the system looks on move-in day. It is what you can find out about it before you commit.

Five questions. None of them exciting. All of them worth more than the spec sheet.

1. What still works when the internet goes down?

Lights? Climate? Shades? Locks? Automations?

The answer does not have to be "everything." Plenty of good systems lean on a cloud service for something, and that can be the right call.

The answer just has to exist before the outage, not during it. A homeowner who knows the front door lock keeps working and the voice assistant does not has a system. A homeowner who finds out at 11pm has a surprise.

2. What information leaves the house, and why?

Maybe you want remote access. Maybe you want a cloud voice assistant. Maybe a particular device is simply better with its vendor service attached.

All defensible. The part that matters is that the trade was intentional, made by you, rather than discovered eighteen months later in a privacy policy update.

"What leaves, and in exchange for what" is a question every installer should be able to answer per device. If nobody can answer it, that is itself the answer.

3. Can a human override the automation?

A smart home should make ordinary life easier, including for people who did not install it.

If a houseguest needs a tutorial to turn off the kitchen lights, you have not built a home. You have built a software demo with plumbing.

Physical switches still matter. So does the ability to stop an automation that has decided something wrong at an inconvenient hour. Automation should be a good default, not an argument you have to win.

4. Who holds the admin access, configuration, backup, and recovery path?

You? The installer? A vendor? An email address a contractor created three years ago that nobody can find?

This one gets less funny the moment something breaks. The system that cannot be recovered is not really yours, no matter what the invoice says. Neither is the one only one person on earth understands.

Ask where the configuration lives, whether there is a backup, whether anyone has ever restored from it, and who holds the credentials. "It's all set up, don't worry about it" is not an answer.

5. Can you fire the installer without firing the house?

This is my favorite test, and the one I would apply to us.

If RyzaLab disappears tomorrow, the homeowner should not discover that we were quietly renting them their own home.

The system should stay understandable. The homeowner should hold administrator control. Documentation, backups, recovery information, and the account relationships that matter should stay with the house.

That is not anti-business. It is what ownership has to mean once the thing you own contains software. A company that has made itself impossible to leave has not earned loyalty. It has just installed a lock and kept the key.

Why boring wins

None of these questions will impress anyone at a dinner party. They are maintenance questions, and maintenance is the least photogenic part of any system.

But they are the questions that decide whether the house still works in year four, after a vendor pivots, an installer moves on, or an internet connection has a bad week. The exciting questions are about what a system does when everything goes right. These are about what it does otherwise, which is the part you actually live in.

Ask them before you buy. Ask them of whoever is quoting the work, including us. Anyone who cannot answer all five is telling you something useful.

If you want the argument underneath these questions, I wrote it up separately: who does my home answer to?

RyzaLab's Smart Home Blueprint is a 60-minute assessment of your space, existing devices, routines, and priorities, ending in a written plan covering what to automate, what hardware to buy, what to skip, and who to call. These five questions are part of what it answers. Book Your Blueprint.