Buying or Selling a House With Control4: What to Ask For

A house with automation in it is either a genuine asset or an expensive puzzle, and the difference comes down to a handful of things nobody thinks to ask about during a sale. By the time the new owner finds out, the seller has moved and the installer's number has changed.

Whichever side you're on, here's what actually matters.

If you're buying: four things to ask for before closing

1. A copy of the project file. This is the single most valuable item and it costs nothing to request. The programming — every light load, every keypad button, every connection — lives on the controller. If nobody outside the house holds a copy, that box is the only record of the system. It's fine right up until a controller fails, at which point the whole thing gets rebuilt from scratch at a cost that can run well into five figures.

Ask the seller to obtain it from their installer as a condition. Installers generally have it and will hand it over when the owner asks.

2. The installer's name and contact. Even if you don't intend to use them. Knowing who built it means knowing who understands it, and it's the fastest route to the project file.

3. Whether anything is broken right now. Ask specifically, and test it yourself during the viewing or inspection: every keypad, the app, the touchscreens, the audio in each room. Systems degrade quietly — a driver stops matching a device, a room drops off — and "it all works" often means "the lights work."

4. Whether there are any subscriptions. Some services are tied to the account rather than the house, and don't transfer. Ask what's active, in whose name, and what happens at handover.

The five-minute survey that tells you what you're getting

You can do this yourself at a viewing:

• Find the rack or closet. Photograph every label. The controller model is the important one.
• Note the OS version from the system's status screen.
• Look for a second system. Very often the lighting is Lutron and everything else is Control4 — two processors, two sets of programming. Worth knowing there are two.
• Press keypad buttons in each room and see what happens.
• Ask to see the app working on the seller's phone.

An HC-series controller tells you the brain has hit its hardware ceiling and will need replacing eventually. An EA or CORE tells you there's life in it. Neither is a reason not to buy the house — but one is a line item you should know about.

The most common thing that breaks at handover

The house sells, the internet account changes, and the new provider fits a new router. Then half the system stops working.

This is the most common cause of a smart home breaking with nobody touching it. Automation equipment gets found by network address, and a new router hands out addresses differently — so the controller is looking for the lighting processor, the amplifier and the touchscreens where they used to be. Nothing is broken. They just can't find each other.

The giveaway symptom: the lights still work from the wall, but the app says everything is offline.

It's often fixable in the router's own settings — you tell it to hand each device back the address it had before, usually called a reservation or a static lease. If you can get the old addresses from the installer or a photo of the previous router's settings, it can be a twenty-minute job with no programming touched.

Which is why one more thing is worth asking for at handover: the network list — device name, hardware address, assigned address, for every piece of automation equipment. That single page prevents this entirely.

If you're selling: what actually adds value

Not the system itself. A buyer who doesn't understand it discounts it, or worse, sees it as a liability they'll have to rip out.

What adds value is making it obviously usable and obviously supportable:

• Get the project file from your installer and hand it over. It transforms the system from an orphan into an asset, and it costs you a phone call.
• Fix whatever is broken before listing, or disclose it plainly. A buyer who discovers three dead rooms after moving in remembers it.
• Write down what does what. One page: which button is which, what the scenes are for, where the equipment lives. Sounds trivial; it's the difference between a buyer who uses it and one who resents it.
• Say what it is. "Control4 with Lutron lighting" means something to the right buyer. "Smart home" means nothing.

If you've already bought and none of this happened

The common position: you own a house with a system in it, nobody handed you anything, and the installer isn't answering.

It's recoverable, and in this order:

1. Don't let anyone factory reset the controller. Not a handyman, not an electrician, not a new installer in a hurry. If no backup exists, that box is the only copy of your house.
2. Get a backup taken. First job, before any changes.
3. Work out what's actually wrong, if anything. If the system broke around the time the internet changed, it's the network, not the system.
4. Get a dealer of record. The request carries more weight from you, the owner, than from a company trying to pick up someone else's system.

Most of that fourth step, and most ongoing work, happens remotely — programming doesn't care where the person sits. What needs someone in the house is smaller than people assume.

What to send if you want a read on it

Photograph the labels in the rack and note the OS version. Tell us whether there's a second system, whether anything is currently broken, and whether the internet or router changed recently.

We'll tell you what you've got, what it can still do, and whether it needs anything — including when the honest answer is that it's fine and you should enjoy it. Taking over systems whose installer has moved on is most of what we do.