Zigbee battery bulbs show 'unavailable' intermittently after switching Wi‑Fi router to a 2.4 GHz channel overlapping Zigbee spectrum

Environment

Home network: Wi‑Fi router set to 2.4 GHz channel 11 (2412–2462 MHz band edge), Zigbee coordinator (ConBee II) and ~20 Zigbee devices (Philips Hue and battery bulbs) on Zigbee channel 15; devices run on separate USB stick coordinator attached to a Raspberry Pi 4 running zigbee2mqtt

Symptoms

Several battery-powered bulbs report 'unavailable' in home automation dashboard for 10–30 minutes at a time after router channel changed; mains-powered bulbs and coordinator remain connected but some battery devices fail to rejoin until router channel changed back

Observations

Zigbee coordinator logs show increased RSSI noise and frequent MAC layer retries for affected endpoints during incidents; 2.4 GHz Wi‑Fi channel scan shows router transmitting on channel 11 with high power; zigbee2mqtt reports 'message timed out' and 'device appears offline' for battery nodes; change to Wi‑Fi channel 1 reduces Zigbee retries and devices stabilize

Already attempted

Repositioned coordinator USB stick to a different USB port and added a short USB extension cable — marginal improvement; set router transmit power to medium and limited SSID airtime (20MHz) — reduced impact but not eliminated; tried moving Zigbee to channel 20 — some older bulbs do not support that channel and re-pair failed

Question

Why do battery-powered Zigbee bulbs become unavailable after switching the Wi‑Fi router to a 2.4 GHz channel that overlaps Zigbee spectrum, and what non-invasive mitigations allow coexistence without re-pairing all devices?

Post timeline

COMMUNITY RESPONSES

Verified community troubleshooting

0 replies

No answers yet..

Showing 0 of 0 community responses

AI DIAGNOSTICS

Incident analysis

Updated 1w ago• Trouble ID

Most likely causes

2.4 GHz Wi‑Fi channel overlap causing RF interference and increased Zigbee packet loss 98%

High Wi‑Fi transmit power and channel width (40MHz) increasing adjacent channel bleed into Zigbee channel 88%

Some battery bulbs have poorer receiver sensitivity and cannot cope with increased retries 85%

Summary

Zigbee (2.4 GHz) and Wi‑Fi channels overlap; high-power Wi‑Fi on overlapping channels can cause RF interference and increased MAC retries, particularly harming low-power, battery‑sleeping devices that have limited time windows to receive messages. Battery devices are more sensitive because they wake infrequently and need frames to get through quickly. Moving Wi‑Fi away from overlapping channels or lowering transmit power reduces interference; moving Zigbee to a non-overlapping channel (e.g., 15 is overlapped by Wi‑Fi 11) or adjusting Zigbee channel can help but older devices may lack full channel support.

Suggested Fixes

Diagnostic step 1

Identify channel overlap matrix: use a Wi‑Fi analyzer to determine router channel and choose a Zigbee channel with minimal overlap (e.g., Zigbee channels 15/20/25 map to certain Wi‑Fi channels). If router uses channel 11, consider moving Zigbee to channel 25 or change Wi‑Fi to channel 1 or 6 to reduce overlap.

Diagnostic step 2

Lower 2.4 GHz Wi‑Fi transmit power temporarily and/or reduce channel width to 20MHz; monitor zigbee2mqtt logs for retries. These are reversible via router UI.

Diagnostic step 3

Relocate the Zigbee coordinator antenna/USB stick away from router and other USB noise, using a short extension cable for improved RF placement.