It’s one of the more common calls we get: “The Wiser app’s spinning, it can’t find the controller, the lights worked yesterday.” Nine times out of ten it’s something simple — a phone that’s dropped to mobile data, a router that’s reshuffled its IP addresses overnight, or the wrong app installed altogether. Let’s walk through it the same way our team does over the phone, starting with the basics and working towards the things only we can sort.
Start with the obvious basics
Before you go digging into network settings, rule out the three things that catch most people out:
- Your phone is actually on the home Wi-Fi. The Wiser app talks to the controller over your local network when you’re at home. If your phone has quietly dropped onto 4G/5G or a neighbour’s Wi-Fi, the local connection will fail. Open your phone’s Wi-Fi settings and confirm you’re joined to your own network.
- The controller has power. The Wiser Home Controller lives in or near your switchboard. Check it’s powered up — there should be a power indicator showing it’s alive. If the whole switchboard area lost power or tripped, that’ll take the controller with it.
- Its network link is active. The Wiser connects to your router either by an Ethernet cable or, on some setups, Wi-Fi. If it’s cabled, check the little link light on the controller’s network port and at the router. A dislodged or chewed cable is more common than you’d think.
Did you install the right app?
This trips people up regularly. Clipsal/Schneider have released more than one app with “Wiser” in the name. The C-Bus Wiser Home Controller (the second-generation unit we typically install) uses the Wiser 2 app — not the newer “Wiser by SE” app that’s aimed at Schneider’s residential Wi-Fi products. If you recently changed phones or got prompted to “upgrade”, it’s worth checking you’ve got the correct one for your controller. The wrong app will simply never see your hardware. If you’re unsure which controller you’ve got, our Wiser help section covers the differences.
If it fails at home (local connection)
When the app can’t connect even while you’re standing in your own lounge room on your own Wi-Fi, the issue is almost always the local network path. The most common cause is an IP address change.
The Wiser controller has an IP address on your home network — think of it as the controller’s street number. Your router hands those numbers out, and if the router was rebooted, replaced, or just reorganised its address pool, the controller may have ended up with a different number than the app expects. The app then knocks on the old address and gets no answer.
- Reboot the router and the controller. Power both off, wait 30 seconds, bring the router up first, then the controller. This clears the vast majority of transient drops and gets everything re-registered cleanly.
- Confirm the controller’s IP. Log into your router’s admin page and look at the list of connected devices (often labelled “DHCP clients” or “attached devices”). You should see the Wiser listed with an IP. If it’s there, the controller is alive and on the network — the problem is the app pointing at the wrong place.
- Re-enter the address in the app. In the Wiser 2 app’s connection settings, make sure the local IP matches what the router is now showing. Save and reconnect.
If it works at home but not when you’re out
This is a completely different problem, and it’s important to separate it from the local fault above. If the app connects perfectly on your home Wi-Fi but goes dead the moment you leave the house, the local side is fine — it’s the remote (cloud/WAN) path that’s broken.
Remote access relies on a chain of things working together:
- Port forwarding on your router, sending the external HTTPS request through to the controller.
- A dynamic DNS service or your WAN IP so the app can find your home from the outside world.
- The correct external HTTPS port matching what’s configured in the controller and the app.
If your internet provider changed your public IP address (very common with home broadband), the app may be trying to reach an address that’s no longer yours. Likewise, a new router won’t carry over the old port-forwarding rules.
- Confirm it really is a remote-only issue by testing on home Wi-Fi (works) then on mobile data (fails). That tells us it’s the WAN path, not the controller.
- Reboot the phone and reconnect. When the app gets stuck switching from local to remote mode, a phone reboot followed by reopening the app forces it to re-establish the connection cleanly. This is a well-known workaround.
- Re-enter the WAN IP or remote URL in the app’s remote-access settings if your public address has changed and you’re not running a dynamic DNS service.
The reliable reset sequence
If you’re not sure whether it’s local or remote, this clean sequence clears most transient faults regardless of cause:
- Close the Wiser 2 app completely (swipe it away, don’t just minimise).
- Reboot your router, wait for it to come fully back up.
- Power-cycle the Wiser controller and give it a couple of minutes to boot — it takes longer than a phone.
- Reboot your phone.
- Confirm the phone is on home Wi-Fi, then reopen the app.
Roughly two out of three “can’t connect” jobs are solved right here without anyone coming out.
When it’s a job for us
If you’ve worked through everything above and the app still won’t talk to the controller, a couple of deeper causes remain:
- Firmware. An out-of-date controller can lose compatibility with newer app versions, particularly after a phone OS update. Bringing the firmware up to date often restores the connection, but it needs to be done carefully so the project and schedules aren’t lost.
- Remote access was never configured. Plenty of systems were only ever set up for local use. If you’ve recently started wanting to control things while you’re away and it’s never worked, there’s nothing to “fix” — it simply needs configuring for the first time.
- A failed network interface or controller fault. Less common, but if the controller isn’t showing on the router at all after a reboot, the hardware may need checking.
If you’ve tried the basics and the reset sequence and you’re still locked out — or you want remote access set up properly the first time — that’s exactly what we do. Drop us a line through our contact page and tell us whether it’s failing locally, remotely, or both; that one detail saves us (and you) a heap of time. We’re Melbourne-based and happy to sort it.
Cheers,
Adam and the DUKE team
Frequently asked questions
Why does the Wiser app work at home but not when I'm out?
That points to the remote access path rather than the controller itself. Remote control relies on port forwarding, a dynamic DNS or your current WAN IP, and the correct external HTTPS port. If your internet provider changed your public IP or your router was replaced, that chain breaks. Reboot your phone and reopen the app first; if it still fails, the remote access likely needs reconfiguring.
Which Wiser app do I need for my C-Bus controller?
For the C-Bus Wiser Home Controller you need the Wiser 2 app, not the newer ‘Wiser by SE’ app, which is for Schneider’s residential Wi-Fi products. Installing the wrong one means it will never find your hardware. If you’re unsure which controller you have, our Wiser help section explains the differences.
The app can't connect at home even on my Wi-Fi. What's wrong?
This is usually an IP address change. Your router may have given the controller a different address than the app expects. Reboot the router and controller, then check your router’s connected-devices list to find the controller’s current IP, and re-enter it in the app’s connection settings. Setting a fixed IP for the controller stops it recurring.
Will rebooting the Wiser controller lose my settings or schedules?
A normal power-cycle reboot does not erase your project or schedules — it just restarts the device. The risk only comes with firmware updates or factory resets, which should be done carefully. If a firmware update is needed we handle it so nothing is lost.