Alexa or Google won’t control Control4 — how to fix voice commands

Nine times out of ten when a customer rings us saying “Alexa’s stopped controlling the lights” or “Google just says the device isn’t responding”, it’s one of a small handful of things — and none of them mean your Control4 system is broken. The voice assistant and Control4 talk to each other through the cloud, so when commands stop working it’s almost always a link, a name, or a subscription that’s dropped out.

Here’s how we work through it, in the order we’d check it ourselves.

First, understand how the two systems actually talk

Alexa and Google Assistant don’t connect directly to your controller in the cupboard. They reach it through Control4’s cloud service, which means three things all have to be healthy at once:

• Your Control4 system has an active 4Sight (or Control4 Connect) subscription.
• The Control4 skill (Alexa) or Action (Google) is linked to your Control4 account.
• Your devices have clear names and rooms that the assistant has discovered.

If any one of those three is out, the voice side goes quiet. So that’s our checklist.

Step 1: Check your Connect/4Sight subscription is active

This is the one we hit most often. Voice control rides on top of remote access, and remote access needs a current subscription. If the card on file expired or 4Sight lapsed, the first thing that usually breaks is exactly this — the app might still work on your home Wi‑Fi, but voice and away-from-home control stop.

Open the Control4 app, head to your account or settings area, and confirm 4Sight/Connect shows as active. If it’s lapsed, renewing usually brings voice back within a few minutes once it syncs. If you’re not sure where to look, our remote access guide walks through it, or give us a call.

Step 2: Re-link the account

Cloud links go stale. A password change, a Control4 account update, or just time passing can quietly break the connection between your assistant and Control4. Re-linking fixes a surprising number of “it just stopped” calls.

In the Alexa app

1. Open the Amazon Alexa app and go to More > Skills & Games.
2. Tap Your Skills and find Control4 Smart Home Skill.
3. Select Disable Skill, confirm, then enable it again.
4. Sign in with your Control4 account details when prompted and allow the link.
5. Let it re-discover devices when it offers to.

In the Google Home app

1. Open Google Home, tap your profile, then Assistant settings > Home control (or search “Control4” under linked services).
2. Unlink the Control4 service, then add it again.
3. Sign in with your Control4 account and authorise the link.
4. Assign rooms when prompted so commands land in the right place.

Make sure you’re signing in with the same Control4 account that’s tied to your system. We’ve had a few cases where someone created a second account by accident and linked the empty one — nothing showed up because there was nothing in it.

Step 3: Re-discover devices

Even with a healthy link, the assistant only knows about devices it has discovered. If we’ve recently added a keypad, a new lighting load, or renamed a room, your assistant won’t know until it re-scans.

• Alexa: say “Alexa, discover my devices”, or in the app go to Devices > + and run a discovery.
• Google: say “Hey Google, sync my devices”, or re-run the link in Google Home.

Give it 30–45 seconds. New devices should appear, and stale ones can be removed so they stop cluttering your command list.

Step 4: Sort out device names and rooms

This is where most of the everyday frustration lives. Voice assistants are literal — if a light is named “Pendant 3” in Composer, saying “turn on the kitchen pendants” won’t do anything useful. The assistant matches what you say to the exact device name and the room it’s assigned to.

A few things that consistently cause grief:

• Duplicate names — two devices both called “Downlights” means the assistant doesn’t know which one you mean.
• Odd or technical names — “Zone 4 Dimmer” rolls off no one’s tongue. Names should be how you’d naturally ask for them.
• Wrong room assignment — if a device sits in the wrong room in the assistant app, “turn off the living room” skips it.
• Special characters or abbreviations the assistant can’t pronounce.

You can rename devices and reassign rooms inside the Alexa or Google Home app without touching Control4 at all. We generally tell customers to name things the way they’d say them out loud — “kitchen bench lights”, “theatre downlights”, “hallway”. If the underlying names in the system are the problem, that’s a quick change we make in Composer — just flick us a message through our contact page and we’ll tidy them up. There’s more on naming conventions in our voice control setup notes.

Step 5: Check Privacy Guard isn’t blocking it

Control4’s OS 3 has a Privacy Guard feature that can deliberately restrict remote and voice access — sometimes it’s switched on intentionally, sometimes it gets toggled by accident. If everything else checks out but voice still won’t budge, this is worth a look.

Privacy settings can block third-party (cloud) access to specific devices like cameras, locks and security functions, which is exactly the kind of thing voice control reaches for. If your security or access devices are the ones not responding, this is the likely reason — and honestly, for locks and alarms that restriction is often there for good reason.

What voice can and can’t do

Some of the calls we get aren’t faults at all — they’re a mismatch of expectations. It’s worth knowing where the line sits.

Voice handles well:

• Turning lights on and off, dimming to a level (“set the kitchen to 40 per cent”).
• Activating scenes and groups you’ve set up.
• Adjusting the thermostat — see our climate help for naming your zones.
• Simple media commands in supported rooms — play, pause, volume.

Voice is patchy or not supported for:

• Complex multi-step automations — those live better as Control4 scenes you trigger by name.
• Detailed AV navigation (scrolling menus, picking inputs) — that’s what your Halo or Neeo remote and touchscreens are for.
• Anything behind Privacy Guard, like cameras and certain locks, unless deliberately allowed.
• Devices that simply aren’t exposed to voice in the first place.

If there’s something you’d love to control by voice that currently won’t, it’s often just a matter of us building a scene and giving it a tidy name — then “Alexa, run movie night” does the lot.

Still not playing nicely?

Work through the list in order — subscription, re-link, re-discover, names and rooms, then Privacy Guard — and the overwhelming majority of voice problems sort themselves out. If you want the official word on the integrations, Control4 keeps current details at control4.com.

If it’s still stubborn, it might be something on the system side — a controller that needs a nudge, names to clean up in Composer, or a network issue affecting the cloud link. That’s our department. We can hop on remotely if your system’s online, or come out if it needs hands-on. Don’t wrestle with it for an hour — flag it with us and we’ll get your voice control behaving again.

Cheers, and happy talking to your house.
— Adam and the DUKE team