Smart home devices that disconnect are the most common reason people give up on home automation. The frustrating part is that they usually work — until they do not, unpredictably, and usually when someone else in the house is trying to use them.
Almost all of these cases trace back to a handful of causes. Work through them in order rather than randomly rebooting things.
First: is it actually Wi-Fi?
Before troubleshooting the network, rule out the alternatives.
Cloud outages. Many devices route through the manufacturer's servers even for local commands. If everything from one brand stops at once while other brands work, the problem is their cloud, not your house. Check the vendor's status page.
Battery. A battery sensor reporting intermittently is usually a battery approaching end of life, not a network fault. Low voltage causes transmission failures well before a device reports itself as flat.
Firmware. A device that started misbehaving right after an update probably has a firmware bug. Check the manufacturer's support forum before disassembling your network.
If several devices from different brands are affected, it is your network. Continue.
Cause 1: the 2.4 GHz and 5 GHz problem
This explains more smart home failures than everything else combined.
Nearly all smart home devices support only 2.4 GHz Wi-Fi. Modern routers broadcast 2.4 GHz and 5 GHz under a single network name and steer clients between them automatically. That is excellent for phones and laptops. It is a persistent problem for IoT devices.
Two failure modes:
Setup fails. The app needs your phone on 2.4 GHz to hand credentials to the device. Your phone is on 5 GHz because it is faster. Setup times out with an unhelpful error.
The device drops later. Band steering tries to move the device to 5 GHz, which it cannot see, and the connection destabilises.
The fix: create a separate 2.4 GHz-only network with its own name — something like HomeNet-IoT — and put every smart device on it. Most routers support this. Some cheap ISP-supplied routers do not, in which case temporarily disabling 5 GHz during setup gets devices connected.
This one change resolves a large proportion of dropout complaints permanently, and makes every future device easier to add.
Cause 2: router client limits
Smart devices use negligible bandwidth. What they consume is connection slots and router memory.
A budget or ISP-supplied router that handled fifteen devices perfectly can become unreliable at forty. The symptoms are exactly what people describe: random dropouts, devices unavailable then fine again, occasional whole-network stalls.
Test it: count your connected clients in the router's admin page. Include phones, laptops, TVs, consoles, printers and every smart device. If you are past thirty on a budget router, this is very likely your problem.
The fix: a better router or a mesh system. This is the single highest-value upgrade in most smart homes, and people usually make it years later than they should.
Cause 3: mesh roaming and band steering
Mesh systems solve coverage but introduce a subtler problem. Smart devices are usually stationary, yet mesh systems periodically re-evaluate which node each client should use. A device sitting equidistant between two nodes can be handed back and forth repeatedly, dropping briefly each time.
Devices with weak radios — cheap plugs and sensors especially — handle this badly.
Fixes to try, in order:
- Disable band steering for the IoT network, or use a dedicated 2.4 GHz SSID as above.
- If your mesh allows it, pin problem devices to a specific node.
- Reduce aggressive roaming thresholds if the setting is exposed.
- Move borderline devices closer to a node, or add a node.
Cause 4: channel congestion
The 2.4 GHz band is crowded, and shared with Bluetooth, microwaves, cordless phones, baby monitors and every neighbour's Wi-Fi. In apartments this is often severe.
Australia permits 2.4 GHz channels 1 through 13. Only 1, 6 and 11 do not overlap with each other, so those are the ones worth using.
What to do: use a Wi-Fi analyser app to see which channels your neighbours occupy, then set your 2.4 GHz radio manually to whichever of 1, 6 or 11 is least contested. Leaving it on "auto" often produces worse results than choosing deliberately, because the router re-evaluates at inconvenient moments.
If you run Zigbee too, it shares the same band. Zigbee channels 15, 20 and 25 sit in the gaps between Wi-Fi 1, 6 and 11. Pairing Wi-Fi channel 1 with Zigbee channel 25, or Wi-Fi 11 with Zigbee 15, keeps them out of each other's way.
Cause 5: signal quality, not signal strength
A device showing three bars can still perform badly. Strength and quality are different things — interference degrades quality without reducing strength.
Common physical culprits in Australian homes:
- Double brick and rendered walls attenuate 2.4 GHz heavily. Older inner-city housing is much harder than modern lightweight construction.
- Foil-backed insulation and sarking in roof spaces acts as a partial shield, which matters for devices in ceilings or attics.
- Metal enclosures. A device inside a metal meter box or behind a stainless fridge is fighting a losing battle.
- Water. Fish tanks, water tanks and hot water systems absorb 2.4 GHz effectively.
Outdoor cameras are the usual casualty — the signal has to leave the house through a wall, and the mounting point is often chosen for viewing angle rather than reception.
A note on NBN and upload speed
If your cameras are uploading continuously and your video calls or streaming suffer, the issue may be upload bandwidth rather than Wi-Fi.
Several NBN technologies, particularly FTTN, deliver modest upload speeds. Two or three cameras streaming continuously to the cloud can consume a meaningful share of it. The symptom looks like general internet slowness rather than a camera problem.
Fixes: reduce camera upload resolution, switch cameras to event-triggered rather than continuous recording, or move to local recording so footage never leaves the house.
Working checklist
- Rule out cloud outages, batteries and firmware.
- Create a dedicated 2.4 GHz SSID for smart devices.
- Count your clients; upgrade the router if you are past thirty on budget hardware.
- Disable band steering for IoT, or pin problem devices to a node.
- Set 2.4 GHz manually to channel 1, 6 or 11, whichever is quietest.
- If you run Zigbee, move it to a channel that does not overlap.
- Address physical obstructions for the remaining stragglers.
Most people stop after step two, because that is where the problem usually was.
