Hi! We’ll get your IoT devices that only work on 2.4 GHz connected properly to your Wi-Fi. A couple of details will help me give you exact steps.

• What kind of smart home devices are we talking about (smart plugs, light bulbs, cameras, thermostat, etc.)?
• Do you know the router or mesh system model (for example ASUS, TP-Link, Eero, Orbi, UniFi, ISP-supplied box)?
• On your phone, do you see one combined Wi-Fi name (same SSID for 2.4 and 5 GHz) or separate names like “Home-2G” and “Home-5G”?

Most IoT devices support only 2.4 GHz Wi-Fi, but modern routers try to move phones to 5 GHz for speed. That can make the app say “cannot find 2.4 GHz network” or “smart plug only supports 2.4 GHz” during pairing. We’ll make sure your phone and the device are both on the same 2.4 GHz network, even with a dual-band or mesh router.

That’s a classic situation after upgrading routers.

Most smart plugs, bulbs, and Wi-Fi cameras are 2.4 GHz only. They don’t understand 5 GHz at all. Your new router is likely using a single SSID with band steering / Smart Connect: it advertises both 2.4 and 5 GHz under one name and automatically pushes phones to 5 GHz for speed.

During setup, the app usually has your phone create a temporary Wi-Fi link directly with the IoT device. If your phone is on the 5 GHz band and the device is 2.4 GHz only, they’re technically on different radios and the pairing fails — even though the network name and password look correct.

The good news: we don’t need new devices. We’ll either:
• temporarily force everything to 2.4 GHz only while you add devices, or
• create a separate 2.4 GHz IoT SSID so smart devices always use 2.4 GHz but your other gadgets can still enjoy 5 GHz speed.

Let’s start by checking if your router lets us separate the 2.4 and 5 GHz Wi-Fi names.

Perfect, that “Smart Connect” toggle is exactly what we need.

Step A — Force a 2.4 GHz network for IoT setup
1) Open the TP-Link app or web interface and go to the Wireless / Wi-Fi settings.
2) Turn Smart Connect OFF. This usually reveals separate options for the 2.4 GHz and 5 GHz bands.
3) Give the 2.4 GHz SSID a simple, unique name; for example: Home-IoT-2G. Keep the 5 GHz SSID as something like Home-5G so you can tell them apart.
4) Make sure security on the 2.4 GHz network is set to WPA2-PSK (AES) or WPA2/WPA3 mixed. Many older IoT devices fail on WPA3-only or weird enterprise modes.
5) Save/apply changes and wait 1–2 minutes for the router or mesh nodes to broadcast the new SSIDs.

Next, on your phone, manually select and connect to Home-IoT-2G (2.4 GHz) and stay on that band while we re-add a couple of devices.

Good progress — your phone is now definitely on 2.4 GHz Wi-Fi, which is a big piece of the puzzle. A few more details can cause that last-step failure:

• Some IoT devices are picky about Wi-Fi names and passwords. Avoid emojis and very long SSIDs or passwords while setting them up.
• Make sure the 2.4 GHz band isn’t set to “802.11n-only”; many cheap smart plugs want 802.11b/g/n mixed and a 20 MHz channel width.
• Place the plug or bulb near the router for onboarding; their antennas are weak and struggle at the edge of coverage, even though 2.4 GHz has better range in general.

Step B — Clean re-pair of one 2.4 GHz device
1) Delete / remove that smart plug from its app if it shows up half-added.
2) Factory-reset the plug (usually holding the button until the LED blinks rapidly).
3) Confirm your phone is still on the 2.4 GHz SSID and that mobile data and VPN are temporarily turned off.
4) Start the app’s add-device wizard again and carefully pick the 2.4 GHz Wi-Fi name and password.

Try that on one plug so we can see if it successfully joins the 2.4 GHz network now.

Great — that confirms the 2.4 GHz only smart devices can live happily on the new router when the band and settings are right. The outdoor camera is a slightly different challenge: range and interference.

