How to safely reboot or power-cycle your C-Bus system

Nine times out of ten when a customer rings us saying “the lights have gone weird” or “my Wiser app won’t connect”, the fix is a lot gentler than people expect. Before anyone starts flicking breakers in the switchboard, there’s a sensible order to work through — and most of it you can do yourself from the couch. This article walks through how to reboot or power-cycle a C-Bus system the right way, from the least-disruptive step to the full cold restart.

The golden rule: start small. A glitchy controller or a frozen app almost never means the whole C-Bus network needs a reset. We’ll build up from a simple app reboot to a complete power-cycle, and we’ll be very clear about which jobs are safe for you and which ones are licensed-electrician work.

Start with the least-disruptive fix: reboot the controller, not the network

C-Bus is a distributed system. The brains aren’t in one box — every input unit (your Saturn, Neo or DLT/eDLT switches) and every output unit (relays and dimmers) carries its own logic and keeps working even if the touchscreen or app falls over. So if the symptom is “the app is spinning” or “the C-Touch screen is frozen” but the wall switches still work, the problem is almost certainly the controller, not the C-Bus network itself.

In that case, reboot just the misbehaving device:

• Wiser Home Controller: a power-cycle of the Wiser is usually all it takes. If it’s on a plug-pack or accessible switched outlet, switch it off for about 20–30 seconds, then back on. Give it a couple of minutes to boot and reconnect to your network before you test the app again.
• C-Touch / Wiser touchscreen: follow the on-screen restart option if there is one, or cycle its power the same way.
• App on your phone: before you touch any hardware, fully close the app and reopen it, and check your phone is actually on the home Wi-Fi (not 4G/5G). A surprising number of “my Wiser is broken” calls are just the phone sitting on mobile data.

When a full C-Bus power-cycle is justified

If the whole network is misbehaving — switches across multiple rooms unresponsive, levels stuck, or units clearly not talking to each other — then a complete power-cycle of the C-Bus system power supply is the next step. The aim is to fully de-energise every unit so the network voltage drops to zero, then let everything re-initialise cleanly from cold.

This is where we have to draw a firm line. The C-Bus pink Cat5 cable itself is low-voltage SELV and perfectly safe to handle. But the system power supply (such as a 5500PS), the relays and dimmers, and the circuits feeding them all live inside the switchboard and run on 230 V mains. Isolating those circuits is licensed-electrician work.

The power-cycle procedure (electrician or DUKE technician)

1. Identify the C-Bus supply circuit. At the switchboard, locate the breaker feeding the C-Bus system power supply (and any separately-fed output units, depending on how the board was wired). On a well-labelled board this is straightforward; on an older install we often have to trace it.
2. Isolate it. Switch off the C-Bus supply circuit. The C-Bus network voltage (normally sitting around the mid-30s of volts DC on the bus) will collapse and every unit will de-energise.
3. Wait about 30 seconds. This is the part people rush. Give it a genuine half-minute so capacitors fully discharge and every unit truly powers down. A two-second flick often isn’t a real reset — units can ride through it and the “reboot” achieves nothing.
4. Restore power. Switch the circuit back on. The power supply re-energises the bus and all the units begin their start-up and re-initialisation.

Let it settle before you test

After you restore power, resist the urge to start tapping switches straight away. Give the system a good minute. During that window:

• The network voltage settles and stabilises across the bus.
• Units complete their start-up and re-establish communications.
• The network clock re-synchronises — important if you rely on scheduled events or timed scenes. If you test scenes before the clock has settled, you might wrongly conclude they’re broken.

Patience here saves a lot of false alarms. We’ve watched plenty of people declare a reboot “didn’t work” because they hammered the wall switch ten seconds after power came back.

Verify it actually worked

Once you’ve given it that minute, check the system has genuinely recovered rather than just assuming it has:

• Indicator LEDs: the status lights on the power supply and units should be back to their normal steady state — not flickering, flashing erratically or off. A unit’s indicator behaviour tells you whether it has network and a healthy clock.
• Wall switches: walk around and press a few switches in different rooms. They should respond promptly with their normal ramp.
• Scenes and automation: trigger a known scene (an “All Off”, a “Welcome” or similar) and confirm it runs as expected.
• The controller and app: open the Wiser app and confirm it connects and reflects the real state of the lights.

If all of that checks out, you’re done — the power-cycle has cleared whatever transient gremlin caused the fault. If you’re setting up or revisiting your controller after this, our notes on the Wiser Home Controller are worth a read.

If a clean power-cycle doesn’t fix it

Here’s the important bit: do not sit there power-cycling over and over. If one proper full power-cycle — isolate, wait 30 seconds, restore, wait a minute — doesn’t bring the network back to normal, the problem isn’t something a reboot can clear. Repeated cycling just stresses the gear and wastes your evening.

At that point the fault is more likely to be one of these, and it’s where our team takes over:

• Programming corruption or drift: the fix is a re-download of the project to the affected units from C-Bus Toolkit, not another reboot.
• No network clock, or multiple clocks fighting: exactly one unit should be generating the network clock. If that’s been lost or duplicated, scenes and timing go haywire. We check and correct this in Toolkit.
• Network burden missing or units over the limit: the bus needs the correct burden enabled and the unit count/cable length within spec, or the voltage sags and comms become unreliable.
• A failed unit or supply dragging the network down.

These are all things we diagnose with the laptop connected via a PCI or CNI interface — a clock-and-burden check and, if needed, a re-download. There’s more background on this in our C-Bus network articles. If you want to read up on the official side of the hardware, Clipsal’s own resources at clipsal.com are a good reference.

Quick summary

1. App glitch or frozen screen → reboot the controller/app only.
2. Whole network misbehaving → a single, proper full power-cycle (electrician work at the switchboard).
3. Wait ~30 seconds off, then ~1 minute after restore.
4. Verify LEDs, switches and a scene before calling it fixed.
5. Still broken? Stop cycling — it needs a re-download or a clock/burden check.

That’s the safe, sensible order we use ourselves on service calls. The app-level reboots are yours to try anytime; the switchboard work belongs to a licensed electrician — and if you’re in Melbourne, that’s us. If a power-cycle hasn’t sorted it, don’t keep wrestling with it: get in touch with the DUKE team and we’ll get your C-Bus system properly diagnosed and back to normal.

Cheers,
Adam and the DUKE Electrical Group team.