Understanding the parts of your C-Bus system

If you’ve just moved into a home with C-Bus, or you’re weighing it up for a renovation, the first thing worth understanding is that it doesn’t work like the light switches you grew up with. With traditional wiring, the switch on the wall is physically wired to the light it controls — flick it and you complete the circuit. C-Bus throws that idea out. Instead, every device in the system talks to every other device over one shared low-voltage cable, and the actual switching of the lights happens somewhere else entirely: inside your switchboard.

That sounds abstract until you see how the pieces fit together. So before we go any further, here’s the lay of the land. The diagram below shows the main families of C-Bus units and where each one lives.

C-Bus is a network, not a bundle of switch wires

C-Bus is Clipsal’s wired automation system (Clipsal is owned by Schneider Electric). The heart of it is a single pink Cat5 cable — the C-Bus cable — that daisy-chains around your home connecting every device. That cable carries both low-voltage power for the devices and the messages they send each other. It’s a SELV (Separated Extra-Low Voltage) cable, so the pink cable itself is the safe, low-voltage side of the system.

When you press a button on a C-Bus wall switch, the switch doesn’t carry any lighting current. It simply puts a message onto the cable: “Group 5, go to 100%.” Every device on the network hears that message, but only the one responsible for Group 5 acts on it. That’s the mental shift — buttons send messages, and something else does the heavy lifting.

The three families of C-Bus units

Every C-Bus device falls into one of three groups: output units, input units, and system units. Once you know which is which, the whole system makes a lot more sense.

Output units — the muscle (relays and dimmers)

Output units are the parts that actually switch or dim your lights and other loads. They sit in the switchboard and the lighting circuits run through them. There are two main types:

• Relays — these are simple on/off switches. They’re perfect for circuits you only ever want fully on or fully off: power points, exhaust fans, garden lights, LED strips on a driver that doesn’t dim well.
• Dimmers — these vary the brightness of a circuit, ramping it smoothly from off through to full. A unit like the L5504D2U is a four-channel dimmer. Dimmers are matched to the type of load (halogen, LED, etc.), which is why getting the right model for your lights matters.

An output unit’s channels are the bit that does the work. When that “Group 5, go to 100%” message lands on the cable, it’s a relay or dimmer channel assigned to Group 5 that responds by energising the circuit. The level can sit anywhere from 0 (off) to 255 (full), which is how dimming and scenes are achieved.

Input units — the messengers (switches and sensors)

Input units are the parts you touch and the parts that watch. Wall switches — the Saturn, Saturn Zen, Neo, and DLT/eDLT ranges — are all input units. So are PIR occupancy sensors, light-level sensors and key fobs. Their entire job is to send messages onto the network.

Crucially, an input unit never carries the lighting load. A C-Bus wall switch isn’t wired to your downlights at all. It’s connected only to the pink C-Bus cable, drawing a tiny amount of power to light its indicator LEDs and send its button presses. This is why a single elegant four-button plate can control a dozen different things — it’s just sending messages, and each button can be programmed to mean whatever you like.

System units — the housekeeping (power supply and network interface)

System units keep the network alive and let it talk to the outside world. The two you’ll hear us mention most are:

• System power supply (such as the 5500PS) — this feeds the low-voltage power onto the C-Bus cable that all those switches and sensors run on. A network needs enough power-supply capacity for the number of devices connected, and it also provides the network “burden” and clock that keep everything in sync.
• Network interface — this is the bridge between your C-Bus network and a computer or controller. A CNI (Clipsal Network Interface, like the 5500CN) connects C-Bus to your home network over Ethernet, so we can programme the system with C-Bus Toolkit, and so a Wiser Home Controller or app can see and control everything. There are also USB (5500PCU) and serial (5500PC) interfaces for direct connection.

You generally never touch the system units day to day — but they’re the reason the whole thing works, and the CNI is what lets us log in remotely to help when something’s not right.

Where everything physically lives

This trips people up, so it’s worth spelling out. Most output units and system units are DIN-rail mounted inside your switchboard — they clip onto the same metal rails as your circuit breakers and safety switches. That’s where the relays, dimmers, power supply and network interface live, all wired together and onto the pink cable.

The input units sit out on the walls where you can reach them — the switch plates by your doors, the sensors in your hallways. They connect back to the switchboard purely via the pink C-Bus cable threaded through the walls. So the elegant switch you press in the lounge is electrically a world away from the dimmer that’s actually controlling those lights three rooms over in the board.

Groups and applications: how it all links up

Since nothing is hard-wired switch-to-light, C-Bus needs another way to connect a button to a circuit. That’s done with Group Addresses and applications.

Think of an application as a category of control. Lighting is application 56, and it’s where almost all your everyday on/off/dim activity happens. There are others — Trigger Control (202) for scenes and Enable (203) for logic — but Lighting is the one to know.

Within an application, a group is the actual label that ties devices together. A dimmer channel is assigned to, say, “Group 12 — Kitchen Pendants.” A button on a wall switch is also assigned to Group 12. Now they’re linked. Press the button, the message goes out tagged Group 12, and the dimmer channel for Group 12 responds. Want that button to control a different light tomorrow? We just change which group it sends — no rewiring. This software-based linking is the whole superpower of C-Bus, and it’s covered in more depth over in our programming articles.

Why this matters when you call us

Knowing the parts isn’t just trivia — it genuinely helps us help you faster. Nine times out of ten when a customer rings about a fault, the most useful thing they can tell us is which part is behaving oddly.

• If one wall switch has gone dead but the lights still work from elsewhere, that points to an input unit or a cable run.
• If a whole circuit won’t respond from any switch, that points to the output unit (the relay or dimmer channel) in the board.
• If the entire system is unresponsive or the app can’t connect, we’re looking at a system unit — the power supply or network interface.

Being able to say “the switch lights up but the lights don’t come on” versus “the switch is completely dark” tells us straight away whether the problem is on the messaging side or the load side. If you’d like to learn how to read the signs yourself, our troubleshooting guides walk through the common ones. You can also read Schneider Electric’s own overview of the platform on the Clipsal website.

That’s the full cast of characters. Output units do the work in the board, input units send the messages from the wall, and system units keep the network humming — all linked together not by copper between switch and light, but by groups and applications in software.

We’ve installed and untangled a lot of these systems around Melbourne, and we’re always happy to explain how yours is set up. If anything here doesn’t match what you’re seeing at home, or you’d like us to take a look, get in touch via our contact page and we’ll sort it out. — Adam and the DUKE team.