HC-800, EA-1, EA-3, EA-5: Which Control4 Controllers Can Still Be Upgraded?

You've found the model number on the box in your rack and you want to know where you stand. Here it is, by model, without the sales pitch.

Find the number first

It's on a label, usually the top or back of the Control4 box everything else reports to. Photograph it while you're there — you'll want the MAC address too, and it's on the same label.

Also get your current OS version from the system's status or settings screen. Model plus version is all anyone needs to give you a real answer.

The legacy generation: HC-250, HC-800, HC-1000

Ceiling: OS 3.3.0. Cannot run 3.4.x. Cannot run X4.

This is a hardware limit. No subscription, no dealer, and no amount of money changes it. If you're on an HC controller and someone has offered to upgrade you to X4, they've misread the model.

What that means in practice: your system works, and will keep working. What you lose is the future — new drivers for equipment made in the last few years increasingly need a newer OS, so a new TV or receiver may simply not be addable. And Control4 has already ended cloud services for OS 2 systems, which is a reminder that "works today" and "supported" are different things.

None of that is urgent. It's the reason a system that's fine slowly becomes one nobody can help with.

The middle generation: EA-1, EA-3, EA-5

All three reach OS 3.4.3, the final and most stable OS 3 build, and the version most third-party drivers were written against.

The EA-3 and EA-5 can go on to X4. The EA-1 is more limited — worth confirming against its current capability before planning around it.

If you're on an EA and your complaint is "I bought something and it won't integrate," getting to 3.4.3 is often the entire fix, and it's the cheaper of the two upgrades. X4 is the bigger jump and buys you Routines — homeowner-editable automation without a dealer — plus HomeKit, AirPlay 2 and a rebuilt app.

Two things X4 takes away that catch people: on-screen display goes away on EA controllers in X4.1 and later, and certain older touchscreens and first- and second-generation lighting stop receiving updates. If your household navigates the system on a TV screen, that changes.

Current: CA-1, CA-10, CORE 1, CORE 3, CORE 5

These run X4 and will for years. If you're here, upgrades are version steps rather than hardware decisions.

What replaces what

The sensible default is like-for-like on capability — an EA-1 is replaced by a CORE 1, an EA-3 by a CORE 3, an EA-5 by a CORE 5. That's a default, not a law. What actually decides it is what's plugged into the back of your current controller, because the new one has to have a home for each of those connections.

‼️Here's the trap, and it's the one that ruins swaps. The CORE 1 has no analog audio output. If your current controller feeds an amplifier from its analog outputs — which is extremely common on older installations — a straight swap leaves that amplifier wired to a port that doesn't exist on the new box.

The fix is a digital-to-analog converter in the signal path. It's a real part with a real cost, and it is not an upsell — it's the difference between the system working and the whole-house audio being silent on day one. A quote that doesn't mention it hasn't looked at your project.

So the question to ask about any controller quote: what is connected to the back of mine, and does the replacement have somewhere for each of those?

The staged climb, and why skipping it breaks things

An OS upgrade isn't one step. A system on 3.1 goes 3.1.x → 3.3.1 → 3.4.3 → and only then 4.2. Each stage carries your project forward.

Skipping stages is how bindings break. A binding is the connection that says this keypad button controls that load and this source feeds that room. Drag a project across too many versions at once and some don't survive the translation. What you see afterwards is a house where buttons do nothing and the wrong lights answer — and the repair is rebuilding programming by hand, which costs multiples of the upgrade.

Ask which versions you'll pass through. A specific answer is a good sign.

The backup is not optional

Your project file — every light load, every keypad button, every driver and binding — lives on the controller. If your original dealer never gave you a copy, that box holds the only copy in existence.

Before anything is touched, a backup should be taken and confirmed readable. "We'll grab one" is not the same as having one. And when a controller is being replaced, that file is the thing that carries your house onto the new hardware — without it, you're not swapping a controller, you're paying someone to rebuild your programming from scratch.

Related: never let anyone factory reset the controller to "start clean." We've seen six figures of programming disappear in about forty seconds that way.

The subscription question

You do not need a Connect subscription to upgrade an existing system to X4. That became optional at the end of Q1 2026, and we've taken a real EA-5 from 3.4.3 to 4.2.0 with none on the account.

4Sight, the old remote-access subscription, is retired. Connect replaced it, activating Connect ends 4Sight permanently, and there's a Core Lite tier that's free through the end of 2026. Decide about remote access on its own merits, after your system is current — not as a toll booth in front of the work.

What the rest of your house does during all this

Very little, and this is the reassuring part. The keypads, dimmers, touchscreens, amplifier and speakers all stay exactly where they are. Whether you're upgrading an OS or replacing a controller, it's the brain that changes. Your house doesn't get rebuilt.

Getting a straight answer

Send the controller model, the MAC address, the current OS version, and roughly what's connected to the back, and we'll tell you which of the three situations you're in — including when the answer is that you're fine and shouldn't spend anything. We do Control4 upgrades and controller swaps remotely, and we'd rather talk you out of one than sell you the wrong box.

Still on OS 2? That crossing has its own rules — a hard floor at OS 2.10.0, a hardware check that rules several of these boxes out entirely, and a step that needs someone physically at the controller. We wrote it up separately: still on Control4 OS 2, what can actually be done.