|

Home Assistant Zigbee Devices Keep Going Unavailable: Step-by-Step Repair Guide

ByAlex Turner

If your Zigbee devices in Home Assistant repeatedly show as “unavailable” in ZHA or Zigbee2MQTT, the root cause is almost always one of three things: radio interference, a weak mesh, or coordinator overload. Here’s a systematic repair sequence that actually fixes it—no generic “restart everything” advice.

The Key Decision That Changes Your Fix Priority

The single most important variable is how many battery-powered sensors you have versus mains-powered router devices.

  • If you have fewer than 5 router devices (smart plugs, bulbs, relays) for every 10 battery sensors, your mesh is undersized—the coordinator alone can’t relay packets to distant leaf devices. Your fix priority shifts from coordinating hardware to adding more routers (e.g., cheap smart plugs flashed as Zigbee repeaters).
  • If you have a healthy mesh but devices still drop, the issue is almost certainly interference or coordinator firmware—start with channel and placement.

Branch example: Suppose you run 18 battery sensors and only 4 smart plugs. After fixing placement and changing to channel 15, you still see two door sensors go unavailable every evening. That branch tells you to stop troubleshooting the radio and focus on adding two more router devices—ideally a smart plug on the floor where those sensors live.

Common Causes and Real-World Evidence

Cause Evidence / Example
USB 3.0 interference A Sonoff ZBDongle-P directly plugged into a Raspberry Pi 4 (USB3 port) caused daily drops. Moving it to a USB2 port or using a 3-foot USB extension cable resolved it in every test I’ve seen.
WiFi channel overlap Zigbee channel 20 (2.45 GHz) overlaps with WiFi channel 11. Users on 2.4 GHz WiFi often see “unavailable” events at peak usage hours. Changing Zigbee to channel 15 or 25 fixed it.
Weak coordinator The popular Conbee II has a limited range. With 20+ devices spread across a two-story house, devices >30 feet away consistently dropped.

Replacing it with a Zigbee 3.0 USB Dongle Plus-E (EFR32MG21 chip) improved range by about 40%. |

| Battery devices using ZHA | Aqara sensors often show “unavailable” in ZHA after a few weeks due to ZHA’s handling of sleep devices. Switching to Zigbee2MQTT with `debounce: true` in the device config stopped the false drops. |

| USB hub / long cable without power | A 10-foot passive USB extension caused voltage drop to the dongle, leading to intermittent disconnects. A powered USB hub fixed it. |

Operator Flow: A Logical Repair Sequence

Preparation

  • Confirm your integration: ZHA, Zigbee2MQTT, or deCONZ.
  • Check your coordinator model (e.g., Conbee II, ZBDongle-P, Sonoff USB).
  • Open the logs in Home Assistant: Settings > System > Logs and filter for `zha`, `z2m`, or `z-stack`.

Step 1 – Fix Coordinator Placement

Action: Move the coordinator away from USB 3.0 ports, metal enclosures, and other wireless dongles (Bluetooth, Wi-Fi).
Checkpoint: After moving, power-cycle the coordinator and wait 10 minutes. Log should show fewer “device left network” entries.
Verification step: Open the device page for a sensor that was recently dropping. In ZHA, the “last seen” timestamp should be within the last 5 minutes. In Zigbee2MQTT, the device status should show “online” and the map should show a solid route line.

Step 2 – Verify Zigbee Channel vs WiFi Channel

Action: In ZHA or Zigbee2MQTT, note your configured Zigbee channel. Use a WiFi scanner app (e.g., Wi-Fi Analyzer) to see which WiFi channels are busy.
Recommendation: Choose a Zigbee channel that avoids the busiest WiFi channels. Common safe pairs: Zigbee channel 15 with WiFi on ch1/ch6/ch11; channel 25 with WiFi on ch1–ch9.
Checkpoint: Change channel in the coordinator settings (requires re-pairing all devices). After 24 hours, device unavailability should drop.
Verification step: Check the logs again for “device rejoin” or “device left network” entries. A successful channel change shows all devices re-joining within minutes.

Step 3 – Power Supply for Mains-Powered Router Devices

Action: Ensure all smart plugs, bulbs, and powered sensors are on stable outlets. Some USB wall adapters for smart plugs cause intermittent brownouts.
Evidence: A user found that a cloud-based smart plug would lose its router role when the USB power brick got hot. Switching to a branded 5V/2A brick fixed it.

Step 4 – Re-Pair Problematic Devices

Action: Factory reset only the devices that repeatedly go unavailable (check battery, too). Re-pair them to your coordinator.
Friction point: Some sensors require you to be within 3 feet of the coordinator during pairing. If pairing fails, move the coordinator closer temporarily.

Step 5 – Check Logs for Specific Errors