Even though 2.4 GHz travels further than 5 GHz, many IoT Wi-Fi radios are very low power. Add walls, glass, metal, and neighbor networks, and the signal at the edge of your yard can be borderline.

Step C — Stabilize 2.4 GHz coverage for distant IoT devices
1) In the router’s 2.4 GHz settings, lock the channel to 1, 6, or 11 instead of “Auto” and keep channel width at 20 MHz to reduce interference.
2) If you have a mesh system or extra node, place one closer to the yard so the camera sees a strong 2.4 GHz signal.
3) Avoid mounting the camera directly behind metal gutters or thick brick; a slight reposition can dramatically improve 2.4 GHz signal.
4) After moving things, power-cycle the camera so it reconnects with the stronger access point.

Once the camera sees a solid 2.4 GHz signal, it should stop dropping, even on a busy dual-band or mesh Wi-Fi network.

Yes — now that everything is online, we can make the layout cleaner so you don’t fight the “IoT works only on 2.4 GHz” problem every time you add a device.

The general strategy is:
• Keep a dedicated 2.4 GHz IoT SSID for smart plugs, bulbs, sensors, and cameras.
• Let phones, laptops, consoles, and TVs primarily use the faster 5 GHz (or 6 GHz) band.
• Make sure your smart speakers or hubs (Alexa, Google Home, HomePods, Home Assistant) can see both networks on the same local network so they can talk to the IoT devices.

You’ve already separated the bands, which is perfect. Next we’ll tidy security and naming so new 2.4 GHz only devices join smoothly and safely.

Great question — small tweaks now will save you a lot of headaches later.

Step D — Make your 2.4 GHz IoT network “set and forget”
• Leave the 2.4 GHz SSID and password stable. Don’t change them unless you have to; IoT devices hate frequent Wi-Fi changes.
• Use WPA2-PSK (AES) security; if WPA3-only is enabled, some older smart plugs will refuse to connect.
• Keep AP isolation / client isolation OFF if you want phones, hubs, or voice assistants to control those devices on the same LAN.
• Consider setting DHCP reservations for important IoT devices (cameras, door locks), so they always get the same IP and are easy to manage from apps or a controller.
• If your router supports an “IoT” or “guest” network mode, you can place 2.4 GHz smart devices there with internet access but limited access to your PCs for extra security, as long as your smart home hub is allowed to reach them.

With this setup, future 2.4 GHz only smart home devices should connect first try: just connect your phone to the 2.4 GHz SSID during onboarding, add the device, then you can hop your phone back to the faster 5 GHz network.

You’re in good shape now. When shopping for more smart home gear, a few quick checks will keep things smooth:

• Read the specs and confirm whether the device is 2.4 GHz only or supports both 2.4 and 5 GHz.
• Prefer brands that clearly mention setup with dual-band or mesh Wi-Fi; they tend to handle modern routers better.
• If you move to Matter, Thread, or Zigbee devices later, you’ll offload some Wi-Fi congestion and keep 2.4 GHz Wi-Fi free for things that really need it.

If you ever change routers again and run into “IoT device won’t connect to Wi-Fi” messages, you can open a chat with an expert and we’ll walk you through splitting bands and tuning 2.4 GHz for your smart home.

Any time! Quick recap: most IoT and smart home devices only work on 2.4 GHz Wi-Fi. On a dual-band or mesh router, you fix frequent pairing failures by:

• splitting 2.4 and 5 GHz into separate SSIDs or using an IoT-only network,
• putting your phone on the 2.4 GHz network during setup,
• using simple WPA2 security and mixed 802.11b/g/n mode, and
• improving 2.4 GHz coverage and channels for outdoor or distant devices.

If a friend says “my smart plug only connects to 2.4 GHz and my new router broke everything”, you can share this checklist — or just start a chat with an expert and we’ll fix it live together.