You've bought a house with C-Bus: assess it before you decide anything

Last reviewed: 18 July 2026

The building report mentioned "C-Bus lighting control", the previous owner left a folder of manuals from 2006, and some of the light switches have more buttons than lights. Most new owners in this position jump straight to a decision — usually either "rip it out" from an electrician who doesn't know the system, or "it's fine" from an agent who's never touched it. Both answers are premature. This page gives you the week-one assessment that tells you what you actually own, and then shows how the results point you at one of three paths: keep it as-is, bridge it into a modern smart home, or replace it.

What you actually own

C-Bus is a wired lighting control system, common in Australian houses built or renovated through the 2000s. The switches on your walls aren't switches in the normal sense: they're buttons on a data bus that tell a controller what to do, and the controller drives the lights. That's why one button can run a "goodnight" scene and why the panel by the door can turn off the whole house.

Here's the part that should reframe the whole decision: the asset is the wiring. Every switch position has data cabling back to a central point, and the lighting circuits are centrally controlled. Installing that wiring in an existing house today means opening walls; you got it included in the purchase price. The electronics on the ends of the wires are replaceable parts. The copper in the walls is the thing a demolition quote throws away.

"It's old" is also not a diagnosis. Wired bus systems age like wiring, not like phones — the fashion moved on, but a healthy installation keeps doing its job. Whether yours is healthy is exactly what the assessment below establishes.

Week one: the four checks

1. Walk the house and test everything. Every button on every panel, written down: what it does, and whether it works. Dead buttons, lights that never respond, scenes that half-fire — the fault list is your baseline, and it changes the conversation with any installer from "mystery system" to "working system with three known faults". If things are misbehaving, the fault patterns are covered in common C-Bus faults and what they mean — and if the trouble started after a blackout, read C-Bus not working after a power outage before assuming anything is broken at all.

2. Find the brain and photograph it. Somewhere — a garage cupboard, the meter board area, a hallway cabinet — there's an enclosure with DIN-rail modules and status LEDs. Photograph everything: module labels, wiring, the lot. Those photos let any C-Bus person quote you sight-unseen, and they're your record of the system before anyone touches it.

3. Hunt for the programming. A C-Bus system's behaviour lives in a project file created when it was commissioned. If the previous owner left a USB stick, CD, or installer's business card in that 2006 folder, you've found the most valuable item in it. With the project file, any competent integrator can read, modify, and extend your system cheaply. Without it, the programming can be recovered from the installation, but you're paying for hours of reverse-engineering before any actual changes. Ask the previous owner directly; ask the original installer if the paperwork names one. Ten minutes of asking can save a four-figure discovery exercise.

4. Find out who can work on it locally. C-Bus is a specialist system: your average sparkie can safely leave it alone but generally can't program it. One phone call to a local automation integrator — "2000s C-Bus install, this many switch panels, do you service it?" — tells you whether support is a normal service call in your area or a capital-city fly-in. That single fact moves the keep/bridge/replace needle more than any spec sheet.

Reading the results: which path fits

Keep as-is suits a system that passed the walk-through, in a house whose lighting behaviour you're happy to live with. Cost of this path: nothing today, occasional specialist service calls when a module eventually fails, and no app or voice control. It's a perfectly sound answer, especially while you settle into the house — nothing about keeping it now forecloses bridging it later.

Bridge it suits a healthy system plus an owner who wants modern smart-home life — automations, voice control, one app alongside everything else in the house. A bridge is a small device that connects the C-Bus network to a modern smart-home hub, so your existing switches and wiring keep doing their job while the lights also become citizens of the new system. The walls stay closed; the panels stay on the walls; you add capability instead of replacing it. This is the path most new owners haven't heard of, and it's usually the best-value one — the wiring you got free keeps working, topped with the features you actually wanted.

Replace it is the honest answer in a narrower set of situations: the assessment found widespread failures, there's genuinely no support within reach, no project file and quotes for recovery come back ugly — or you're gutting the house anyway, in which case the walls are open and the calculus changes completely. Outside those cases, ripping out working wiring to install a wireless system is paying money to trade down in reliability.

The deeper comparison — what C-Bus does better than wireless gear, where it shows its age, what each path costs — is on should you keep C-Bus or switch. This page's job is the sequence: assess first, then choose.

If you're leaning bridge: the questions for the integrator

Keep the specifics generic until someone has seen your system, but walk in with these: Can you work with my existing programming, and what happens if I don't have the project file? Which smart-home platforms can you bridge to, and which do you actually support long-term? What still works if the internet is down? What does the bridge cost installed and programmed — and what would the same outcome cost if I waited until something breaks? Ask, too, what they'd do with your specific fault list from the walk-through; a good integrator folds the repairs and the bridge into one visit.

All of the enclosure work is mains-adjacent and the programming is licensed-installer territory — this is a trade you hire, not a weekend project.

The short version

The C-Bus in your new house is wired lighting control, and the wiring — not the ageing electronics — is the asset you paid for. Before deciding anything, spend week one testing every button, photographing the enclosure, hunting down the project file, and phoning one local integrator. A healthy system points to keep or bridge; bridging adds app, voice, and automations while the walls stay closed; full replacement only earns its cost when the system is genuinely failing, unsupported, or the renovation has the walls open anyway.

General guidance only — C-Bus programming and enclosure work are jobs for a licensed installer or integrator who has seen your actual system.

Just moved in and want the honest read on what you've inherited? Send us your enclosure photos and fault list and we'll tell you whether it's a keeper, a bridge candidate, or genuinely end-of-life. No rip-out you don't need.