It’s one of the most common calls we get on a Monday morning: “Adam, my screen’s gone black and I can’t control anything from it.” The good news is that nine times out of ten when a C-Touch or Wiser touchscreen goes dark, frozen or unreachable, the underlying C-Bus network is still happily running in the background. That changes everything about how we approach the fix — and it usually means a far simpler outcome than people fear.
This guide walks you through the same diagnostic order our team uses on site. Work through it top to bottom and you’ll either get your screen back or know exactly what’s failed.
First things first: is it the screen or the whole network?
Before you touch anything, walk to a normal wall switch — a Saturn, Neo or DLT/eDLT — and press it. Does the light come on? If your physical switches still operate lights and fans as normal, your C-Bus network, its power supply and the output units in the switchboard are all fine. The fault is isolated to the touchscreen or Wiser controller itself.
This matters because it tells us the pink C-Bus cable is carrying its 36V supply and clock, the 5500PS system power supply is doing its job, and the relays and dimmers are taking commands. The diagram above shows where the Wiser sits on the network relative to those output units — it’s just another unit on the bus, plus a separate mains supply and a network connection.
Check power and the C-Bus connection
A genuinely black screen — no backlight, no logo, nothing — is far more often a lost supply than a dead unit. A C-Touch and a Wiser both need two things to come alive: their own mains-derived supply and a healthy C-Bus connection for the lighting data.
- Mains supply: Many wall-mounted touchscreens and the Wiser Home Controller are powered from a dedicated supply, often via a plug-pack or a circuit in the switchboard. If a breaker has tripped or a plug-pack has failed, the screen simply won’t boot.
- C-Bus connection: The pink Cat5 C-Bus cable plugs into the unit. A connector that’s worked loose — common after cabinetry work or a renovation nearby — can leave a screen partly powered but unable to communicate.
Power-cycle the controller properly
A frozen screen — backlight on but unresponsive, or stuck on a logo — usually clears with a clean reboot. The key word is clean: a quick tap of power often isn’t enough, because these controllers hold a charge and need a moment to fully discharge and reinitialise.
- Isolate the controller’s power. Switch off the dedicated circuit or unplug the supply. If you’re not certain which breaker feeds the screen, stop here and call us rather than guessing at the board.
- Wait a full 30 seconds. This lets the unit discharge completely. Don’t rush it — a two-second flick rarely does the trick.
- Restore power. Switch the supply back on and leave the controller alone. A Wiser or C-Touch can take a minute or two to boot, load its project and reconnect to the bus.
- Re-test. Once it’s settled, try operating a light from the screen. If it responds, you’re done.
If the reboot brings it back but it freezes again within hours or days, that points to either a marginal project file or a unit that’s beginning to fail — note when it happens and how often, as that detail helps us a lot.
Did it go wrong straight after an update?
If the screen died the moment someone transferred a new project or did a firmware update, the new transfer almost certainly didn’t complete cleanly. An interrupted download — a dropped connection, a laptop going to sleep mid-transfer, a power blip — can leave the controller with a corrupt or half-written project and no way to start.
The fix here isn’t a replacement; it’s re-transferring a known-good project. Our team always keeps the last working project file backed up for exactly this reason. We reconnect to the controller via the network interface (a PCI, CNI or USB interface depending on the setup) and re-download the saved project from PICED for Wiser, or C-Bus Toolkit for the lighting side.
Wiser app says “can’t connect”
A black physical screen and a Wiser app that won’t connect are two different problems, even though they feel similar. If the controller itself looks alive but the app on your phone or tablet throws a “can’t connect” error, work through the network side before assuming the hardware has died.
- Confirm you’re on the right network. The Wiser app needs to be on the same Wi-Fi as the Wiser controller for local control. If you’ve added a new router, mesh node or guest network, the app may be sitting on a different subnet.
- Check the Wiser’s IP address. If your router hands out addresses by DHCP and the Wiser’s address has changed, the app may still be looking for the old one. A fixed (reserved) IP address for the Wiser avoids this entirely — it’s how we set them up.
- Match the app and project versions. A Wiser app that’s auto-updated on your phone can fall out of step with an older project on the controller (or vice versa). Mismatched versions are a classic “can’t connect” cause that looks like a hardware fault but isn’t.
- Reboot the router and the Wiser. A clean power-cycle of both — router first, then the Wiser once the network’s back — clears a surprising number of connection gremlins.
Our Wiser articles go deeper on app setup and remote access if you want the full picture. Schneider Electric also publishes the official Wiser documentation if you’d like the manufacturer’s reference — you can find it via clipsal.com.
When it’s genuinely a hardware failure
If you’ve confirmed the rest of C-Bus works, checked the power and C-Bus connection, done a proper power-cycle, and re-transferred a known-good project — and the screen still stays black or won’t boot — then we’re looking at a hardware failure. C-Touch units in particular have a finite life; the displays and internal power circuitry do eventually give out, especially the older models that have been running a decade or more.
This isn’t a disaster. Because your C-Bus network and switches keep working independently, you don’t lose control of your home while we sort a replacement. For ageing C-Touch screens we’ll often recommend moving across to a current Wiser controller or a modern touchscreen, which also brings the app and remote-access features people want these days. We migrate your existing project across so the look and behaviour stay familiar.
A quick recap
- Wall switches still work? The network’s fine — it’s just the screen.
- Black screen? Check power and the C-Bus plug first.
- Frozen? Isolate, wait 30 seconds, restore, give it time to boot.
- Died after an update? Re-transfer a known-good project.
- App won’t connect? Check Wi-Fi, IP address and version match.
- Still dead after all that? It’s hardware — time for a replacement.
Work through these in order and you’ll resolve most touchscreen dramas without anyone climbing into the switchboard. And if you’d rather not — or you’ve hit the hardware-failure end of the list — we’re happy to take it from here.
That’s the same checklist we run on site, and it sorts the vast majority of black-screen calls before we’ve even unpacked the toolkit. If your Melbourne C-Bus screen is still misbehaving after this, get in touch with the DUKE team — we’ll diagnose it properly, restore your backup or fit a modern replacement, and have you back in control. Cheers, Adam and the DUKE crew.
Frequently asked questions
My touchscreen is black but my lights still work from the wall switches — why?
That’s actually good news. If your wall switches still operate lights, your C-Bus network, power supply and output units are all healthy. The fault is isolated to the touchscreen or Wiser controller, not the network, so it’s usually a power, software or hardware issue with that one unit.
How do I properly reboot a frozen Wiser or C-Touch?
Isolate the controller’s power (switch off its dedicated circuit or unplug its supply), wait a full 30 seconds so it discharges completely, then restore power and leave it alone for a minute or two to boot. A quick tap of power often isn’t enough — the clean wait is what clears most freezes.
My screen went black right after a project update. What now?
An interrupted or failed project transfer is the most likely cause. Re-transfer a known-good project from your backup using PICED (for Wiser) or C-Bus Toolkit. This is why we always keep your last working project file — it turns a scary black screen into a 20-minute fix.
The Wiser app says it can't connect — is the controller dead?
Not necessarily. Check that your phone is on the same Wi-Fi network as the Wiser, confirm the Wiser’s IP address hasn’t changed, and make sure the app and project versions match. Mismatched versions and changed IP addresses are common causes that look like hardware failure but aren’t.
When does a black C-Touch screen mean it needs replacing?
If the rest of C-Bus works, you’ve checked power and the C-Bus connection, done a clean power-cycle and re-transferred a known-good project — and it still won’t boot — then it’s a hardware failure. Older C-Touch displays and their power circuitry do eventually fail and need replacing, often with a modern Wiser controller.