Control4 App Offline? OS 2 Systems Are Losing Cloud Access
Your Control4 app stopped working, or says the whole house is offline, while the keypads on the wall carry on as if nothing happened. In 2026 there is one cause that did not exist a year ago: if your system still runs OS 2, Control4 switched off its app, remote access and cloud services on November 1, 2026. The house keeps working. The connection to it from outside does not.

That is one of five causes, and most people can tell which one is theirs in five minutes — before anyone charges for a visit.
The single most useful question
Do the keypads on the wall still work? Go press one. Turn a light on and off from the wall, not the app.
If the wall controls work and the app doesn't, your system is running and something between you and it is broken. That is the easier problem, and often free to fix.
If nothing works anywhere, that is power, the controller itself, or the network. Skip to cause 5.
Cause 1: your system is on OS 2, and its cloud has been retired
Check this first, because no setting fixes it. Open the app (or a touchscreen) and go to Settings → About. If the version starts with 2., read on.
Control4 switched off the OS 2 cloud services on November 1, 2026: remote access and cloud services for systems running OS 2 are gone. Snap One's first notice had given August 4, 2026. Before that, 4Sight subscriptions on OS 2 had already stopped auto-renewing in August 2025, and one owner reported an OS 2 controller that stopped reaching Control4's servers in late August.
What stops:
- The app away from home, and remote access generally
- Push notifications and alerts
- Voice control through Alexa or Google
- Intercom Anywhere
- Remote support — a dealer can no longer connect to fix anything from their office
What keeps working: everything inside the house. Keypads, handheld remotes, in-wall touchscreens, lighting scenes, schedules and the programming behind them all run on the controller, not in the cloud. A system that works today will still work tomorrow; you just lose the reach into it.
The fix is to leave OS 2, and the controller model decides how:
- EA-1, EA-3, EA-5, CA-1: these run current software. An OS 2 box of this kind is behind, not obsolete, and moving it up keeps the app.
- HC-800: can move to OS 3, up to 3.3.0 and no further. That keeps you on the OS 3 side of the cutoff, but it is the last stop for that box.
- HC-200, HC-250, HC-300, HC-500 and HC-1000: cannot run OS 3 at all, and they are too old for us to work on. Staying connected means a new controller, set up new, with your programming built again.
One thing to know before anyone quotes you: on an EA or CORE controller, the crossing from OS 2 to OS 3 is done in place with Control4's own update tool, with the project kept, and it can be done remotely. A box below OS 2.10 steps to 2.10 first. We explain the model-by-model detail, including the version steps, in which boxes can make the jump from OS 2 to OS 3.
And if staying on OS 2 suits you — the system does what you want and you never use the app away from home — that is a legitimate answer. Nothing in the house stops working on the retirement date.
Cause 2: the router was replaced
If anything changed about your internet — a new router, a mesh system, an ISP swapping the box, even a factory reset — start here. Automation equipment is found by network address, and a new router hands addresses out differently. The controller is looking for the amplifier, the touchscreens and the lighting processor where they used to be. Nothing is broken; they cannot find each other.
The signature is the one above: wall controls fine, app offline. Often the fix is yours: give the equipment its old addresses back with DHCP reservations on the new router. We walk through it in why a smart home stops working after a new router.
Cause 3: it works at home but not away
If the app is fine on your home Wi-Fi and dead on mobile data, and your system is not on OS 2, that is remote access specifically. The local system is healthy.
Remote access needs a route in from outside. 4Sight, the old subscription, is retired; Connect replaced it, and since November 2025 Connect is one plan, $249 a year, that is optional on X4 (a system already on the old CA-1 or CORE Lite plan keeps it at $0 through the end of 2026). Worth knowing: you do not need a subscription to upgrade your system to X4. That requirement went away at the end of Q1 2026, so if someone bundled the two, they have conflated them.
Cause 4: the app itself, or the phone
- Force-quit and reopen. It genuinely fixes a share of these.
- One phone or all of them? If someone else's app works, it is that device, not the system.
- Home Wi-Fi, not the guest network. Guest networks are usually isolated from other devices by design, which is exactly this symptom.
- Which app? Systems on OS 3 and later use the current Control4 app; an OS 2 system needs the old one, and the current app will not connect to it.
Cause 5: everything is genuinely down
- Does the controller have power and a network light? Equipment gets unplugged during other work and never goes back.
- Was there a power cut? Gear sometimes comes back in the wrong order. A sequenced restart — network first, then lighting processors, then the controller, a minute each — resolves more of these than people expect.
- One room or everywhere? One room points at one device or one circuit. Everywhere points at the controller or the network.
And the thing not to do, however frustrated you get: do not factory reset the controller. Every light, keypad button and connection lives in the project on that box. If nobody has a copy, a reset means the house gets rebuilt from scratch. This matters twice over on an OS 2 system, because the first step of any move off OS 2 is taking a verified backup of that project.
A five-minute triage
- Settings → About. Version starts with 2? → cause 1.
- Press a wall keypad. Doesn't work? → cause 5.
- Anything change about the internet in the last few weeks? → cause 2.
- App works on home Wi-Fi but not mobile data? → cause 3.
- Works on another household member's phone? → cause 4.
While you are there, write down the controller model from its label and the OS version. Every useful conversation from here starts with those two.
Find out where you stand
Our free OS checker takes the model and the version and tells you which situation you are in — including when the honest answer is that a controller has reached its ceiling. No account, no email.
If it turns out to need someone, almost all of this is remote work: repointing drivers, sorting out remote access, planning the move off OS 2. What needs a person in the house is smaller than people assume — a controller that will not boot, and anything physical. We do Control4 work remotely and read and price Lutron systems, and we will tell you when the fix is a router setting you can change yourself this afternoon.
