Updating Wiser firmware and backing up your configuration

The Wiser Home Controller is the brain of a lot of the C-Bus homes we look after around Melbourne. It holds your scenes, your schedules, your logic, the remote access that lets you check the house from the office — all of it. So when it comes to firmware updates and backups, this is one of those jobs where a little bit of care up front saves you a very long, very expensive afternoon. We’ve been called out to rescue more than one DIY update that went sideways, and almost every time the root cause is the same: no proper backup before the change.

This article walks through how we update Wiser 2 firmware and, just as importantly, how we make sure your configuration is safe before we touch anything. It’s pitched at the advanced end — if you’re a fellow integrator this’ll be familiar territory, and if you’re a homeowner it’ll help you understand exactly what’s going on (and why we’re so fussy about it).

Your PICED project file IS your backup

This is the single most important thing to understand about Wiser. Unlike a lot of controllers that hold their own self-contained backup, the Wiser is programmed and maintained with two pieces of Clipsal software: C-Bus Toolkit (which handles the underlying network — your Group Addresses, output units, switches and so on) and PICED, the Project Integrated Configuration Editor, which builds the Wiser’s web interface, scenes, schedules and logic.

The PICED project file is your backup. There is no magic “download everything” button that captures the lot in one click. The scenes you’ve named, the schedules that bring the outside lights up at dusk, the conditional logic that arms the away mode — that all lives in the PICED project. If you lose that file and the controller has to be wiped or replaced, that configuration has to be rebuilt from scratch. We’ve done those rebuilds. They are not fun and they are not cheap.

Before you touch anything: save the current project

Our golden rule, and we mean every single time, is to pull and save a copy of the current PICED project before any change. Not the version you think is current — the version that’s actually running on the controller right now.

1. Connect to the network. Open C-Bus Toolkit with your network interface online (PCI, CNI or USB) so you’ve got a live link to the installation.
2. Open PICED and transfer FROM the Wiser. In PICED, use the option to retrieve the project that’s currently loaded on the Wiser controller rather than assuming the file on your laptop matches. The unit in the field may have been edited since the last copy you saved.
3. Save it with a clear, dated name. Something like SmithStKew_Wiser_2024-06-01_pre-update.pp. Date it, label it, and store it somewhere it won’t get lost. We keep a copy on our server and a copy on the project laptop.
4. Save the Toolkit project too. Tag it the same way. The Toolkit file and the PICED file are a matched pair — keep them together.

Updating the firmware

There are two routes for updating Wiser 2 firmware, and which one you use depends a bit on the unit and the version you’re moving to.

Through PICED

The cleanest path for most updates is through PICED. With the project open and a connection to the controller, PICED can push a firmware image to the Wiser as part of the transfer process. Because you’re already in the tool you use to manage everything else, this keeps the workflow tidy and lets you transfer your (already backed-up) project straight back afterwards.

Manual Update via the web client

The Wiser also has a Manual Update option under Settings in the controller’s web client. You log in to the Wiser’s web interface, head to the settings area, and upload the firmware file directly. This is handy when you’re applying a specific image supplied by Clipsal/Schneider, or when you’re not in front of a PICED machine.

Use the firmware that matches YOUR controller

This trips people up, so pay attention here. The same catalogue number can ship as different controller variants over the years, and those variants can carry different firmware lines. Grabbing “the latest Wiser firmware” off a forum and flashing it without checking is how units get bricked.

Before you update, identify exactly which variant you’ve got and which firmware line it runs. Check the current version in the web client’s settings page, and confirm the correct firmware against the official Schneider Electric/Clipsal documentation for your specific unit. When we manage an update for a customer, we record the variant and the running version in our notes so there’s never any guessing. If you’re unsure what’s installed, our C-Bus network resources cover how to identify the gear on your system, or just give us a call.

The part everyone forgets: SSL and reconnection

Recent Wiser firmware versions enforce secure SSL/HTTPS connections. This is a genuinely good thing — your connection to the controller is encrypted — but it does change behaviour after an update, and it catches people out constantly.

Here’s what tends to happen: the firmware goes on fine, the lights still work off the wall switches, everyone relaxes… and then someone tries to open the app from their phone and it won’t connect. Nine times out of ten when a customer rings us about this, the controller is perfectly healthy — the app simply needs to reconnect over the new secure connection, or a remote-access link needs re-establishing because the security model changed underneath it.

So treat the security change as part of the job, not an afterthought. After any update that touches the SSL/HTTPS behaviour, expect that the app and web client may need to reconnect, and budget time to sort it on the spot rather than discovering it three days later.

After the update: test everything

An update isn’t finished when the controller reboots. It’s finished when you’ve confirmed everything still works the way the homeowner expects. Work through this every time:

1. Web client. Log back in to the Wiser web interface. Confirm it loads over HTTPS and your scenes and schedules are present and correct.
2. Local app access. Open the app on a phone connected to the home Wi-Fi. Confirm it connects and controls loads. If it won’t connect, re-add the controller / re-enter credentials — the secure connection may have reset the pairing.
3. Remote app access. Get off the home Wi-Fi (use mobile data) and confirm remote access still works. Security changes most often break this, so don’t skip it.
4. Voice integrations. If the home uses Google or Alexa voice control, test a couple of commands. These links sometimes need reconnecting after a security change.
5. Schedules and logic. Spot-check that time-based events and any conditional logic still fire. Confirm the controller’s clock is correct.
6. Re-save the project. Once you’re happy, pull and save a fresh, dated copy of the now-updated project so your backup reflects the new state.

Why we’re so careful about all this

The Wiser is reliable when it’s looked after properly, but it’s also the one device in the system that, if it goes wrong without a backup, can take a home from “fully automated” to “manual light switches and a long rebuild bill” in an afternoon. A disciplined backup-update-test routine turns a nerve-wracking job into a routine one. For the official line on Wiser and C-Bus product support, Clipsal’s own resources at clipsal.com are the authoritative reference.

That’s the way our team handles every Wiser update — back it up, match the firmware to the exact unit, update carefully, then test local, remote and voice before we leave. If you’re a Melbourne C-Bus owner and you’d rather not risk your configuration on a DIY firmware update, or your app stopped connecting after one, drop us a line via our contact page and we’ll get you sorted. Cheers — Adam and the DUKE team.