Why Your Zigbee Devices Keep Dropping — and How to Fix the Dead Spots

The symptom

You know the pattern. A door sensor shows unavailable in Home Assistant. A bulb at the far end of the house responds to commands sometimes, with a two-second lag, and sometimes not at all. In Zigbee2MQTT the device's last-seen timestamp is hours old, and when it does report in, the LQI is in the teens. Re-pairing "fixes" it for a day or two, then it drops again.

LQI — link quality indicator — runs from 0 to 255, higher is better. A device sitting next to the coordinator reports 200+. Anything consistently below ~50 is a weak link, and a device in the teens is barely holding on: every retransmission is a coin flip, batteries drain faster from the retries, and the device eventually gives up and leaves the network. The re-pairing ritual doesn't fix anything because the radio path is still bad — you're just resetting the clock on the next dropout.

Cause 1 — Router starvation: your "mesh" is secretly a star

Zigbee's headline feature is the mesh: devices relay traffic for each other, so the network extends itself. The catch that trips up almost everyone: only mains-powered devices route. Smart plugs, wired bulbs, in-wall switches — those are routers. Battery devices — door sensors, temperature sensors, buttons, motion sensors — are end devices. They sleep most of the time to preserve battery, they relay nothing, and each one connects through exactly one parent.

So a house with a coordinator stick and fifteen battery sensors is not a mesh at all. It's a star network pretending to be one: every sensor must reach the coordinator directly, and the ones two rooms away simply can't. This is by far the most common cause of Zigbee dropouts, and no amount of channel tuning fixes it.

The fix: add routers along the path — a smart plug or an always-powered bulb roughly every couple of rooms, positioned between the coordinator and the far devices. Two caveats: a bulb only routes while it has power, so a bulb behind a wall switch that people actually flip is a router that randomly vanishes (and takes its children with it). And a few mains devices ship configured as end devices — check the device page in Zigbee2MQTT rather than assuming.

Cause 2 — Walls and distance: 2.4 GHz physics doesn't care about your hub

Zigbee lives in the same 2.4 GHz band as WiFi, and the same propagation rules apply — except Zigbee transmits at a fraction of the power. Realistic indoor range for one hop is 10–20 m with a clear-ish path, and every wall in between takes its cut: drywall a couple of dB, brick roughly 6–8 dB, concrete 10–15 dB per wall, and reinforced concrete worse still. Metal is the killer — a fridge, an oven, a mirror, or a metal-clad boiler cupboard in the path can flatten the link entirely.

The mistake people make is judging distance as the crow flies. Your sensor might be 8 m from the nearest router — but if the straight line passes through the kitchen's appliance wall and a concrete stairwell, the radio distance is far greater than the tape measure says.

The fix: trace the actual path. If the line between a flaky device and its nearest router crosses two masonry walls or any large metal object, the fix isn't a stronger coordinator — it's a router placed so the path is broken into short, low-loss hops.

Cause 3 — WiFi interference: your own network is jamming your sensors

Zigbee channels 11–26 sit inside the same 2.4 GHz band as WiFi channels 1, 6, and 11 — and most Zigbee coordinators default to Zigbee channel 11, which sits directly underneath WiFi channel 1. A busy WiFi network is orders of magnitude louder than a Zigbee sensor; when they overlap, Zigbee loses.

The fix: pick your WiFi channels first (1/6/11 as usual), then park Zigbee in one of the gaps — 15, 20, or 25 are the safe picks; 26 works but some devices transmit at reduced power there or refuse to join. One honest caveat: changing the Zigbee channel on an existing network in Zigbee2MQTT or ZHA is not free. Routers usually migrate, but sleeping battery end devices often miss the change announcement and need to be woken or re-paired. Do it once, deliberately, on a day you have half an hour — not as weekly channel-hopping.

Cause 4 — The coordinator is sabotaging itself

The classic setup: coordinator stick plugged straight into the back of a server or NUC, which itself sits inside a metal case, in a metal rack, in a corner of the utility room. Every part of that sentence hurts. The corner placement wastes half the coverage into exterior walls, the metal case shadows the antenna, and — the famous one — USB 3.0 ports radiate broadband noise squarely in the 2.4 GHz band. A coordinator plugged into a USB3 port next to an external SSD can be effectively deaf, which is why "use a USB 2.0 extension cable" is the first line of the Zigbee2MQTT setup advice and has rescued thousands of networks.

The fix: put the stick on a 0.5–1 m USB 2.0 extension cable, away from the machine, USB3 devices, and anything metal. If the server lives in a bad corner, the cable buys you a metre of freedom; a network-attached coordinator (PoE Ethernet models) buys you the whole house.

Diagnosing: the map shows the mesh you have

Zigbee2MQTT's network map and ZHA's visualization draw the mesh as it currently exists: which device is parented to which router, with LQI on each link. That's genuinely useful for confirming a diagnosis — you'll see the battery sensor clinging to the coordinator three rooms away at LQI 15, ignoring the smart plug next door, or a whole branch of devices hanging off one bulb that someone keeps switching off.

But the map has a blind spot: it can only show you the network you already built. It can't tell you where a router should go, whether one plug in the hallway would fix three flaky sensors at once, or whether the far bedroom is reachable at all without a hop through the stairwell. For that you need to reason about the building, not the graph.

Plan the mesh instead of guessing

This is exactly the problem predictive planning solves, and it works for Zigbee the same way it works for WiFi. Our free browser planner now has a Zigbee mode: upload your floorplan, draw the walls with their materials (drywall, brick, concrete, glass), place the coordinator and candidate routers, and see the predicted coverage heatmap — including the dead zones — before you buy a single plug.

Under the hood it runs the COST-231 multi-wall propagation model with per-material attenuation — the same math as the WiFi link-budget walkthrough, tuned for Zigbee's transmit power. Like any predictive model it carries a ±6–10 dB envelope (the accuracy page spells out why), which is not survey-grade — but it's exactly enough to answer the questions that matter: how many routers, and where. Dragging a virtual smart plug around a floorplan is free; buying four plugs to find out one was in the wrong place is not.

The placement checklist

• →Coordinator central, elevated, in the open. Not in a metal case, not in a corner, not in the basement.
• →USB 2.0 extension cable, always. Half a metre of cable away from the server and any USB3 device. Cheapest fix in all of home automation.
• →A router every 10–15 m or every two masonry walls — whichever comes first on the actual radio path.
• →Routers between, not beside. A plug in the same room as the coordinator adds nothing; a plug halfway to the far sensor adds a hop.
• →Route around metal and water. Fridges, ovens, mirrors, boilers, fish tanks — plan hops that dodge them rather than punch through.
• →Only count routers that stay powered. A bulb on a wall switch people use is not infrastructure.
• →Pick the channel once: WiFi on 1/6/11, Zigbee on 15, 20, or 25. Set it before pairing everything if you can.
• →Verify with LQI afterwards. After changes, give the mesh a day to re-route, then check the map: every link above ~50, no battery device parented across the house.

Beyond Zigbee

The same plan-first logic applies to the other smart-home meshes. The planner has dedicated pages for Zigbee, Thread (same 2.4 GHz band, same wall physics, different routing rules), and Z-Wave (sub-GHz, so walls cost less but hop limits bite harder). If your problem is the WiFi network itself, start with the apartment planning walkthrough instead.