2.4 GHz vs 5 GHz: which Wi-Fi band IoT devices need

The 2.4 GHz vs 5 GHz question comes down to reach against capacity. A 2.4 GHz signal travels further and gets through walls and floors better, but the band is narrow, slower and shared with a lot of other equipment. A 5 GHz signal carries more data and has far more room, but it fades faster as it passes through a building. For smart home and IoT devices the choice is mostly made already, because most of them only have a 2.4 GHz radio. This article covers how the two bands differ, why IoT hardware sticks to 2.4 GHz, why pairing so often fails on a dual-band router and how to fix it, and where Zigbee, Thread, Bluetooth, 6 GHz and Wi-Fi HaLow fit.

2.4 GHz vs 5 GHz at a glance

For IoT, the rows that matter are range and channels. Speed rarely does, because a smart plug or a temperature sensor sends a few hundred bytes at a time and would work on the slowest Wi-Fi ever standardized. Cameras are the exception.

Range and walls

Higher-frequency signals lose more strength over the same distance, and they lose much more when they pass through brick, concrete, plasterboard with foil backing, floors, and anything containing water, including people. Metal blocks both bands. In practice a 5 GHz network is usually the stronger of the two in the same room as the router, and the weaker one two rooms and a floor away, where the 2.4 GHz network is often still usable.

That matters more for IoT devices than for phones. They live at the edges of a home: in the garden, the garage, the porch, a meter cupboard or the far bedroom. They have small, cheap antennas and modest transmit power, so they have less signal margin to spare.

Reach cuts both ways. Your neighbors’ 2.4 GHz networks reach into your home too, which is why the band is so crowded in flats and terraced streets. The shorter reach of 5 GHz keeps most of the neighbors out.

Channels, widths and congestion

The 2.4 GHz band runs from 2.400 to 2.4835 GHz, a total of 83.5 MHz. Wi-Fi divides it into channels whose centers are 5 MHz apart, numbered 1 to 11 in North America and 1 to 13 in most other regions. A Wi-Fi signal is about 20 MHz wide, though, so a network on one channel number spills across its neighbors on either side. Only channels 1, 6 and 11 sit far enough apart not to overlap. Networks on the same channel take turns; networks on partly overlapping channels, such as 1 and 3, cannot coordinate and treat each other as noise, which is worse.

Wi-Fi 4 and later can bond two 20 MHz channels into one 40 MHz channel. At 2.4 GHz that takes up about half the band and many IoT devices do not support it, so 20 MHz is the right width there.

The 5 GHz band is much larger. Its channels are numbered from 36 upwards, and even at 20 MHz there are many more that do not overlap, which is why routers bond them into 40, 80 or 160 MHz channels for speed. Some of the channels in the middle of the band are shared with weather and other radar, so a router using them must apply dynamic frequency selection (DFS): it listens for radar and moves the network to another channel if it hears any. That can make a 5 GHz network briefly disappear.

Why most IoT devices only support 2.4 GHz

The chips came first. The low-cost Wi-Fi system-on-chip families that most smart plugs, bulbs, switches and sensors are built on, including the widely used ESP8266 and most of the ESP32 range, were 2.4 GHz only for years. Dual-band parts exist, but they are newer and less common in cheap devices.

One band is simpler to build. A single-band design needs one radio front end and one antenna tuned for one frequency range. Dual-band adds parts, board space and testing, for a device that gains nothing from the extra speed.

Range decides whether the device works at all. A plug in the garage that connects reliably on 2.4 GHz and drops out on 5 GHz has only one useful band.

Power follows from range. A battery device spends most of its energy while its radio is awake. A strong link needs fewer retries, so the device finishes sending and goes back to sleep sooner. Wi-Fi 6 on 2.4 GHz adds target wake time, which lets a device agree with the access point when it will next wake up, and that helps battery devices further.

The exceptions are devices that move a lot of data: cameras, video doorbells, displays and streaming hardware. Many of these are dual-band, though a camera at the bottom of the garden may still do better on 2.4 GHz. If you are still deciding whether a device should use Wi-Fi at all, the Zigbee, Z-Wave and Wi-Fi comparison sets out when a low-power mesh radio is the better choice.

Why a device will not pair when your phone is on 5 GHz

Most routers and mesh systems now broadcast one network name on both bands and use band steering to move dual-band clients onto 5 GHz. Your phone ends up there, and pairing a 2.4 GHz device from it can then fail in three ways.

Some setup methods need the phone and the device on the same band. In the older quick-pairing modes, the phone encodes the network name and password in a pattern of Wi-Fi traffic that the unconfigured device listens for on 2.4 GHz. With the phone on 5 GHz, the device often hears nothing it can use.