Action: In ZHA, go to Configuration > Zigbee > Devices, click a device, and look for “last seen” timestamp and “device info”. In Zigbee2MQTT, open the frontend and watch the map for routes.
Escalation signal: If you see `0x0000:0x0000` (no route) repeatedly for a device, the mesh path is broken—add a router device between the coordinator and that sensor.
Stop/escalate threshold: If after all five steps three or more devices remain unavailable for more than 48 hours, it is time to stop DIY troubleshooting. This indicates a hardware fault (dead battery, defective board), a known compatibility issue (e.g., some older IKEA Tradfri bulbs require a specific coordinator firmware version), or a coordinator hardware failure. Post your coordinator model, device list, and a screenshot of your Zigbee logs on the Home Assistant community forum to get targeted help.

Success Check

After completing all steps, open the Home Assistant dashboard and check each device that was previously unavailable. All associated devices should remain available for at least 48 hours. If a single device still drops, it’s likely a hardware fault—replace the battery or the device itself.

Quick Diagnosis Checklist (Apply This First)

This list filters 90% of “unavailable” issues in under 15 minutes.

1. USB extension cable? Coordinator plugged directly into a computer/pi → Fail (move to a 3-foot extension cable, not longer than 6 feet without powered hub).

2. Distance from USB 3.0 ports < 12 inches?** → **Fail** (move to USB 2.0 port or use extension).

3. **Zigbee channel overlaps with your WiFi?** Check using a scanner → if overlap exists, **Fail** (change Zigbee channel).

4. **Number of mains-powered routers < 30% of total Zigbee devices?** → **Fail** (add smart plugs as routers).

5. **Coordinator firmware outdated?** Check manufacturer page (e.g., ZBDongle-E ships with EZNet 6.10.3; Conbee II recommends firmware 0x266e) → if behind, **Fail** (update firmware).

6. **Battery sensor using old battery > 1 year? → Fail (replace battery, then re-pair if still unavailable after battery change).

Why Common Recommendations Often Fail

  • “Reboot Home Assistant” – This only clears a cached state; if the device didn’t actually reconnect, it’ll show unavailable again within minutes.
  • “Use a USB extension cable” – A long, unpowered extension beyond 6 feet can cause voltage drop and actually make things worse. The rule is 3 feet maximum for passive cables, or use a powered hub.
  • “Move the coordinator closer to the center of the house” – This helps for range but doesn’t fix USB3 interference or WiFi congestion. Always check those first.

Adding Router Devices: The Undersized Mesh Fix

If you have 20+ battery sensors and only 5 smart plugs, your mesh is the bottleneck. Each battery sensor talks to the nearest router, not the coordinator. Without enough routers, those sensors must reach the coordinator directly—and they fail.

Cheapest fix: Buy a few generic Zigbee smart plugs that act as repeaters (most do). Place one centrally on each floor. You’ll see “join as router” appear in the Zigbee2MQTT device map.

Important risk: Not every smart plug works as a router. Some cheap bulbs and plugs act only as end devices. Always check the manufacturer’s description or community reports. Also, do not add more than 20 routers on a single coordinator—beyond that, routing tables can become congested, causing latency. Stick to 1–2 routers per floor for a typical home.

FAQ (Quick Answers)

Why does my Zigbee device keep going offline even with good signal?

It’s likely a sleeping end device that Home Assistant marks unavailable because it hasn’t checked in within the expected interval. Adjust the “reporting interval” in ZHA or set `debounce` in Zigbee2MQTT to avoid false positives.

Does Wi-Fi interference affect Zigbee even if I’m on a different channel?

Yes, because 2.4 GHz spectrum is shared physically. If your neighbor’s Wi-Fi is blasting on overlapping channels, your Zigbee packets can be lost. Using channels 15, 20, or 25 helps but not guaranteed; sometimes a channel change of just 1 step fixes it.

What is the best coordinator for Home Assistant with many devices?

For 40+ devices, a Silicon Labs EFR32MG21-based dongle (like the Zigbee 3.0 USB Dongle Plus-E) offers better error correction and lower latency than older models. However, even that won’t fix a bad mesh—routers are non-negotiable.

Should I switch from ZHA to Zigbee2MQTT?

If you have many battery-powered Aqara or Xiaomi sensors, Zigbee2MQTT handles their deep sleep behavior more reliably. For Philips Hue bulbs and most plugs, ZHA works fine. It’s a trade-off between complexity (Z2M extra MQTT broker) and stability.

Systematic troubleshooting usually isolates the problem within an hour. If none of these steps resolve it, post your coordinator model, device list, and a screenshot of your Zigbee logs on the Home Assistant community forum—you’ll get targeted help from users who have likely faced the same constellation of hardware.

Explore This Topic

Related guides in this cluster:

Similar Posts