Adding voice control to C-Bus with Alexa or Google Assistant

One of the most common questions we get after we’ve installed a C-Bus system is “can I just tell it to turn the lights off?” The short answer is yes — C-Bus pairs nicely with Amazon Alexa, Google Assistant and Apple’s Siri (via HomeKit). The thing worth understanding up front is that the voice smarts don’t live inside C-Bus or the Wiser app at all. There’s no microphone in your Saturn switch and no “hey Wiser” wake word. What actually happens is the Wiser controller talks to the cloud, and your Alexa or Google device talks to that same cloud, so when you speak, the assistant relays the request through to your scenes and loads.

Get the setup right and it’s genuinely brilliant — “Alexa, goodnight” and the whole house settles down. Get it wrong and you’ll be standing in the kitchen repeating yourself while the dog looks at you. This article walks through how it fits together and how to set it up so the commands you actually use work every time.

How voice control connects to C-Bus

Your C-Bus network handles the lighting, blinds and whatever else is wired to your output units. The Wiser Home Controller sits on that network and gives it an interface to the wider world — the Wiser app on your phone, and crucially a cloud connection. Alexa and Google Assistant each run their own cloud service too. To bring the two together, you link the controller to the relevant voice platform, either through the controller’s own cloud service or a dedicated skill/action, and authorise the connection so the two clouds can talk.

Once that handshake is done, the assistant can “see” the items the controller exposes — usually your scenes (Wiser calls these moments) and, depending on setup, individual loads. From then on, speaking a command sends it up to the assistant’s cloud, across to the controller’s cloud, down to your Wiser controller, and out onto the C-Bus network as a normal Lighting (application 56) command. It sounds like a lot of hops, but it all happens in under a second on a healthy connection.

Why scenes (moments) are the secret to reliable voice

Here’s the bit that trips most people up. Voice assistants are great at “turn this on” and “turn this off”, but they’re not great at understanding your house. They don’t know that your kitchen actually has three separate dimmable circuits, or that “movie time” means dim the lounge to 20%, kill the downlights and drop the blinds.

That’s why, nine times out of ten when we set up voice for a customer, we build the things they want to say as scenes on the Wiser controller first. A scene is a single named action that can set any number of loads to any levels you like. The voice assistant then just needs to “turn on” that one scene — which it’s very good at.

• Single loads work too — “turn on the kitchen lights” can map to one group address — but you lose the ability to set a specific level or ramp rate, and busy areas with multiple circuits get clunky.
• Scenes give you predictable, repeatable results every single time, because the levels are baked into the scene on the controller, not left to the assistant to guess.

So if there’s a particular lighting state you use daily, ask us to build it as a moment. “Dinner”, “Movie”, “Goodnight”, “Welcome home” — each becomes a tidy voice command.

Name your scenes the way you’ll actually speak

This matters more than people expect: the name of your scene becomes your voice command. If we label a moment “LZ3 Evening Preset 2”, you’re going to have a bad time trying to say that to Google at 9pm. Name things in plain, natural language.

• Say it out loud before you commit to a name. “Turn on movie time” should roll off the tongue.
• Avoid abbreviations, room codes and numbers where you can.
• Keep names distinct — if “lounge” and “lounge lamps” sound too similar, the assistant may trigger the wrong one.
• Group rooms sensibly so “kitchen lights” does what you’d expect.

The “all off” trap

A request we hear constantly: “I just want to say turn everything off.” Reasonable — but a blanket all-on or all-off usually won’t work out of the box. The assistant can only act on what the controller exposes, and it doesn’t inherently know what “everything” means in your house.

The fix is simple: we build an “All Off” (and often an “All On” or “Welcome Home”) moment on the Wiser controller that sets every relevant load to the right level. Then “Alexa, all off” maps to that single scene and behaves exactly how you’d want. If you’ve ever wondered why your mate’s voice command turns everything off and yours only does the lounge, this is why — theirs was built as a scene, yours wasn’t yet.

Voice runs through the cloud — so the internet matters

Because every command travels through the assistant’s cloud and the controller’s cloud, voice control depends entirely on your internet connection being up. If the NBN drops out or your controller loses its connection to the cloud, voice commands stop working — even though the C-Bus network itself is still happily running locally.

The good news is your wall switches, the Wiser app on the local network and any programmed schedules keep working regardless. Voice is a convenience layer on top, not a single point of failure for the whole house. But it does mean a flaky router or a controller that keeps losing its internet link will show up as “voice randomly stops working”, and that’s worth chasing down. If your assistant has gone quiet, our troubleshooting guides are a good place to start.

Setting it up, step by step

Here’s the general flow. Alexa and Google differ slightly in wording, but the shape is the same.

1. Confirm the controller is online. Open the Wiser app and check the controller has a healthy internet connection. Voice won’t link if the cloud connection isn’t up.
2. Build the scenes you want to control. Decide which actions you’ll speak — Goodnight, Movie, All Off, Welcome Home — and have them created as moments on the controller with sensible, natural names.
3. Add the integration on the assistant side. In the Amazon Alexa app or the Google Home app, add the relevant Wiser/Clipsal skill or action and sign in with your controller’s cloud account to authorise the link.
4. Discover devices. Ask the assistant to discover devices (“Alexa, discover devices”) or run the discovery in the app. Your exposed scenes and loads should appear.
5. Tidy the names and add routines. Rename anything that’s awkward to say, group items into rooms, and create assistant-side routines for extra trigger phrases like “goodnight”.
6. Test the commands you’ll actually use. Stand in the room, say each command out loud, and confirm it does exactly what you expect. Adjust scene levels on the controller if needed.

Where we come in

You can absolutely do the linking yourself, but the part that makes voice feel polished is the planning underneath — which scenes to build, what to name them, and tuning the levels so “movie time” looks right rather than just “on”. That’s the bit we genuinely enjoy. We’ll sit down with you, work out the handful of commands you’ll really use day to day, build them as proper moments, link your assistant, and then test every command together so you’re not left guessing.

If you want to dig deeper into building scenes in the first place, our automation articles cover moments and schedules, and the Clipsal/Schneider Electric resources at clipsal.com have the official Wiser documentation if you like reading the fine print.

Thanks for reading — and if you’re a Melbourne C-Bus owner who wants voice control set up properly so it just works, get in touch with our team via our contact page and we’ll sort it out for you. Cheers, Adam and the DUKE team.