Some setup apps check the phone’s band and refuse to continue on 5 GHz, even when the device could have joined anyway.

Some devices receive the network name and password correctly and then fail to join. Band steering works by nudging clients toward 5 GHz, for example by being slow to answer them on 2.4 GHz, and a device with a short setup timeout can give up first. Other causes look the same from the outside: a 2.4 GHz radio set to Wi-Fi 6 only or WPA3 only, which older IoT chips do not support, or a network on channel 12 or 13, which a device built for North America usually cannot see.

Fixing pairing: split the bands or give IoT its own network

There are three fixes, from the most temporary to the most permanent.

Turn 5 GHz off while you pair. Switch off the 5 GHz radio, or band steering, for a few minutes and leave the network name unchanged. The phone falls back to 2.4 GHz, the device pairs, and you switch 5 GHz back on. Because the name never changed, the device reconnects normally afterward. It only has a 2.4 GHz radio, so there is nothing to steer.

Give each band its own name. This also works, with one catch: the device stores the name it was set up with. If you later merge the two names again, every device paired to the separate 2.4 GHz name loses its connection. Treat a split as permanent or do not do it.

Run a dedicated 2.4 GHz network for IoT. Many routers offer a second network, labeled guest or IoT, that can be limited to 2.4 GHz. Set it to 20 MHz wide, a fixed channel of 1, 6 or 11, and WPA2 or WPA2 and WPA3 transition mode (the WPA3 vs WPA2 guide explains the choice), and pair every IoT device to it. On a router that supports VLANs, the same network can be kept apart from your computers and phones, which is the arrangement described in putting IoT devices on a separate VLAN.

Whichever fix you choose, a few 2.4 GHz settings help every device on the band: a fixed channel of 1, 6 or 11 so the network stays put, a 20 MHz width, and a security mode that the oldest device in the house supports.

Zigbee, Thread and Bluetooth share the same band

Wi-Fi is not alone at 2.4 GHz. Zigbee and Thread both use the IEEE 802.15.4 radio, which divides the band into 16 channels numbered 11 to 26, each 2 MHz wide with centers 5 MHz apart. Bluetooth Low Energy uses 40 narrow channels across the whole band. All of them share the air with Wi-Fi, and Wi-Fi transmits more power and more traffic, so the low-power networks are the ones that suffer when they collide.

For Zigbee, the practical rule is to put its channel in a gap in your Wi-Fi. If your 2.4 GHz networks use 1, 6 and 11, Zigbee channels 15, 20 and 25 fall between or above them, as the first diagram shows. If you only use one Wi-Fi channel, pick a Zigbee channel at the far end of the band from it. Decide early: moving an established Zigbee network to a new channel is possible on some coordinators, but devices are often left behind and need pairing again. Thread networks are usually formed by a border router that chooses the channel itself, and Bluetooth copes by hopping between channels and avoiding the busy ones, with its three advertising channels placed clear of Wi-Fi channels 1, 6 and 11.

This is another reason to move phones, laptops and televisions to 5 GHz where they can reach it: it frees 2.4 GHz airtime for the devices that have nowhere else to go. The IoT protocols explainer shows where each of these radios sits in the wider stack.

6 GHz and Wi-Fi HaLow

Two more bands are worth knowing about. Wi-Fi 6E extended Wi-Fi 6 into the 6 GHz band, and Wi-Fi 7 uses it too, with channels up to 320 MHz wide. The band is large and clean, it requires WPA3, and its range is shorter than 5 GHz. The amount of 6 GHz spectrum open to Wi-Fi depends on the country. Very few IoT devices use it; its effect on IoT is that every fast client that moves up to 6 GHz leaves more room on the lower bands.

Wi-Fi HaLow, standardized as IEEE 802.11ah, goes the other way. It runs in the license-exempt bands below 1 GHz, such as 902 to 928 MHz in the United States, with narrow channels and low data rates. In exchange it reaches much further than 2.4 GHz Wi-Fi and suits battery-powered sensors across a farm, a campus or a warehouse. It needs its own HaLow access points, because ordinary routers and phones do not have a HaLow radio. It competes for the same outdoor, low-data jobs as LoRaWAN, with the difference that devices get ordinary IP networking. The Wi-Fi HaLow guide covers its bands, range, speed and where it fits.

For a home today, the bands that matter for IoT are still 2.4 and 5 GHz. Put the devices that need speed and sit near the router on 5 GHz, give everything else a 2.4 GHz network it can reach, and set that network up on purpose so that pairing a new device is a short job.