Quick answer: A Wi‑Fi or router change can affect Zigbee reliability even though Zigbee and Wi‑Fi are different protocols. They share parts of the 2.4 GHz band, so channel overlap, a moved Home Assistant host, USB interference, or a changed power setup can expose a weak mesh. Diagnose one layer at a time instead of resetting every device.
1. Identify what changed
Write down whether the problem began immediately after replacing the router, changing Wi‑Fi channels, moving the Home Assistant computer, changing USB ports, or losing power. Note whether all Zigbee devices fail together or only battery-powered devices in one area. A simultaneous outage points toward the coordinator, integration, host or radio environment; isolated failures more often suggest routing, battery or signal issues.
2. Check the Zigbee coordinator and integration
- In Home Assistant, open the relevant integration (ZHA or Zigbee2MQTT) and confirm it is loaded and the coordinator is available.
- Check the integration logs for serial-port errors, repeated reconnects, adapter resets or MQTT connection failures.
- If the coordinator is USB-connected, check that its stable device path is still present and that the host has not moved it to a different port.
- Use a USB extension cable to move the radio away from the computer, USB 3 devices and metal enclosures if interference is plausible.
3. Consider Wi‑Fi and Zigbee channel overlap
Do not change channels blindly. First record the current Zigbee channel and the router’s 2.4 GHz channel. Nearby networks, channel width and actual radio conditions matter. If you decide to change the Zigbee channel, check the documentation for your coordinator and integration first: some devices may need special handling or rejoining, and a channel change can create a second problem if done casually.
4. Check the mesh before re-pairing
Make sure mains-powered Zigbee routers—such as compatible smart plugs or bulbs—are powered and have had time to rejoin. A powered-off router can strand battery sensors that depended on it. Test a nearby device and a distant device separately. Replace a weak battery only when the evidence points to that device; do not delete devices from the entity registry just because they are temporarily unavailable.
5. Verify recovery
- Make one change at a time.
- Watch the integration logs and device availability for several minutes.
- Test both a nearby and a distant device.
- Record the fix and any channel or coordinator changes.
When to escalate
If the coordinator repeatedly disconnects, capture the relevant log lines and identify your integration (ZHA or Zigbee2MQTT), coordinator model, host type and what changed before the outage. Avoid posting network keys or other secrets. Those details make the next diagnostic step much more reliable.
Related guides: If Zigbee devices were already dropping offline, see the Zigbee offline diagnosis guide. If several kinds of Home Assistant devices are affected, start with the broader offline checklist. If the issue began after a power cut, use the power-outage recovery guide.
Image credit: James Yarema on Unsplash. This guide is general troubleshooting advice; exact menus and options vary by Home Assistant version and coordinator.