A group of your C-Bus lights won’t turn on or off: what to try first

One of the most common calls our team gets goes like this: “Most of the house is fine, but the kitchen lights won’t come on from the switch or the app.” Nine times out of ten that’s a localised fault — a single group misbehaving, not your whole C-Bus system falling over. The good news is you can do a fair bit of the detective work yourself before anyone touches the switchboard, and that helps us turn up with the right part in the van.

This guide walks you through the same diagnostic sequence we use on site. Work through it in order — each step rules out a chunk of the system so you (or we) aren’t guessing. The diagram below shows how the pieces connect, which makes it much easier to picture where a fault can sit.

First: is ALL of C-Bus dead, or just one group?

Before you go anywhere near the switchboard, walk around and test a few other circuits. Try a different room’s wall switch. Fire off a scene from your eDLT, the Wiser app or a key plate. The question you’re answering is simple: is this one group of lights, or is the whole network down?

• Everything is dead — no switches respond, scenes do nothing, the app can’t talk to the system. That’s a network-wide problem (power supply, network burden/clock or interface), not your kitchen lights. Start with our C-Bus troubleshooting steps for a whole-system outage instead.
• Other rooms work, one group doesn’t — good. The fault is localised. Keep reading.

Step-by-step: localise the fault

1. Confirm the scope. Operate the failing group from two different sources — the local wall switch AND the app or another switch. If it’s dead from everywhere, the issue is at the output unit or the Group itself. If it works from the app but not the wall switch (or vice versa), you’ve narrowed it to a switch or its programming.
2. Check the wall switch driving the group. Press the relevant button on your DLT/eDLT, Saturn or Neo switch. Is the switch’s screen or indicator lit at all? A completely blank, dark or unresponsive switch usually points to a network or unit-power problem — the switch isn’t getting C-Bus power or clock — not a problem with the light itself. A switch that lights up and beeps but the lights don’t move is a different story (the message is getting out, the load isn’t responding).
3. Head to the switchboard and find the output unit. This is the relay or dimmer (for example an L5504D2U dimmer) that actually feeds the affected circuit. Look at its C-Bus status indicator. A steady light generally means it’s powered and seeing a healthy network clock. A unit that’s off or flashing oddly can mean it’s lost C-Bus power, lost the network clock, or has a fault — worth telling us.
4. Check the load circuit breaker. The output unit needs C-Bus to receive the command, but the lights also need 230V on their circuit. If the breaker feeding that lighting circuit has tripped, the unit will happily “turn on” with no light to show for it. If a breaker keeps tripping, stop — that’s a fault that needs a licensed electrician.
5. Use the output unit’s local override/test button. Relays and dimmers have a manual override on the unit itself. Press it. This is the single most useful test in the whole list, because it bypasses the C-Bus message entirely.

What the local override test tells you

When you press the override on the relay or dimmer:

• The lights come on. Brilliant — your load, wiring and the output channel are all healthy. The fault is in the C-Bus side: the message from the switch or app isn’t reaching the unit, or the programming has gone astray. That’s almost always a scene, Group Address or project-download issue rather than hardware.
• The lights stay off. Now you’ve separated a wiring or load fault from a programming fault. Either the lamps have failed (whole group of LEDs dying at once is rarer but happens with a shared driver), the circuit breaker is off, or there’s a wiring fault between the unit and the fitting. This side of things is electrician territory.

That one test saves an enormous amount of time. If you ring us and can say “the override brings them on but the switch won’t,” we already know to bring a laptop and C-Bus Toolkit, not a ladder and lamps.

When only one Group is dead across the whole network

Here’s a pattern we see a lot. The lights work from the local override. The wall switch lights up and beeps normally. But that one group won’t respond from any switch or scene anywhere in the house. When the hardware is clearly fine but a single Group Address is unresponsive system-wide, suspect software, not silicon:

• A corrupted or edited scene. Someone may have saved a scene with that group set to level 0, or a trigger/scene got tangled. Lighting is application 56; scenes often ride on Trigger Control (application 202).
• A missing or partial project download. If the project was edited in Toolkit or PICED and only partly downloaded — or a unit was replaced and never had the project pushed back to it — that group’s Group Address mapping can go missing. The unit is online but doesn’t know it owns that group anymore.
• Learn mode left on, or a duplicated Group Address. Occasionally two units end up fighting over the same group after a botched edit.

These are all things our team fixes from a laptop without touching a single mains terminal — we connect through the network interface (a PCI 5500PC, USB 5500PCU or CNI 5500CN), pull the project, and re-download it cleanly. If you want the background on how that side works, our C-Bus programming notes explain Group Addresses and project downloads in plain English.

Who can fix what

We get asked this constantly, so let’s be clear about the line in Australia:

• You can safely do: testing which switches and scenes work, noting the output unit’s indicator and override behaviour (with the board cover closed), and tweaking scenes or schedules in the Wiser app.
• Licensed-electrician work (our team): anything inside the switchboard, replacing a relay or dimmer, replacing failed lamps or drivers on a fixed circuit, and any mains wiring or circuit-breaker fault. Re-downloading the project and repairing corrupted scenes is a job for an experienced C-Bus integrator like us, even though it’s not “electrical” work — get it wrong and you can knock out other groups.

For more on the network side and how power and clock reach your switches, have a read of our C-Bus network overview. Clipsal also publish solid background material over at clipsal.com if you like the deep detail.

Quick recap

1. Confirm it’s one group, not the whole system.
2. Check the wall switch — blank means network/power, lit-but-no-light means message-not-load.
3. At the board, read the output unit’s indicator and the load breaker.
4. Press the local override: lights on = C-Bus/programming fault; lights off = wiring/load fault.
5. One group dead everywhere with healthy hardware = scene or project-download issue.

That sequence will tell you, in about five minutes, whether you’re looking at a quick app fix or a job for the van. We’ve fixed thousands of these and most turn out to be a stray scene or a half-finished download rather than dead gear — which is the good news.

If you’ve worked through this and your kitchen (or wherever) is still in the dark, don’t sweat it. Drop the symptoms you noted to us and our Melbourne team will sort it — head to our contact page and we’ll get you booked in. Cheers, Adam and the DUKE crew.