You have inherited a C-Bus house

You bought a house with a lighting system nobody explained. The switches have too many buttons, one of them does nothing, the computer that ran it is long gone, and the electricians you have called do not want to know. This page is the explanation nobody gave you.

There is a specific and surprisingly common situation this page is written for. A house built or renovated in Australia between roughly 2000 and 2015 was fitted with Clipsal C-Bus. The installer has since retired, moved on, or vanished. The PC that ran it died years ago and went to the tip. Half the lights work, one panel does nothing, and every electrician who looks at it says the same thing: rip it out and start again.

Almost none of that advice is based on an examination of your system. It is based on the fact that the person giving it cannot help you. Those are very different statements, and confusing them costs Australian homeowners a great deal of money every year.

What C-Bus actually is

C-Bus is a wired control system. The important thing to understand is that your wall switches are not switches. They are small networked devices that send a message over a dedicated data cable. Separate units, usually mounted on a DIN rail inside an enclosure in a garage or cupboard, receive that message and do the actual switching of power to the lights.

Everything else follows from that split. It is why one button can run a whole-house scene. It is why a switch by the front door can turn off the bedrooms. It is why the system can run schedules. And it is why, when something fails, the fault is either on the sending side or the receiving side, which is what makes it diagnosable.

The wall switches

Input units. They send messages. They do not carry the power to your lights.

The enclosure

Output units: dimmers and relays on a rail, which do the switching. Plus a network power supply that keeps the whole bus alive.

The pink cable

The C-Bus network, carrying both data and low-voltage power between everything. Commonly a pink Cat5-style cable in Australian installs.

The lighting circuits

Ordinary mains wiring, running from the output units to your lights. This is the part that has real value.

The project file

A file on a computer somewhere describing how it was all configured. This is the part that usually went missing.

The thing nobody tells you: the wiring is the asset

This is the single most important idea on this page. In a C-Bus house, every switch position has data cabling running back to a central point, and the lighting circuits are centrally controlled. Installing that in an existing house today means opening walls and ceilings. You got it included in the purchase price of the house.

The electronics on the ends of that wiring are replaceable parts, like the components in any system. A dimmer module is a part. A wall switch is a part. A power supply is a part. What is not replaceable at any sensible price is the copper in your walls and the centralised topology it creates, and a demolition quote throws exactly that away.

So when someone quotes you to remove C-Bus and install a wireless system, understand what is being proposed: discarding an expensive wired infrastructure to install something that runs on batteries and radio. There are situations where that is the right call. "The electronics are old" is not one of them.

"It's old" is not a diagnosis

Wired bus systems age like wiring, not like phones. There is no software subscription that lapses, no cloud service to be discontinued, no app that stops being updated. A C-Bus network from 2006 that is working today is not on borrowed time; it is doing what it was engineered to do. Components fail individually over the years, and they get replaced individually.

What has genuinely dated is the interface. C-Bus predates smartphones, and a system from that era has no app, no voice control and no remote access unless someone added it. That is a real limitation, and it is a fair reason to want something more. It is a different proposition from the system being worn out, and it should be quoted as an upgrade rather than a rescue.

The orphaned-system problem, properly explained

Here is what actually happened to you. When your system was commissioned, the installer used software called C-Bus Toolkit to configure every unit and saved the result in a project file. That file is the map of your system: every unit, every group, every scene, with the names a human typed in. It lived on the installer's laptop and possibly on a PC in your house.

The installer left. The PC died. The file went with them. Your system carried on working perfectly, because the programming is stored in the units themselves, out on the network, not in the file. What you lost was not the system's brain. It was its documentation.

That distinction is the whole ballgame, and here is why: the programming can be recovered by scanning the live network. Toolkit can interrogate every unit and rebuild a working project file that describes your system accurately. What the scan cannot recover is the naming, because a unit reports its address, not the fact that it drives the kitchen pendants. Putting the names back means somebody walking your house, operating each channel and writing down what lit up. That walk is most of the labour, and it is a one-off.

• Recoverable: every unit on the network, its address, its type, its configuration, which channels drive what, and the scene structure.
• Recoverable with legwork: the human-readable names, by operating each channel and observing which lights respond.
• Not recoverable by scanning: custom logic that ran on a touchscreen or PC rather than in the network units. If that machine is gone, that behaviour must be rebuilt from a description of what it used to do.
• Worth searching for first: the original file. An hour of looking regularly saves a four-figure recovery.

Before you spend anything: look for the file

In rough order of success rate: the folder of manuals and warranties left with the house; any old computer that came with the house, including a dead one, because the drive is usually fine; the previous owner, asked directly by email so they can forward an attachment; the original installer, if any paperwork or a sticker inside a cupboard names them, since many keep old project files indefinitely; and your conveyancer's file, which sometimes carries handover documents nobody read.

Do not open the enclosure yourself to look for a disc taped inside the door. Ask whoever does the work to check when they are in there.

Your realistic options

Do nothing

Entirely valid if it works. A healthy C-Bus system needs no maintenance schedule. The risk you carry is that the day something fails you start from zero, with no file and no relationship with anyone who can help.

Get it documented

Have the network scanned and the project file recovered while nothing is wrong. Converts an opaque system into a documented one, makes every future job cheaper, and travels with the house when you sell. The best value move for most owners.

Repair what is broken

Fix the specific faults. Usually one or two modules and some programming. Far cheaper than owners expect once someone has actually diagnosed it rather than guessed.

Repair and modernise

Keep the wiring and the switches, and add a modern interface layer on top so you get app or voice control without opening walls. A genuine upgrade conversation, and a separate one from a repair.

Replace it

Honest in a narrow set of cases: widespread confirmed failures, genuinely no support reachable, or a renovation with the walls open anyway. Outside those it is paying to trade down.

How to find someone who can help

Search for automation integrators, not electricians, and use the trade's words: C-Bus programming, C-Bus commissioning, Clipsal C-Bus service. Understand that you may need two trades: the licensed electrical work, which any competent electrician can do, and the programming, which most cannot. A job that gets only the first half leaves you with a new switch that does nothing.

Ask on the phone: do you have Toolkit and a PC interface; how do you handle a system with no project file; and will I get a copy of the file afterwards. The answers sort the field quickly. There is a fuller version of this in who can actually reprogram a C-Bus system.

Where to start today

Three things, in order, none of which cost anything. Walk the house and write down what every button does and whether it works. Look at the indicator LEDs on the plates while you do it, because they tell you which half of the system is unhappy. Then spend an hour looking for the project file.

With those three done you have converted "a mystery system nobody will touch" into "a documented system with three known faults", which is a different conversation with anyone you call. If you want the faults narrowed down further, the fault diagnoser takes what you observed and gives you a specific verdict.

Last reviewed: 14 August 2026. General guidance only, and no substitute for someone competent looking at your actual system. All work on fixed wiring, switchboards and enclosures is licensed electrical work.