Smart plug won’t connect? It’s almost always the 2.4 GHz band

1. Config mode, and the light that proves it

During setup a smart plug creates its own small Wi-Fi network so your phone can talk to it directly and hand over your home network details. It only does that in config mode, and the status light tells you whether it is there. TP-Link documents the pattern for Kasa: a Wi-Fi LED blinking orange and green means the device is in config mode. Smart bulbs signal it differently — a Kasa bulb flashes three times on power-up when it is ready.

If your plug is not showing that pattern, no amount of retrying in the app will help, because there is nothing to connect to. Reset it to return it to config mode — the button and hold time vary by model, so TP-Link's instruction is to look up your specific model's user guide rather than assume. On most plugs it is a press-and-hold on the physical button until the LED changes pattern.

You can verify independently, which is worth doing when the app is being unhelpful. Open your phone's own Wi-Fi settings and look for the device's network: TP-Link names them in the form TP-Link_Smart Plug_XXXX or TP-Link_Smart Bulb_XXXX, where the last characters match part of the MAC address printed on the device label. If that network is listed, the plug is working and advertising correctly, and your problem is in the app or the handover — not the hardware.

A plug bought second-hand or moved between homes is still paired to its previous network and will not enter config mode on its own. Reset it first rather than assuming it is faulty.

2. It is a 2.4 GHz device, and your phone matters

This is the single most common cause of setup failing at the last step. Smart plugs are 2.4 GHz only — they have no 5 GHz radio at all — and TP-Link's guidance is to use the 2.4 GHz band and, if problems persist, to temporarily turn off the 5 GHz band, noting that 2.4 GHz gives longer range anyway. If you hand the plug a 5 GHz network name, it cannot join it and setup fails with no useful explanation.

Your phone's band matters too, which surprises people. Setup involves your phone talking to the plug on 2.4 GHz and then relaying credentials, and a phone sitting on the 5 GHz half of a combined network frequently cannot complete the handover. The reliable workaround is to force the phone onto 2.4 GHz for the duration — either by connecting it to the 2.4 GHz network by name, or by temporarily disabling the 5 GHz radio at the router while you set up.

The lasting fix is to give the two bands different names. TP-Link recommends exactly this: use a different SSID for 5 GHz than for 2.4 GHz, or temporarily turn 5 GHz off. Once the bands are named separately you can point the plug and your phone at the 2.4 GHz one deliberately, and every future smart device you add gets easier rather than harder.

3. Router settings that break smart devices

Some router features that improve life for phones and laptops actively break simple IoT devices. TP-Link names band steering and Smart Connect as known to conflict with Kasa devices — both work by presenting one network name and silently moving clients between bands, which is precisely the behaviour a 2.4 GHz-only device cannot survive. Turning them off, at least during setup, is often the whole fix.

TP-Link also publishes three specific radio settings worth applying when setup keeps failing: switch Wi-Fi encryption to WPA2+AES, set the wireless channel to 1, 6 or 11 rather than auto, and set the channel width to 20 MHz. These are not arbitrary. Mixed-mode encryption such as WPA2/WPA3 confuses older Wi-Fi chipsets, channels outside 1/6/11 overlap their neighbours, and 40 MHz channel width on 2.4 GHz causes trouble for narrow-band devices.

Confirm the whole picture by testing elsewhere. TP-Link's suggestion is to try the device on a different 2.4 GHz network — a phone hotspot works well — because a plug that sets up instantly on a hotspot and never on your home network has told you conclusively that the router is the problem, not the plug. That is the same logic as the hotspot test for a TV that will not join Wi-Fi, and it is just as decisive here.

Guest networks and IoT VLANs isolate clients from each other, so a plug set up on one may be invisible to the phone that set it up. Put it on the main network unless you specifically want it segregated and know how to allow the app through.

4. Phone permissions the app needs

On iPhone and iPad, an app cannot discover devices on your Wi-Fi without Local Network permission, and if it was denied once the app simply never finds anything. TP-Link's guidance is to go to Settings, find the Kasa app in the list, and enable the Local Network option. The same applies to any smart home app on iOS, and it is the first thing to check when an app that used to work stops finding devices after a phone upgrade.

On Android the equivalent is location permission, which the system requires for the Wi-Fi scanning that device discovery depends on. Denying it produces the same result — an app that appears to work but never lists a device. Grant it at least while setting up.

Then rule out a stale app state before anything more drastic. TP-Link suggests force-closing the app, relaunching it and waiting a few seconds before checking whether the device appears. Also disable any VPN on the phone for the duration: a VPN routes traffic away from your local network, so the app cannot reach a device sitting in the same room.

5. When it set up fine and later went offline

A plug that worked for months and then disappeared is a different problem from one that never set up. The most common trigger is a change to the network it was given: a new router, a new ISP box, a changed Wi-Fi password, or a mesh system replacing a single router. The plug is still trying to join a network that no longer exists under those details, and no amount of restarting will help — it needs setup run again.

Before doing that, rule out the simple physical causes. Power-cycle the plug at the socket, check that the socket itself is live and not on a switched-off extension lead, and consider signal strength: a plug behind a sofa, inside a cabinet, or at the far end of the house may have been marginal all along and tipped over when something in the environment changed. Metal furniture and appliance bodies block 2.4 GHz effectively.

If several smart devices went offline at once, stop looking at any of them individually — that is the router or the network configuration. A firmware update to the router that switched Smart Connect back on, or a mesh node placed differently, will take out every 2.4 GHz-only device in the house simultaneously while phones and laptops carry on perfectly.

6. When it is the plug, and what to tell support

The evidence for a hardware fault is specific rather than accumulated. It looks like a plug that will not enter config mode after a documented reset, or that never appears in your phone's Wi-Fi list under its own name, or that sets up successfully on a phone hotspot and then fails identically on two different home networks. A plug that works on a hotspot is not faulty, whatever else is happening.

Check the socket is delivering power before concluding anything, using something ordinary like a lamp. It is worth saying because a smart plug on a switched socket, an extension lead with its own switch, or a circuit controlled by a wall switch will appear completely dead and perfectly innocent — the same trap as a Hue bulb behind a light switch.

When you contact support, lead with the config mode result. Tell them what the status LED does, whether the device's own network appears in your phone's Wi-Fi list, whether your 2.4 GHz and 5 GHz networks share a name, whether band steering or Smart Connect are on, and whether the plug sets up on a phone hotspot. Those five answers separate a plug that is not in config mode from a router configuration problem from genuinely faulty hardware.

Frequently asked questions

Sources and review notes

Checked on September 7, 2026. Compiled by Glitchary from TP-Link’s Kasa support documentation, which is the most specific published guidance for this class of device; the 2.4 GHz, band steering and app permission causes apply across brands, but LED patterns, reset buttons and network names are TP-Link’s and differ elsewhere — check your own manufacturer’s article. Router settings vary by manufacturer and are not covered by TP-Link’s documentation. Glitchary is independent of TP-Link.

• TP-Link: Kasa not connecting? Fix setup issues
• TP-Link: fix Kasa device offline issues
• TP-Link: how to set up a Kasa smart plug