If Home Assistant devices repeatedly become unavailable, do not start by deleting and re-pairing them. First find out whether the failure affects one device, one integration, an entire radio network, or Home Assistant itself. That distinction can save hours of rebuilding automations.
1. Identify the scope of the outage
- One device: check its battery, power, range, and recent physical changes.
- Several devices on one protocol: inspect the Zigbee, Z-Wave, Thread, Wi-Fi, or Bluetooth network and its coordinator/router.
- Devices from several integrations: check Home Assistant host health, network connectivity, and recent restarts.
Record which entities are unavailable and when the problem began. Compare the timestamps rather than relying on memory.
2. Check Home Assistant and the integration
Open Settings → System → Repairs and review notifications. Then open the relevant integration and check whether it reports a setup or connection error. Review the log around the first failure; repeated errors after the outage may be symptoms, not the original cause.
3. For Zigbee, check the coordinator and mesh
This broad checklist helps identify which layer is failing; it is not a substitute for a protocol-specific recovery procedure. If the problem is specifically repeated Zigbee dropouts during normal use, follow the Zigbee dropout diagnosis. If the failure began immediately after power returned, use the power-outage recovery guide. Keep this page focused on identifying whether the issue is device-, protocol-, integration-, or host-wide.
Confirm that the coordinator is powered and that the correct serial path is configured. If you use a USB radio, check whether a host restart changed device access or whether another process has taken control of the port. Powered Zigbee routers help extend the mesh; battery-powered sensors generally do not route traffic. After a power outage, give mains-powered routers time to rejoin before judging every sensor.
4. For Wi-Fi devices, test the network first
Check whether the device still appears in the router’s client list and whether its IP address changed. Review Wi-Fi signal, access-point restarts, DHCP reservations, and any recent network-name or password changes. Do not assign a static address inside the DHCP pool.
5. Make one change at a time
Restart only the affected integration when its logs point to an integration-level fault. Restarting the whole host can hide the evidence and interrupt unrelated devices. Avoid factory resets until power, connectivity, and integration setup have been checked.
6. Verify the fix
Watch the affected entity through several normal update cycles. Test the automation that depends on it, and check the log for fresh errors. If the device returns briefly and drops again, the underlying network or power problem may remain.
Frequently asked questions
Should I re-pair every unavailable device?
No. Re-pair only when the device has genuinely lost its network membership or the integration’s documented recovery steps call for it.
Why did everything go offline after a restart?
Possible causes include a coordinator that did not reconnect, a changed device path, network startup timing, or an integration that failed to initialize. The logs and scope of the outage help separate them.
What information helps diagnose the next step?
Note the protocol, integration, device model, Home Assistant installation type, first error timestamp, and whether one device or many failed. Remove credentials and other private information before sharing logs.
Image credit: Unsplash. This is a general troubleshooting guide; menu labels can vary by Home Assistant version and integration.