How a C-Bus system is organised: networks, applications and groups

One of the first things we explain when a customer rings up curious about how their C-Bus system actually “thinks” is that nothing is hard-wired in the way they imagine. A traditional light switch is physically connected to the light it controls — pull that cable out and the switch is dead. C-Bus doesn’t work like that at all. Instead, switches and lights are linked by a shared address, and that’s what makes the whole system so flexible. Once you understand the three-part address, the rest of C-Bus falls into place.

The address has three parts, and they always travel in the same order: Network, then Application, then Group Address. Every command a switch sends — and every output unit listening — speaks this same language. The diagram below shows how those three layers nest together.

The Network: where everything lives

At the top of the tree is the Network. Think of it as the shared conversation that all your C-Bus devices are part of. Physically, it’s the pink Cat5 C-Bus cable daisy-chaining around your home, powered by a system power supply (the 5500PS) which also provides the network clock and burden. Every Saturn, Neo or eDLT switch, every relay and dimmer in the switchboard, and any network interface like a PCI or CNI sits on that network and can hear every message that goes across it.

Most Melbourne homes we wire run as a single network, which keeps things simple. Larger properties get split into multiple networks joined by a Network Bridge (5500NB) to keep traffic manageable — but the principle is identical, and each network gets its own number. If you’re still getting your head around the cabling side of this, our C-Bus network articles walk through power supplies, burden and topology in more detail.

The Application: what type of function

Within a network, an Application defines the type of thing being controlled. Lighting is by far the most common, and it’s Application 56 (you’ll also see it written as 0x38 in hexadecimal). When a switch sends a lighting command, it stamps it with application 56 so that only devices configured for lighting pay attention.

There are other applications too — Trigger Control is 202 and Enable Control is 203, both used heavily for scenes and automation logic. For everyday switching and dimming, though, application 56 is where the action is. The key idea is that the application is a category, not a specific light. It narrows the conversation down to “this is a lighting instruction” before we get to the part that says which light.

The Group Address: the actual channel

Here’s the part that makes C-Bus click for people. The Group Address is the specific “channel” within the lighting application — the thing that genuinely ties a switch to a load. It’s the C-Bus equivalent of tuning two radios to the same frequency.

When our team programmes a system, we assign a Group Address to each output. So a single dimmer channel in your switchboard — say one channel of an L5504D2U dimmer — gets allocated Group Address 3. From that moment on, that channel is “listening” for any message addressed to group 3 on the lighting application.

Now, any input that sends to group 3 will control it. That could be a button on a Saturn switch by the kitchen door, a button on an eDLT down the hall, a scene triggered by the Wiser Home Controller, or a command from your phone. None of them are physically wired to the dimmer. They’re simply all set to send to group 3, and the dimmer obeys whoever speaks last.

This is the whole secret to C-Bus being so flexible. Want the kitchen lights controlled from three different switches? Set all three buttons to group 3. Want one button to control lights in two rooms? Have it send to two groups. Nothing in the switchboard changes — it’s all in the programming.

Levels: off, dimmed or full

A Group Address doesn’t just carry an on/off state. It carries a Level, a number from 0 to 255. Zero means fully off, 255 means fully on, and everything in between is a dimmed value. So the same group 3 can mean “off” (level 0), “romantic dinner” (level 80), or “full brightness for cleaning” (level 255).

This is why a single dimmer group can do so much. A button press might send group 3 to level 255, a long press might ramp it down, and a scene might set it to level 128 over a few seconds (that gradual fade is the ramp rate). The output unit just receives the target level and the time to get there, and does the work. If you’d like to understand how dimmers and relays respond to those levels, our C-Bus lighting guides go deeper on output units and ramp rates.

Tags: turning numbers into names

Nobody wants to remember that group 3 is the kitchen downlights and group 12 is the alfresco. So C-Bus stores Tags — human-readable names — against networks, applications and groups. In the programming, group 3 gets tagged “Kitchen Downlights”, and from then on that’s what you and we both see in Toolkit, in the Wiser app, and on engraved switch labels.

The tag is purely a label for humans; under the bonnet the device is still using the number. But it makes the system far easier to live with and to service. When a customer rings and says “the alfresco lights won’t come on”, we can open the project, find the tag, and know instantly which group and which output unit to check.

Why switches and lights are logically linked

Pulling it all together, the address Network → Application 56 → Group 3 at Level 255 means: “on this network, lighting, kitchen downlights, full brightness.” A switch sends it; the dimmer assigned to group 3 hears it and ramps to full. No physical one-to-one wire between them — just a shared address.

Understanding this explains a lot of the “magic”:

• One switch, many lights: the button sends to several groups at once.
• Many switches, one light: all those buttons send to the same group.
• Scenes: a single trigger sets a handful of groups to chosen levels.
• Re-allocating control: we can move which switch controls which light without touching a single mains cable.

It’s also why C-Bus diagnostics start with the address, not the wiring. If a light won’t respond, we ask: is the switch sending the right group? Is the output unit assigned to that group? Are they on the same network? Our C-Bus troubleshooting articles follow exactly that logic. If you want to read more about the protocol itself, Clipsal/Schneider Electric publish solid background material at clipsal.com.

The short version

1. Network — the shared C-Bus cable everything lives on.
2. Application — the type of function (Lighting = 56).
3. Group Address — the specific channel linking switches to loads.
4. Level (0–255) — off, dimmed or full brightness for that group.
5. Tags — friendly names so ‘3’ reads as ‘Kitchen Downlights’.

That’s the foundation the whole system is built on, and once it makes sense, everything from scenes to automation becomes a lot easier to picture. If you’re a Melbourne homeowner with a C-Bus system and you’d like us to map out your groups, re-allocate a switch, or just explain what’s behind your walls, the DUKE team is always happy to help — drop us a line via our contact page and we’ll sort you out.

Cheers,
Adam and the DUKE team