For techniciansFor homeownersBasicLast reviewed 2026-06-20

A C-Bus wall switch that’s gone completely dark, or one that’s stubbornly showing the wrong room name, is one of the more common calls our team gets. The good news is that nine times out of ten it’s not the switch failing — it’s a network or power issue, or a programming quirk that’s quick to put right. The trick is working through it in the right order so you’re not pulling perfectly good switches off the wall.

Before we get into it, a bit of background that makes the whole thing click into place: your DLT, eDLT, Saturn, Saturn Zen and Neo wall switches are input units. They don’t switch any mains themselves. They’re powered over the same pink C-Bus pair that carries every message on the network, and when you press a button they send a command to an output unit (a relay or dimmer) back in the switchboard, which does the actual switching. The diagram below shows how a switch sits on the network and gets its power.

Wall switchpress a keyGroup Address 3“Kitchen lights”Dimmer outputswitches the loadmessagerespondsKitchen downlightsThe link is in software, not the wiringAny key can be pointed at any Group Address — so one button can run a whole scene, no rewiring.
A C-Bus switch never wires straight to a light. It sends a message on a Group Address; whichever output unit owns that group responds.

Keep that picture in your head and the symptoms start to tell you exactly where to look.

Symptom 1: the switch is completely blank or unlit

If a switch shows no backlight, no indicator LEDs, nothing at all, it has lost C-Bus power. These switches draw their power from the network, so a dead switch almost always means the C-Bus pair has lost voltage or the network has a fault — not that the switch itself has died.

The first question we ask is: is it one switch, or a whole bank?

  • A whole group of switches dark points firmly at the network or the system power supply. A healthy C-Bus network sits around 30V on the pink pair, fed by a 5500PS system power supply (or the supply built into a Wiser controller). If that’s tripped, failed, or you’ve lost a section of cable, everything downstream goes dark together.
  • One switch dark while its neighbours are fine tells you the network is healthy and the fault is local — a bad connector on that unit, a nicked cable, or occasionally a failed switch.
Heads up The pink C-Bus cable is low-voltage SELV and safe to handle, but the system power supply and every output unit live in the switchboard alongside 230V mains. Opening the board, reseating output units or chasing a tripped supply is licensed-electrician work under AS/NZS 3000 — that’s our team’s job, not a DIY one. Checking switches on the wall is fine; opening the board is not.

Symptom 2: the switch lights up but the buttons do nothing

This is a completely different fault. If the backlight and indicators are on, the switch has power and is talking to the network — so the hardware is fine. When a powered switch does nothing, we suspect programming, not the unit.

The usual culprits are:

  • A Group Address that’s been changed or cleared, so the button is now sending to a load that doesn’t exist.
  • A scene or trigger change — someone reprogrammed the project and the button now fires a scene that, for example, sets everything to a level it was already at, so nothing visibly happens.
  • The output unit the button drives has itself dropped off the network or tripped at the board.

If every button on the switch does nothing but the switch is lit, look at the output side and the project. If only one button is dead, it’s almost certainly that single button’s Group Address or scene assignment. Either way it’s a software fix in C-Bus Toolkit, not a hardware swap.

Confirm what a button actually drives with Learn mode

Before changing anything, it’s worth proving which load a button is mapped to. C-Bus has a handy Learn mode built into the switches for exactly this.

  1. Press and hold the button in question for around 10 seconds.
  2. The output that button is mapped to will switch (or ramp) while all the other loads on the network go off — isolating the one Group Address that button controls.
  3. Release the button to exit. The system returns to normal once you let go.

This is a quick, non-destructive way to answer “what does this button even do?” If nothing responds when you hold it, the button isn’t mapped to a live Group Address — which points you straight back at the programming.

Tip Learn mode is great for tracing a mystery switch in an older install where the labels no longer match reality. Walk the house with someone watching the lights and you’ll map the whole project in 20 minutes.

Symptom 3: a DLT or eDLT switch shows the wrong or stale labels

The text labels on a DLT, eDLT, Saturn Zen or Neo switch aren’t typed into the switch on the wall — they’re pushed from the C-Bus project when it’s downloaded from Toolkit. So if a switch is showing an old room name, a label from a previous owner’s setup, or text that no longer matches what the button does, the fix is to refresh the labels from the project.

