Free tools Windows power users keep installed
One-click scans. No signup required.
If Zigbee devices keep going offline in Home Assistant, treat “offline” as a symptom rather than a diagnosis. Start by finding out whether one device, several devices, or the whole ZHA network is affected; then use ZHA’s map, logs, and device diagnostics before changing channels or replacing hardware.
The likely causes include radio interference, poor coordinator placement, weak mesh coverage, coordinator firmware or hardware problems, an unstable serial connection, and device-specific or battery-related faults. The sequence below helps you narrow those possibilities without making disruptive changes prematurely.
As an Amazon Associate I earn from qualifying purchases.
1. Establish whether the failure is local or network-wide
“Why does my Zigbee sensor become unavailable?” cannot be answered from the unavailable status alone. A battery sensor that disappears by itself points you toward a different investigation than several mains-powered devices that fail at the same time. Before changing anything, write down what is actually happening.
Record the affected devices
- List every device that becomes unavailable, including its room, model, and whether it is battery-powered or mains-powered.
- Note whether devices fail simultaneously or at different times.
- Record whether the coordinator, Home Assistant host, or ZHA integration restarted shortly before the outage.
- Write down whether an affected device returns on its own, returns after a button press, or remains unavailable until it is re-paired.
- Capture the approximate time of each failure so you can match it with ZHA log entries.
This record does not prove a cause, but it separates a single-device investigation from a network, coordinator, or host investigation. A single battery device may have a device-specific problem; multiple devices disappearing together makes the shared radio path, coordinator, serial link, or Home Assistant host more important to examine.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Understand what “offline” means in ZHA
ZHA can show a device as unavailable when it has not provided a usable response within the integration’s expectations. That status does not identify whether the radio signal was blocked, a router could not forward the message, the coordinator lost serial communication, or the device itself stopped responding. Do not infer a failed battery, a bad channel, or a defective coordinator from the status alone.
2. Inspect the ZHA topology map, logs, and diagnostics
Use evidence from the installation before buying a router, moving hardware, or changing the Zigbee channel. Home Assistant’s official Zigbee Home Automation (ZHA) documentation describes the relevant tools and their limitations.
Open the network map
- In Home Assistant, open Settings > Connectivity > Zigbee.
- Select Show map.
- Locate the coordinator, the affected device, and any mains-powered devices between them.
- Look for the reported multi-hop paths and the RSSI/LQI values shown for links.
The map can reveal that a distant device is relying on one weak-looking path or that several devices depend on the same router. RSSI and LQI can help flag a poor link, but they are not universal signal meters. Values are reported through each device’s Zigbee stack, so different manufacturers may calculate or expose them differently. Missing links for battery-powered end devices are common and do not automatically mean that the device has no route.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Use logs to identify shared failures
Open the ZHA logs around the time of an outage. Look for repeated communication errors, device timeouts, coordinator restarts, or messages that affect several devices together. A single timeout is not enough to identify the cause; a recurring pattern that aligns with multiple unavailable devices is more useful.
If you use a Silicon Labs EZSP coordinator and see the message NCP entered failed state. Requesting APP controller restart, Home Assistant says this indicates dropped communication between ZHA and the coordinator’s serial interface. Investigate the local serial connection and coordinator stability before treating the event as a mesh-coverage problem.
Download device diagnostics
For a report involving one device, download that device’s diagnostics from its ZHA device page. Include the diagnostics with the debug log when seeking help. Home Assistant asks issue reports to identify the exact coordinator model and firmware; for a device-specific problem, include the device’s Zigbee signature and diagnostics as well. These details can distinguish a route problem from a device implementation or compatibility problem.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
3. Check coordinator placement and 2.4 GHz interference
Coordinator placement is one of the least disruptive checks and is worth doing before replacing the coordinator. ZHA’s guidance identifies USB 3.x ports, unshielded USB 3.x devices, and unshielded USB 3.x cables as possible interference sources for low-power 2.4 GHz radios.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsMove the coordinator away from noise sources
Inspect the coordinator’s physical position relative to the Home Assistant host, USB peripherals, power supplies, appliances, and Wi-Fi access points. A coordinator plugged directly into a crowded computer may be only a few centimetres from a noisy USB device or metal chassis. If practical, reposition it so the antenna has open space and is not pressed against the host or another radio.
Home Assistant recommends using an adequately long, shielded USB extension cable to place the coordinator away from the host and other potential interference sources. Where the hardware supports it, a USB 2.0 port or a powered USB 2.0 hub can also provide a better physical arrangement than a USB 3.x port. These are documented practices, not guaranteed cures: a move that helps one installation may not solve a different source of interference.
Change one physical variable at a time
Do not move the coordinator, change the Wi-Fi channel, add routers, and replace batteries simultaneously. Make one change, then observe whether the same device or group of devices fails again. Keeping a short change log—date, action, and result—prevents you from losing the evidence needed to identify the real cause.
4. Evaluate mesh coverage before adding hardware
Zigbee is a mesh network. The coordinator is not the only possible path: mains-powered Zigbee devices generally act as routers and can repeat messages for other devices. Battery-powered sensors normally act as end devices and commonly sleep to conserve power, so they do not provide the same always-on relay function.
Look for a coverage gap
Use the map and the physical layout together. A sensor at the edge of the home, in a detached room, behind dense building materials, or separated from the coordinator by several rooms may have an unreliable path. If several distant devices rely on one mains-powered router, that router becomes a useful point to investigate when they fail together.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Add a compatible powered router only when the evidence supports it
If the topology and device locations indicate weak coverage, adding a compatible mains-powered Zigbee router or smart plug can create another path. Compatibility is not universal: some device and router combinations do not work correctly together. Choose hardware documented as compatible with your ZHA setup rather than assuming that every powered Zigbee product will route every other product.
After adding a router, allow the mesh time to discover and use the new path. A newly powered device does not guarantee that an existing end device will immediately select it, and a map may not show every battery-device relationship. Judge the change by whether the affected device remains responsive over its normal reporting interval, not by one instant map snapshot.
5. Check coordinator hardware, firmware, and the serial path
When many devices become unavailable together, or logs show coordinator restarts, inspect the coordinator and its connection to Home Assistant. ZHA recommends supported coordinator hardware and current firmware as part of reliability troubleshooting.
Know the documented adapter status
Home Assistant identifies Home Assistant Connect ZBT-2 as the recommended official adapter for a new ZHA network. ZBT-1 is discontinued and replaced by ZBT-2, but remains supported. This is guidance for choosing hardware for a new network; it does not make replacing a functioning coordinator the default fix for an existing installation.
Consider a coordinator change only when the current adapter, its firmware, or its connection is implicated by diagnostics and logs. Before migrating, record the current coordinator model and firmware and back up the information you need to recover the network. A new adapter can introduce its own setup and migration work, so it should follow evidence of a coordinator-side problem rather than precede basic placement and serial checks.
Keep the serial connection local and stable
For an EZSP coordinator, the NCP entered failed state. Requesting APP controller restart message points to communication loss between ZHA and the coordinator’s serial interface. Check the USB cable, connector, host port, and power arrangement. Avoid carrying the coordinator’s serial connection over Wi-Fi, a wide-area network, or a VPN; Home Assistant’s guidance calls for a stable local serial connection.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
If the coordinator repeatedly drops after the host resumes from sleep, reboots, or experiences USB power changes, correlate those events with the ZHA logs. A serial interruption can make many otherwise healthy Zigbee devices appear offline at once, so repairing the serial path is more appropriate than adding routers for that symptom.
6. Treat channel changes as a targeted intervention
ZHA uses Zigbee channels 11 through 26 in the 2.4 GHz band. A channel change can affect the entire network, so it should not be the routine first step for one unavailable device.
Check Wi-Fi overlap first
Home Assistant’s ZHA guidance says to keep the default Zigbee channel unless there is a specific reason to change it. When interference with Wi-Fi is suspected, first consider setting a static Wi-Fi channel so the wireless environment is predictable. This lets you test whether the Zigbee channel is genuinely overlapping with a persistent Wi-Fi transmission instead of reacting to an assumption about automatic channel selection.
The documentation gives channels 15, 20, and 25 as general Zigbee recommendations, while warning that device support can vary. “Recommended” does not mean universally optimal for every combination of Wi-Fi channel, building, coordinator, and end device.
Plan for the reconnection window
A Zigbee channel change may take up to an hour for devices to reconnect. Schedule it when you can tolerate missing automations and unavailable sensors. Keep a list of devices and their locations, and be prepared to intervene if a particular device does not rejoin automatically. Because the change affects the network rather than one sensor, use it only when logs, radio conditions, or a controlled test provide a specific reason.
7. Investigate the affected device itself
Once the shared infrastructure looks healthy, focus on the device that drops offline. The manufacturer’s model, firmware, power source, and installation location all matter.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Battery-powered devices
Check the battery state and the manufacturer’s device-specific instructions. Home Assistant notes that low battery voltage can cause pairing problems for some battery-powered devices. That statement does not establish that low battery level causes every already-paired device to go offline, so do not use a battery percentage alone as proof of the diagnosis.
Replace the battery with the type specified for the device when its condition is suspect. Home Assistant also recommends fresh batteries before an over-the-air firmware upgrade. After replacement, wake the device according to its instructions and observe whether it reports normally; avoid repeatedly removing and re-pairing it until you have captured diagnostics and logs.
Mains-powered devices
Confirm that the device still has power and has not been switched off at a wall outlet, fuse, or smart-plug control point. A powered Zigbee device that is offline and physically unpowered cannot route traffic or respond to ZHA. If power is present, compare its map links and logs with other devices using the same nearby router.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Pairing trouble is not the same as an offline event
Low voltage, device compatibility, and proximity can all affect pairing. An already-paired device that later becomes unavailable may instead be experiencing a route, interference, coordinator, or serial problem. Keep those cases separate when interpreting manufacturer guidance and ZHA diagnostics.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.8. A practical troubleshooting sequence
Use the following order to minimize disruption and preserve useful evidence.
- Define the scope. List affected devices, power types, failure times, simultaneous outages, and any recent Home Assistant or coordinator restart.
- Capture evidence before changing settings. Open Settings > Connectivity > Zigbee > Show map, save relevant screenshots or notes, review ZHA logs, and download diagnostics for the affected device.
- Check the coordinator’s physical position. Move it away from USB 3.x hardware, unshielded USB 3.x cables, power supplies, appliances, and Wi-Fi access points. Use a shielded USB extension, USB 2.0 port, or powered USB 2.0 hub where suitable.
- Assess the mesh. Compare the affected device’s location with the map and identify whether it depends on a distant or single router.
- Improve coverage only if indicated. Add a compatible mains-powered Zigbee router when the layout shows a real coverage gap, remembering that compatibility varies.
- Check coordinator health. Verify the coordinator model and firmware, inspect USB and power connections, and investigate serial errors. Keep the serial path local; do not route it over Wi-Fi, WAN, or VPN.
- Investigate the device. Confirm power, check a battery-powered device’s battery and manufacturer guidance, and collect its Zigbee signature and diagnostics.
- Consider radio-channel changes last. If Wi-Fi overlap remains a plausible cause, make Wi-Fi channel use predictable first. Change the Zigbee channel only for a specific reason and plan for up to an hour of reconnection time.
- Re-test without stacking changes. Observe the same device across its normal reporting cycle, and record exactly which single intervention preceded any improvement or new failure.
9. Symptoms and the most useful next check
| Observed symptom | Most useful next check | What it can and cannot tell you |
|---|---|---|
| One battery sensor becomes unavailable | Check battery condition, location, device diagnostics, and its map links | Raises device, power, or local-route questions; does not prove the battery is the cause |
| Several devices fail at the same time | Review coordinator logs, serial stability, host restarts, and shared routers | Suggests a shared path or coordinator issue more than an isolated sensor fault |
| Distant devices fail while nearby devices remain stable | Inspect topology and consider compatible powered-router coverage | Supports a coverage investigation; map links may be incomplete for battery devices |
| Failures follow USB or host changes | Move the coordinator, check the cable and port, and review logs | Raises interference or serial-connection concerns; a move is not a guaranteed cure |
| EZSP failed-state message appears | Investigate the local serial connection and coordinator stability | Home Assistant associates this message with dropped ZHA-to-coordinator serial communication |
| Devices remain unavailable after a channel change | Allow the documented reconnection period, then inspect individual devices and logs | A channel change can take up to an hour to reconnect devices and is not proof that the original diagnosis was correct |
10. When to seek a targeted hardware change
Hardware can help, but match it to the evidence.
- Shielded USB extension: useful for repositioning a coordinator away from USB 3.x interference and the host. It is a placement aid, not a guaranteed fix.
- Compatible mains-powered router: appropriate when the map and room layout indicate inadequate mesh coverage. Compatibility varies by device and router combination.
- Coordinator replacement: consider only when the current coordinator, firmware, or serial connection is implicated. ZBT-2 is the documented official recommendation for a new ZHA network; ZBT-1 remains supported despite being discontinued.
- Replacement battery: relevant when the affected device’s battery condition is suspect or before an OTA firmware upgrade, using the manufacturer-specified type.
There is no universal router, battery, coordinator, or channel setting that Home Assistant’s documentation identifies as a guaranteed solution. The useful purchase is the one that addresses a demonstrated placement, coverage, power, or coordinator problem.
11. What to include in a useful support request
If the problem persists, provide enough detail for someone else to reproduce the reasoning rather than only reporting that a device is “offline.” Include:
Recommended Free Tools
- The Home Assistant version and the ZHA integration context.
- The exact coordinator model and firmware.
- The affected device model, Zigbee signature, power type, and battery information when applicable.
- Debug logs covering the failure and recovery attempt.
- The device diagnostics download.
- A description of whether one device or several failed, whether failures were simultaneous, and whether the coordinator or host restarted.
- The relevant network-map observations, including reported RSSI/LQI and any apparent multi-hop route, with the understanding that values vary by Zigbee stack.
- Physical changes already made, including coordinator location, USB cable or port, added routers, Wi-Fi settings, or channel changes.
This information lets support distinguish a device-specific implementation issue from a radio environment, mesh, coordinator, or serial-path failure.
12. The decision rule to keep
When Zigbee devices keep going offline in Home Assistant, do not start with the most disruptive explanation. First establish the scope, then inspect ZHA’s map, logs, and diagnostics. Check coordinator placement and serial stability, evaluate powered-router coverage, and verify the affected device’s power and manufacturer guidance. Only after those checks should you consider a network-wide channel change, and only with a clear reason and time to allow devices to reconnect.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
