Buying a home that’s already got Clipsal C-Bus running the lights, blinds and scenes is a genuine bonus — but the system is only as easy to live with as the paperwork that comes with it. Nine times out of ten when a new owner rings us after settlement, the first question we ask is: “Did you get the Toolkit project file?” If the answer is yes, we can have you in full control within an afternoon. If the answer is no, the system still works, but everything from relabelling a switch to adding a new downlight takes longer until we rebuild what should have been handed to you at the front door.
This guide walks through exactly what to ask for when you’re buying (or selling) a house with C-Bus, why the project file matters so much, and how to get proper local support once you’ve got the keys.
The one file that matters most: the C-Bus Toolkit project
C-Bus is a programmed system. Every button on every switch, every scene, every timer and every label lives inside a configuration that an installer built in C-Bus Toolkit and loaded onto the network. That configuration is captured in a project file — typically handed over as a .cbz backup (a compressed archive), which Toolkit restores back into a working .cb3 project.
Inside that one file is the lot:
- Every Group Address and its friendly label — “Kitchen Pendants”, “Master Ensuite”, “Alfresco Blinds” and so on
- Which physical button on which DLT/eDLT switch controls which load, and how it behaves (toggle, dimmer, scene trigger)
- All your scenes and the levels they recall (0–255), plus ramp rates for how gently lights fade up and down
- Timers and schedules — the garden lights that come on at dusk, the away-mode that mimics occupancy
- The structure of the whole network and how it maps to the output units in your switchboard
Without the file, none of that is lost from the running system — the house keeps working exactly as it did. The problem is that all of it is locked inside the hardware in a form that’s tedious to read back out. With the file, your dealer opens it in Toolkit and instantly sees the whole house laid out clearly.
What if the project file has gone missing?
It happens more often than you’d think. The original installer has retired, the file was only ever saved on a laptop that’s long gone, or nobody told the sellers it even existed. The good news: a competent C-Bus dealer can connect to the network and read much of the configuration back off it — the group addresses, current levels, and which units are present. Toolkit’s discovery and scan tools do a lot of the heavy lifting here.
The catch is time. Reading a system back is slower and more painstaking than simply restoring a backup, and some things — especially descriptive labels, the original intent behind a scene, and any logic — have to be re-created by inference and testing. That’s billable hours that a $0 file at settlement would have saved you. So while a missing file is recoverable, it’s worth chasing hard before the sale closes.
Your handover checklist when buying
Before settlement, ask the seller (or their agent) to round up the following. It’s reasonable to make this part of the inclusions conversation, the same way you’d ask for alarm codes or pool-pump manuals.
- The C-Bus Toolkit project file — the .cbz backup. This is the priority. Ideally get it emailed to you as well as left on any controller.
- The original installer’s or dealer’s details. Even just a business name and number lets your new dealer ask the right questions, and sometimes they can supply the file directly.
- Switchboard documentation — circuit schedules, any labelling of which relay/dimmer channel feeds which area, and photos of the board layout.
- The Wiser controller login, if a Wiser Home Controller is fitted. You’ll need the account credentials (and ideally the admin password) to use the app, set schedules and remote access.
- Any user guides or scene “cheat sheets” the household used day to day — handy for understanding what the previous owners set up.
If you’d like a hand knowing what to look for, our C-Bus getting started guides explain the main components in plain English so you can ask informed questions.
Living without the file: what still works, what slows down
Let’s be clear — a C-Bus house with no project file is not a broken house. Press the buttons and the lights come on. The system runs entirely on its own once it’s been programmed; it doesn’t need a laptop, a controller or the cloud to keep working. The friction shows up the moment you want to change something:
- Relabelling a switch after you’ve redecorated or repurposed a room takes a reverse-engineering session first.
- Adding loads — a new pendant, an outdoor circuit, garden lighting — means mapping the existing system before anything new can be tied in cleanly.
- App and Wiser setup is far quicker when the dealer can import the existing project rather than rebuild the device list by hand.
- Scenes and schedules can be tweaked, but understanding the original logic without documentation is guesswork at first.
So the practical answer is: you can absolutely live in the house and enjoy it, but budget for a rebuild of the documentation if the file never turns up.
New owners: engage a C-Bus dealer early
The smartest move once you’ve moved in is to bring a C-Bus dealer into the picture early — ideally before you want to change anything. There are two pieces of “ownership” to transfer:
1. Take ownership of the project file
Your dealer should hold a current, verified copy of your .cbz backup, confirmed to match what’s actually running on your network. If you received a file from the seller, we check it opens and matches the hardware. If you didn’t, we scan the network and build one. Either way, you end up with a known-good master copy.
2. Take ownership of the Wiser account
If there’s a Wiser Home Controller, the app and any remote access are tied to an account that needs to be transferred into your name with a fresh password. You don’t want the previous owners (or their old installer) still holding the keys to your lighting. Our Wiser support articles cover the controller side in more detail.
In Melbourne, DUKE provides exactly this handover service — verifying or rebuilding the project file, securing the Wiser account, walking you through the switches, and then being on the end of the phone for the inevitable “can we add a light over here?” down the track. C-Bus has been around a long time and Clipsal still publish plenty of product and system information, but having a local dealer who knows your specific install is what makes ownership painless.
Keep a copy off-site — don’t trust a single box
Here’s a lesson we’ve learned the hard way on behalf of customers: don’t let the only copy of your project file live on the controller in the cupboard. Hardware fails. Lightning, a power surge, a dead SD card or a controller that simply ages out — and if that box held the only copy of your configuration, you’re back to reading the system off the network.
We always leave our customers with the .cbz backup in at least two places: stored safely by us as your dealer, and a copy you keep yourself — email it to yourself, drop it in your cloud storage, whatever survives a house fire or a fried controller. It’s a tiny file. Treat it like the title deed for your smart home.
A note for sellers
If you’re the one moving out, the kindest thing you can do for the buyer is leave the system documented. Dig out the original installer’s invoice or business card, locate the project file (your installer likely emailed it once, or it’s on the Wiser controller), and write down the Wiser login. It costs you nothing and makes the home far more attractive to anyone who values the smart-home features you’ve enjoyed.
If you can’t find any of it, a quick visit from a dealer to pull a fresh backup before the sale is a small spend that smooths the whole handover. We’re happy to do that as part of a pre-sale tidy-up.
Where to go from here
Whether you’ve just bought a C-Bus home and want it documented properly, or you’re selling and want to leave it in good order, the path is the same: get hold of that Toolkit project file, secure the Wiser account, and have a local dealer who knows the system. If anything feels stuck — a switch that does nothing, a scene that’s misbehaving — our troubleshooting guides are a good first stop.
Thanks for reading — and welcome to the C-Bus club if you’ve just moved in. We’ve handed over and rescued plenty of these systems across Melbourne over the years, and there’s almost always a clean, sensible way forward. If you’d like us to verify your project file, take over your Wiser account or just give the system a once-over, get in touch via our contact page and we’ll sort you out. — Adam and the DUKE team
Frequently asked questions
What is the C-Bus Toolkit project file and why does it matter?
It’s the configuration backup (a .cbz file that restores as a .cb3 project) holding every group address, label, scene, timer and ramp rate for your home. Handing it over at settlement saves a dealer hours of reading the system back off the network, so it’s the single most valuable thing in a C-Bus handover.
Does C-Bus still work if I don't have the project file?
Yes. C-Bus runs entirely on its own once programmed and doesn’t need a laptop, controller or internet to keep working. The file only matters when you want to change something — relabelling switches, adding lights or setting up the app all take longer without it.
Can a dealer recover the configuration if the file is lost?
Largely, yes. A C-Bus dealer can connect to the network and read back group addresses, current levels and the units present using Toolkit. The catch is time — descriptive labels and scene logic often have to be re-created by testing, which costs more than simply receiving the backup.
What about the Wiser controller login when I buy the house?
Ask the seller for the Wiser account credentials and admin password. Once you’ve moved in, have a dealer transfer the account into your name with a fresh password so previous owners and old installers no longer have access to your system.
Where should I store my C-Bus project file?
In at least two places. Don’t rely on the copy sitting on the controller — hardware fails. Keep a copy yourself (email it to yourself or use cloud storage) and have your dealer hold one too, so the file survives a controller failure or power surge.