2.4 GHz interference and channel planning

Two formulas, and everything follows#

You can derive the entire channel plan from these. Nothing below is a rule of thumb.

IEEE 802.15.4 (Zigbee and Thread), channels 11 to 26:

center = 2405 + 5 x (channel - 11)   MHz

Channel spacing is 5 MHz. Occupied bandwidth is about 2 MHz at the -3 dB points and roughly 3 MHz out to the first nulls, so treat each channel as center plus or minus 1.5 MHz.

2.4 GHz Wi-Fi, channel n:

center = 2407 + 5n   MHz

A 20 MHz OFDM channel occupies center plus or minus 10 MHz. Legacy 802.11b DSSS is wider, at center plus or minus 11 MHz.

Apply the second formula to the three US non-overlapping channels:

Which leaves exactly three interior gaps: 2422 to 2427, 2447 to 2452, and everything above 2472 up to the 2483.5 MHz band edge. Three gaps, two of them 5 MHz wide.

Every 802.15.4 channel against Wi-Fi 1, 6 and 11#

Twelve of the sixteen channels sit inside a Wi-Fi channel. Wi-Fi 1 covers 802.15.4 channels 11 to 14, Wi-Fi 6 covers 16 to 19, and Wi-Fi 11 covers 21 to 24. The survivors are 15, 20, 25 and 26, which is why every guide names those four. The guides usually stop there. The arithmetic does not.

The four survivors, examined#

Channel 15, center 2425 MHz, occupied 2423.5 to 2426.5. It fits the 2422 to 2427 gap with 1.5 MHz of margin below and 0.5 MHz above. Under legacy 802.11b that gap shrinks to 2423 to 2426 and channel 15 no longer fits. It is also 1 MHz from Bluetooth advertising channel 38.

Channel 20, center 2450 MHz, occupied 2448.5 to 2451.5. Same 5 MHz gap, same tight margins: 1.5 MHz above Wi-Fi 6's upper edge, 0.5 MHz below Wi-Fi 11's lower edge. And 2450 MHz is squarely where microwave oven energy concentrates, which no channel plan routes around.

Channel 25, center 2475 MHz, occupied 2473.5 to 2476.5. Above Wi-Fi 11 with 1.5 MHz of clearance from its nominal upper edge. A nominal edge is a spectral mask, not a wall: real transmitters put measurable energy into their sidebands, and channel 25 is close enough to catch some.

Channel 26, center 2480 MHz, occupied 2478.5 to 2481.5. The only one with genuine distance: 8 MHz above Wi-Fi 11's upper edge and 18 MHz from its center. This is why Home Assistant's Thread documentation recommends channel 26 in heavy Wi-Fi environments, with 25 as the fallback.

The move most guides miss: drop Wi-Fi channel 6#

The four-survivor list assumes Wi-Fi on channels 1, 6 and 11. Most homes do not need three 2.4 GHz channels. Pin your access points to 1 and 11 only, and 2427 to 2447 stops being occupied. The interior gap becomes:

2422 to 2452 MHz   (30 MHz of clear spectrum)

That range holds 802.15.4 channels 15 through 20 in their entirety. Work out the margins:

Channel 17 gives you 13 MHz of worst-case separation from the nearest Wi-Fi edge. Channel 26, in a house that still uses Wi-Fi 11, gives you 8 MHz, and pays for it with reduced transmit power and patchier device support. So restricting Wi-Fi to 1 and 11 produces a better 802.15.4 environment than picking a clever 802.15.4 channel does.

If you run both Zigbee and Thread, you need two separated channels out of that range. 16 and 19 is a good pair: 15 MHz apart from each other, 8 and 7 MHz from the nearest Wi-Fi edge, and both below the frequencies where microwave energy lives.

Overlap is necessary, not sufficient#

