Sharing 2.4 GHz: What a Zigbee Channel Change Costs

A Zigbee channel change can improve an unreliable mesh, but may also interrupt communication and leave individual devices needing attention. Before changing the network, the useful checks are the occupied Wi-Fi channels, channel width, coordinator placement and actual message reliability. No Zigbee channel is permanently free of interference.

Channel numbers describe frequency, not guaranteed separation

For the 2.4 GHz Zigbee channels 11–26, the centre frequency is 2405 MHz plus 5 MHz for each step above channel 11. The signal occupies roughly 2 MHz. Modern 2.4 GHz Wi-Fi commonly uses 20 MHz channels; the familiar 22 MHz drawing describes legacy DSSS operation. Neither drawing is a hard wall beyond which a strong transmitter has no effect.

Zigbee centre (MHz) = 2405 + 5 × (channel − 11)
Zigbee 11: 2405    15: 2425    20: 2450    25: 2475    26: 2480
Wi-Fi   1: 2412     6: 2437    11: 2462    13: 2472
Numbers are centre frequencies, not interference-free boundaries.

Wi-Fi 1, 6 and 11 form a common three-channel plan. Other channels exist where permitted and supported; the plan is not a statement that only these three numbers can work. Zigbee 15, 20 and 25 are useful candidates around that particular Wi-Fi arrangement, not universally clear channels. Wi-Fi 13 changes the situation near Zigbee 25 and 26. Actual nearby access points, widths and signal strengths determine the choice.

Interference depends on received energy and airtime

Neither Wi-Fi nor Zigbee has one universal transmit power. The important conditions include received signal strength, distance, antenna placement, receiver filtering and how much time each radio transmits. A nearby busy access point can overwhelm a weak Zigbee link even when a simplified channel diagram suggests a gap.

Both systems use mechanisms to avoid collisions. Wi-Fi does not decode a Zigbee packet as a Wi-Fi packet, but sufficiently strong non-Wi-Fi energy can still affect channel assessment. The claim that Wi-Fi never hears Zigbee is therefore too absolute. Carrier sensing also cannot eliminate every collision, particularly when transmitters cannot hear each other. Delayed or lost messages are possible in both directions.

Reduce local interference before moving the mesh

• Coordinator position: distance from the host, SSD, USB 3 devices and Wi-Fi antennas can help. A suitable shielded USB extension and a USB 2 port are useful trials. A one-metre cable is neither a guaranteed cure nor evidence that range previously fell by exactly half.
• Wi-Fi width: 20 MHz generally leaves more room in a crowded 2.4 GHz band than 40 MHz. Moving suitable clients to another supported band can reduce 2.4 GHz traffic.
• Intermittent sources: microwave ovens and other radios can disturb reception. Their effect depends on location, shielding and activity; channel 20 is not automatically unusable whenever an oven runs.
• Measurement: compare message success, delays and repeatable operating conditions. A Wi-Fi network list does not reveal every non-Wi-Fi interferer. A single link-quality value does not explain the cause.

Channel migration is not automatically a complete re-pairing

Zigbee2MQTT documents an existing-network channel change for the zstack and ember adapter types. A network-update broadcast communicates the change. Sleeping devices may follow when they next wake; triggering a sensor after the change helps verify this. Some devices do not support the migration and may need manual re-pairing after remaining unresponsive despite waking.

Before migration, a verified backup and a record of the existing channel are useful. The supported procedure depends on the integration and adapter. Changing a channel must not be confused with changing the network key or PAN ID: those changes have different re-pairing consequences. A maintenance window should allow time to check powered routers, wake battery devices according to their instructions and test important automations. A successful coordinator log alone does not prove that every device followed.

Moving Wi-Fi can be the less disruptive option, but a Wi-Fi channel change can interrupt active clients, calls or IoT connections. The better choice depends on both networks. After any change, reliability needs checking during realistic traffic and recurring interference. No choice remains optimal merely because a neighbouring router has not changed yet.