This happens most often after we’ve reprogrammed part of a system: the new logic gets downloaded but a switch was off the network at the time, so it’s running stale text. A clean re-download sorts it.

  1. Open the current C-Bus project in Toolkit and connect to the network through your interface (a 5500PC PCI, 5500PCU USB, or 5500CN CNI).
  2. Check the label text against each unit in the project tree and correct anything that’s wrong in the software.
  3. Re-download the project to the network so every input unit refreshes its labels and Group Address assignments.
  4. Confirm the switch now displays the correct text and that buttons fire the right loads.

If you don’t have the live project file, don’t guess — relabelling without the correct project risks overwriting good programming. We keep a backed-up copy of every project we commission for exactly this reason.

So is the switch actually faulty?

Putting it together, here’s how we read the evidence:

  • One switch dead, rest of the network healthy → likely a faulty unit or a bad C-Bus connector on that switch. Reseating or replacing it is the next step.
  • A whole bank or section dead → network fault or power supply problem. Don’t touch the switches; look at the cable run and the 5500PS at the board.
  • Switch lit but unresponsive → programming or output-side issue, fixed in software.
  • Wrong labels, buttons still work → stale project data, fixed with a re-download.

Reseating a switch on its C-Bus connector, or swapping in a replacement unit, is technician work — it means handling the network terminations and confirming the burden and clock are still healthy afterwards. Relabelling, on the other hand, is purely software-level and doesn’t require touching any hardware. It’s worth keeping that distinction clear when you’re deciding what you can safely poke at yourself.

Tip Before you call anyone, note whether it’s one switch or several, whether the dead switch is lit or dark, and whether anything was reprogrammed recently. Those three answers let us walk in knowing roughly where the fault is. For more on diagnosing the network itself, see our guide to C-Bus network health and power.

If you want to read up on the switch range itself, Clipsal’s official C-Bus documentation has the full input-unit catalogue and specs.

When to call us

If you’ve got a dead bank of switches, a tripped power supply, or a switch that needs reseating or replacing, that’s our wheelhouse — and anything inside the switchboard has to be done by a licensed electrician anyway. Stale labels and “what does this button do” questions we can often sort quickly, sometimes remotely if your system has a Wiser or a network interface we can reach.

We’ve been commissioning and repairing C-Bus across Melbourne for years, and we keep project backups for every job we touch so a relabel or re-download is painless. If a switch in your home has gone dark or is showing the wrong room, get in touch with our team via our contact page and we’ll get it sorted properly.

— Adam and the DUKE team

Frequently asked questions

Why is my C-Bus wall switch completely blank with no lights?

C-Bus switches are powered over the pink network pair, so a completely dark switch means it has lost C-Bus power. If a whole bank is dark, suspect the network or the 5500PS system power supply; if just one switch is dark while others are fine, it points to a faulty connector or unit on that switch.

My switch lights up but the buttons don't do anything. What's wrong?

If the switch is lit it has power and is talking to the network, so the hardware is fine. The problem is almost always programming — a changed Group Address, a scene that no longer does anything visible, or an output unit that has dropped off the network. It’s a software fix in C-Bus Toolkit.

How do I fix wrong or out-of-date labels on a DLT switch?

DLT and eDLT labels are pushed from the C-Bus project, not typed into the switch. Open the current project in Toolkit, correct the label text, and re-download the project to the network so every switch refreshes its labels. Don’t relabel without the correct project file.

How can I tell which light a C-Bus button controls?

Use Learn mode. Hold the button for about 10 seconds and the output it’s mapped to will switch while all other loads go off, isolating that one Group Address. Release the button to return to normal. If nothing responds, the button isn’t mapped to a live address.

Can I replace a dead C-Bus switch myself?

Relabelling is software-level and safe, but reseating or replacing a switch means handling network terminations and checking the burden and clock afterwards — that’s technician work. Anything inside the switchboard must be done by a licensed electrician under AS/NZS 3000.

Still need a hand? Our team looks after Control4 homes across Melbourne. Call 1300 003 853 or get in touch and we’ll sort it. — Adam, DUKE