Frequency overlap tells you where interference is possible. Whether it hurts depends on received power, and there distance matters more than arithmetic. A home access point commonly transmits around 20 dBm. A coordinator dongle transmits far less: the Home Assistant Connect ZBT-2 runs 10 dBm in Europe and 8 dBm elsewhere. That gap is an unfair fight at any frequency, and it gets much worse when the two sit 20 cm apart on one shelf.

So before you change channels, change positions. Move the coordinator or border router at least a couple of meters from the access point, get it out of a metal rack and off the back of a TV, and give it a clear line into the house rather than into a wall. The same logic applies to your Wi-Fi placement, covered in the network setup a smart home wants.

The aggressor almost nobody suspects: USB 3.0#

This is real, documented, and it ruins Zigbee and Thread coordinators every day.

USB 3.0 signaling produces broadband noise whose harmonics land across roughly 2.4 to 2.5 GHz. Intel published a white paper on it in April 2012, "USB 3.0 Radio Frequency Interference Impact on 2.4 GHz Wireless Devices", carried as USB-IF document 327216-001, describing a noise rise on the order of 20 dB at close range.

Two things follow. First, this is in-band noise, so no filter can remove it: it lands on exactly the frequencies your radio needs. Second, it falls off quickly with distance, so the fix is physical. Put the dongle on a 1 to 2 meter USB 2.0 extension cable, away from the host, the drives and the ports. Nabu Casa ships a 1.5 meter cable with the Connect ZBT-2 for this reason, and Home Assistant's ZHA documentation says to avoid USB 3.x ports outright. If your host has only USB 3.x ports, put a powered USB 2.0 hub in between.

The other aggressors#

Microwave ovens. A domestic microwave concentrates energy roughly between 2450 and 2470 MHz, at power levels no radio in your house can compete with. That range covers 802.15.4 channels 20 through 24 and Wi-Fi channel 11. If your smart home degrades for two minutes at a time and then recovers, look at the kitchen before you look at the logs. Note the irony: channel 20 is one of the four channels commonly recommended as safe from Wi-Fi, and it is the microwave's center of mass.

Bluetooth advertising channels. Bluetooth LE uses adaptive frequency hopping on its 37 data channels, which makes it a well-behaved neighbor most of the time. Its three advertising channels do not hop. They are fixed at 2402, 2426 and 2480 MHz, chosen to fall in the Wi-Fi gaps, which is exactly where you were planning to put your mesh:

• Advertising channel 39 at 2480 MHz is exactly 802.15.4 channel 26.
• Advertising channel 38 at 2426 MHz is 1 MHz from 802.15.4 channel 15.
• Advertising channel 37 at 2402 MHz sits at the bottom of the band, inside Wi-Fi 1.

Advertising packets are short, so this ranks below Wi-Fi, but in a room with several phones, watches, headphones and trackers it is not nothing. It is another argument for the 1 and 11 plan with 802.15.4 in the middle of the band. See Bluetooth and BLE in the smart home.

Everything else. Video baby monitors, analog wireless cameras and cheap 2.4 GHz mouse dongles are narrowband, constant, and hop nowhere. Eliminate them one at a time when nothing else fits.

Zigbee and Thread in the same house#

They share the PHY, the band and the channel numbering, and two 802.15.4 networks on one channel contend exactly as Wi-Fi would. Put them on different channels from each other and from Wi-Fi. A workable plan, given the arithmetic above and which radio for which job:

Many combination dongles run either Zigbee or Thread but not both at once, including the Connect ZBT-2, so two networks means two radios and two antennas that should not sit next to each other either. Designing a Thread mesh that holds up and Zigbee in 2026 cover the topology side. If none of this is solvable in your building, the honest answer may be to move the problem devices to Z-Wave at 908.42 MHz.

The channel planner does this arithmetic for your specific Wi-Fi channel and returns the safe pair, with the frequencies shown so you can check the result against the formulas above.

Reading the symptoms#

Not every problem is spectrum. If failures are geographic rather than intermittent, that is topology: start with Thread troubleshooting or a device shows as unresponsive.