What a Remote Control4 Dealer Can and Can't Do Without Visiting

People are reasonably sceptical about remote work on a home system. It sounds like the kind of thing that gets sold as convenient and turns out to mean "we couldn't be bothered to come."

So here's the honest split. There's a real line, it's not about effort, and knowing where it sits stops you paying for a van when you didn't need one — and stops you waiting on a remote session that was never going to work.

The short version

Almost everything that lives in software is remote. Almost everything that involves your eyes, your hands, or a screwdriver is not.

That covers about 90% of cases without further thought. The rest is worth going through, because the exceptions surprise people in both directions.

Done remotely, usually within a session

• Adding a device that's already installed. A new TV or receiver is physically connected and powered; getting the system to know about it is a driver and some programming.
• Fixing an integration that broke after a router change. The single most common repair there is. A driver pointed at an address that no longer exists gets repointed. Small change, big effect.
• OS upgrades. Including the staged climb — 3.x to 3.4.x to X4 — with a backup taken and verified first. Nobody needs to be in the room, though somebody should be reachable.
• Scenes, schedules, and what buttons do. The bulk of "can you change this" requests.
• Recovering a device that fell off the system. Usually re-identifying it in software rather than replacing it.
• Adding rooms or sources to an existing project.
• Taking a backup. Which, if nobody has one, should happen before anything else.
• Working out whether your hardware can do what you want at all. Reading the system and telling you honestly.

Most of these take well under an hour once someone has access, and they're the majority of what a working system needs over its life.

Genuinely needs someone in the house

• Low-end trim on dimmers. Setting the minimum level so LED fixtures don't flicker or drop out has to be judged by eye, in that room, at night, with that fixture. Nobody can see your light flicker from a distance. If lights are twitchy at the bottom, this is a visit.
• Anything physical. Mounting, wiring, re-terminating, swapping a failed device, installing new hardware.
• Wireless range problems. Working out where a repeater goes means being there to find where the signal drops.
• A first pass on scene design. Some of it can be described remotely, but sitting in the room at night deciding how the house should feel is better in person. Adjustments afterward are remote.
• A completely dead controller. If the box won't boot or won't come on the network, somebody has to touch it.

The prerequisite: someone has to be able to reach the system

This is the part that decides whether remote is possible at all, and it's worth understanding before you're told it's impossible.

Your controller sits on your home network, behind your router. For someone outside to work on it, there has to be a route in. Historically that meant a subscription service from the manufacturer. It isn't the only way — a small piece of software or hardware on your network can provide the same reach — but some route has to exist.

Two things worth knowing:

You do not need a Connect subscription in order to upgrade to X4. That requirement went away at the end of Q1 2026. If someone made buying one the precondition of doing work, their information is out of date. Decide about remote access on its own merits, not as a toll booth.

4Sight is retired. If you had one, it doesn't come back. Connect replaced it, and activating Connect ends 4Sight permanently.

If neither exists on your system, establishing reach is usually a short first job, and after that everything on the remote list above is available.

The arrangement that works best

Most households that inherit a system end up with a split: someone remote for programming and system work, a local electrician or handyman for hands.

That's usually faster and cheaper than one company doing both, because most of what gets called "on-site work" doesn't require programming skill — it requires being there. Paying integrator rates for van time and physical labour is paying twice for one of them.

It also means the two things happen at their own pace. A driver fix doesn't wait for a scheduling window; a mounting job doesn't wait for a programmer's availability.

How to tell which one you need, before you call

Ask yourself: would the fix be visible on a screen, or in a wall?

• "The app can't see it, but the wall control works" → software, remote.
• "Nothing lights up at all" → power or wiring, on-site.
• "It flickers at low levels" → trim, on-site.
• "It stopped after the router was replaced" → almost always software, remote.
• "It works sometimes" → likely wireless range, probably on-site.
• "I want it to do something different" → programming, remote.

That list resolves most calls before anyone quotes you.

What to have ready either way

Controller model and MAC address from the label. Current OS version from the status screen. Whether network equipment changed recently. Whether anyone has a backup of your project. And a plain description of the symptom — which device, does it light up, is it constant or intermittent.

Send us those and we'll tell you which category you're in, including when the honest answer is that you need someone local rather than us. We do Control4 and Lutron work remotely and we'd rather say "that's a visit" up front than take your money and discover it afterwards.