Your Zigbee coordinator (the hub, the bridge, the radio stick) is showing devices as offline that you know are powered up and reachable. They come back when you ping them in the app. They go offline again a few hours later. You start to think the coordinator is failing. In most cases it is not. The mesh routing or the channel is the actual problem, and both are fixable without changing hardware.
How Zigbee actually routes
Zigbee is a mesh network, but only mains-powered devices route. Battery-powered devices (door sensors, motion sensors, buttons) are end devices and do not relay messages. They talk to the nearest router and rely on that router to forward to the coordinator. When a router goes offline, every battery device that was using it has to find a new route, which can take ten to thirty minutes during which they appear offline.
This is the single most common cause of “random” device drops. A smart plug that was acting as a router got unplugged because someone needed the outlet. Now five sensors that depended on it are searching for a new route.
Identify your routers
You need a map of which devices in your home are acting as Zigbee routers. The tooling depends on your coordinator:
- Home Assistant with ZHA or zigbee2mqtt: open the Zigbee panel, view the network map. Routers and end devices are visually distinguished.
- SmartThings: use the IDE (still available at
my.smartthings.com) and look at each device’s “Type”. Anything labeled as a Zigbee router shows up explicitly. - Hubitat: Zigbee Details page (under Settings) shows a full topology including LQI per route.
- Hue Bridge: the official app does not expose this. Use diyHue or a Zigbee2MQTT bridge mode to inspect.
Most consumer smart plugs, mains-powered smart bulbs, and in-wall switches act as routers. Battery-powered devices never do. Some battery devices that claim to be “long range” still cannot route; they just have better radios.
The router density rule
A good rule of thumb: you want at least one Zigbee router within thirty feet of every end device, in every direction. If you have a motion sensor in a hallway and the nearest router is two rooms away across a thick wall, you are going to see drops. Add a smart plug or a mains-powered Zigbee bulb halfway between them.
Be careful with cheap Zigbee bulbs. Older Sengled and IKEA TRADFRI bulbs are notorious for poor routing, sometimes worse than no router at all because end devices will choose them based on signal but then fail to actually forward messages. If you have a setup with a lot of these older bulbs and persistent drops, replacing a couple of bulbs in the path with a known-good router (Aqara plug, Innr plug, or a newer TRADFRI) often clears the entire problem.
The channel problem
Zigbee runs on 2.4GHz, the same band as Wi-Fi. There are sixteen Zigbee channels (11 through 26) and only three non-overlapping Wi-Fi channels (1, 6, 11). The collisions matter. Specifically:
- Zigbee channel 11 overlaps Wi-Fi channel 1
- Zigbee channel 15 overlaps Wi-Fi channel 4 to 5
- Zigbee channel 20 overlaps Wi-Fi channel 9
- Zigbee channel 25 overlaps Wi-Fi channel 13
If your Wi-Fi is on channel 6 and your Zigbee coordinator is on channel 15, every burst of Wi-Fi traffic from your laptop crowds out the Zigbee packets from your sensors. The coordinator will report drops on the devices that have the weakest routes.
Pick a Zigbee channel that does not overlap your Wi-Fi. If your Wi-Fi is on channel 6, put Zigbee on channel 25 or 26. Many coordinators ship on channel 15 by default, which is one of the worst choices for a typical home.
How to change the channel without re-pairing
This is the painful part. Most Zigbee coordinators do not let you change channels without re-pairing every device, because the channel is part of the network key negotiation. There are a few exceptions:
- Zigbee2MQTT: allows channel changes via the frontend. After the change, you have several minutes during which devices will rejoin on the new channel before being marked offline.
- Hubitat: same, with an in-app warning during the change.
- Hue, SmartThings, Aqara: require a full reset and re-pair to change channels.
If you are stuck with the no-change ecosystems and need to switch channels, the typical workflow is to plan a Saturday afternoon for a full re-pair. Document each device’s room and name first.
Stabilizing without changing the channel
If you cannot change the channel, you can still reduce drops by tightening the mesh:
- Add two or three Zigbee plugs in the rooms where you see drops.
- Move your Wi-Fi router at least three feet from your Zigbee coordinator. They interfere with each other locally even on different channels.
- If you have a 2.4GHz IoT network, consider lowering its transmit power to reduce its airtime hogging.
- Reboot every Zigbee router (not the coordinator) once a quarter. End devices that were stuck on a flaky route will rebind to better neighbors.
When the coordinator really is the problem
If your network map shows healthy routes, your channel is not overlapping Wi-Fi, and you still see widespread drops, the coordinator hardware may be failing. The most reliable test: pull the coordinator stick (if you use Home Assistant or similar) and try a different stick of the same model. If the drops stop, your old stick was failing. Coordinators with a few years of heavy use can develop intermittent radio output issues that are hard to detect any other way.
Building a small monitoring habit
Stable Zigbee networks are not set-and-forget. Once a quarter, take ten minutes to look at the network map (whatever your hub exposes) and note which devices have weak LQI. Compare against last quarter. If a device that used to be solid is now marginal, something physical changed: new furniture absorbing signal, a new microwave nearby, a router that swapped channels.
Document the channel your coordinator is on in a notes file or sticky on the back of the hub. Next time you read a guide about channel conflicts, you can answer the first question (“what channel are you on?”) without digging through settings. The deeper context lives in our Zigbee channel conflict guide.
Related reading: false-offline status guide.
