If you've ever opened Home Assistant and seen half your Zigbee devices marked unavailable, you know how frustrating it is. I went through this myself a few months back, losing motion sensors and plugs at random, sometimes for hours at a time. Here's what I learned tracking it down, in case it saves someone else the same headache. Start with the network map, not the device My first instinct was to reboot the offline device. That almost never fixed anything. What actually helped was pulling up the network map in Zigbee2MQTT (or the visualization in ZHA) and looking at how that device was routing. Devices that had lost their route to a router, or were trying to hop through a router that had itself gone flaky, were the ones dropping out. The map told me where the actual problem was instead of me guessing device by device. Battery devices are not the same problem as mains-powered ones I used to lump all my offline devices into one bucket, but battery sensors and mains-powered plugs fail for completely different reasons. Battery devices sleep most of the time and only report in on a schedule or when triggered, so a sensor that looks offline might just be low on battery or waiting for its next check-in. Mains-powered devices, on the other hand, are always-on routers for the mesh, so when one of those goes offline it can take a chunk of your network down with it since other devices were relying on it to relay. Interference was my actual culprit In my case, the real issue was my Zigbee coordinator sitting a few inches from a USB 3.0 hub. USB 3.0 is a known noise source in the 2.4GHz range, and it was quietly wrecking my signal without any obvious symptom other than random dropouts. Moving the coordinator onto a USB extension cable, away from the hub and my router, cleared up most of my problems immediately. Channel congestion sneaks up on you I also checked my Zigbee channel against my Wi-Fi channels, since overlap between the two causes intermittent packet loss that looks exactly like random offline devices. Switching to a Zigbee channel that didn't overlap with my 2.4GHz Wi-Fi channel helped stabilize the last few stragglers. Give the mesh time before you panic After making any change, whether it's adding a router device, moving the coordinator, or switching channels, I had to resist the urge to judge results immediately. The mesh needs time to rebuild its routes, sometimes several hours. I made the mistake of assuming a fix didn't work after ten minutes, when really the network just hadn't finished reorganizing yet. What actually fixed it for me, in order Moved my coordinator away from USB 3.0 interference Added two router devices in the areas where I was seeing the most dropouts Switched to a less congested Zigbee channel Let the mesh sit overnight before checking again Between those four changes, my offline device count went from a near-daily annoyance to essentially zero. If you're chasing the same problem, I'd start with the network map and the coordinator placement before touching anything else. Those two things caused the majority of my issues.

Been meaning to write this up because I see the same question pop up every few weeks: "my Zigbee devices near the edge of the house keep going unresponsive, but everything close to the coordinator is fine." I ran into this myself with a contact sensor on my back gate, about 40ft and two walls from the coordinator. It would work fine for a day or two, then just drop off and need re-pairing. Here's what I learned digging into it. The mesh isn't as smart as people assume Zigbee mesh networking sounds great on paper: routers repeat the signal, end devices hop through them to reach the coordinator. But it only works if you actually have routers in the right spots. A lot of people don't realize: Battery-powered devices (sensors, most buttons) are almost always "end devices," not routers. They don't repeat signal for anyone else. Only mains-powered devices (smart plugs, some bulbs, in-wall switches) act as routers. If your edge-of-house devices are all battery sensors with no mains-powered Zigbee device nearby, there's nothing to relay them. They're relying on a direct, weak hop straight back to the coordinator. What actually fixed it for me I added a Zigbee smart plug about halfway between the coordinator and the back gate, specifically as a repeater. Within a day the contact sensor's LQI/RSSI reading jumped noticeably and it hasn't dropped since. A few other things worth checking if you're in this situation: Route table health: some coordinators/hubs let you see routing paths in their diagnostics. If a device is hopping through 3+ routers, that's a sign your mesh has gaps. Channel interference: Zigbee channels 15, 20, 25 overlap with 2.4GHz Wi-Fi. If your router's on a busy channel, that can look like a range problem when it's actually noise. Firmware: some manufacturers have quietly improved mesh healing behavior in updates. The takeaway Zigbee range problems are usually a topology problem, not a raw distance problem. A $15 to $20 mains-powered plug positioned as a repeater will usually do more for your edge devices than moving the coordinator around. Curious if others have run into this. Did adding routers fix it for you, or was it something else (channel, firmware, specific brand)?

Zigbee is one of the most reliable protocols for smart home devices, but a lot of people run into flaky connections or dropped devices because of a few common mistakes. Here's how to get the most out of it: Build a strong mesh network Zigbee is a mesh protocol — mains-powered devices (smart plugs, bulbs, in-wall switches) act as routers and extend your network. Battery devices (sensors, buttons) don't. Aim for a good spread of mains-powered devices throughout your home so signal has multiple paths to travel. Avoid Wi-Fi channel overlap Zigbee operates in the 2.4GHz band, same as Wi-Fi. If your Zigbee network feels unstable, set your Wi-Fi router to channels 1, 6, or 11 and pick a Zigbee channel that doesn't overlap (e.g. channel 25 or 26). Don't overload a single hub Most Zigbee coordinators can handle 50-200 devices depending on hardware, but performance degrades if you cram too many onto one hub without any routers. Spread devices out and let mains-powered ones do their job as repeaters. Keep your coordinator central and elevated Place your Zigbee hub/coordinator in a central location, elevated off the floor, and away from metal objects, mirrors, or thick concrete walls that can block signal. Update firmware regularly Zigbee firmware updates often fix bugs related to pairing, range, and interference. Check your hub manufacturer's app periodically for updates. Use pairing correctly Always factory reset a device before pairing it to a new network, and pair devices one at a time and close to the coordinator initially — you can move them to their final location afterward once they've joined the mesh. Group similar devices logically Use rooms/zones and groups in your hub software so scenes and automations are easier to manage and troubleshoot later. Following these basics will get you a Zigbee network that stays online and responsive instead of one that needs constant re-pairing. Happy to answer questions if anyone's running into specific issues.

This is an automated test reply from the Knovik MCP.

This topic was created by the Knovik MCP integration test suite and will be deleted immediately.

This topic was created by the Knovik MCP integration test suite and will be deleted immediately.

Testing lock/unlock via MCP.

Testing pin/unpin via MCP.

This is an automated test reply from the Knovik MCP.

This topic was created by the Knovik MCP integration test suite and will be deleted immediately.