Troubleshooting
When all smart home devices go offline at once, do not start with individual device resets. A whole-house outage is usually a shared layer: router or internet, a hub or bridge, a cloud account, an ecosystem controller, local discovery, or one automation owner exposing stale status everywhere.
Fast rule: if more than one brand or room failed at the same time, pause device-by-device troubleshooting and prove which common layer disappeared first.
Start with the outage boundary
| What still works | Most likely shared layer | Best first move |
|---|---|---|
| Phones and laptops are offline too. | Internet service, router, modem, gateway, or whole-home Wi-Fi. | Fix the network before opening every smart-home app. |
| Normal internet works, but every smart device is offline in one app. | Alexa, Google Home, Apple Home, SmartThings, or Home Assistant status/exposure layer. | Check one native device app before resetting devices. If native control works, repair the ecosystem layer. |
| Wi-Fi devices work, but Zigbee, Z-Wave, Matter, or Thread devices vanished together. | Hub, bridge, coordinator, Matter controller, Thread border router, or protocol mesh infrastructure. | Inspect the hub or bridge path before touching endpoints. |
| Vendor apps work, but voice assistants say everything is unavailable. | Cloud integration, account link, skill/service token, or duplicated room graph. | Relink the assistant only after native app control is proven healthy. |
| Only one room or edge area failed. | Coverage, power, backhaul, bridge placement, or local interference. | Treat it as a location problem, not a whole-platform outage. |
Run three checks before resetting anything
- Check one normal internet device. If phones or laptops are also failing, the smart home is only a symptom of a network outage.
- Check one native app for a device that looks offline. If it works there, the device is probably healthy and the control layer is stale.
- Check the main hub, bridge, or controller. If every device behind one box disappeared, restart or inspect that box before resetting endpoints.
Read the failure by grouping
A whole-house offline alert is useful only if you group it correctly. All Wi-Fi clients failing points to router or gateway health. All bridge devices failing points to that bridge. All Apple Home accessories showing No Response while vendor apps work points to Apple Home hub, HomeKit bridge, Matter controller, or local discovery state. All Home Assistant entities unavailable while the local dashboard works points to integrations or exposed bridges, not the server itself.
- One platform sees the outage: fix that platform's account, controller, room graph, or exposure path.
- Every platform sees the outage: look lower: power, router, Wi-Fi, hub, bridge, or vendor cloud.
- One protocol family disappeared: focus on the coordinator, bridge, repeater mesh, or Thread border router.
- One device family disappeared: check that vendor bridge, cloud service, firmware update, or account link.
Common Questions
Why does this kind of failure keep coming back even after basic fixes?
Because a lot of smart-home failures are shared-layer problems rather than one-time glitches. If the pattern keeps returning, follow the shared failure-layer guide instead of treating each device as a separate mystery.
How do I know whether this is Wi-Fi, protocol, or cloud trouble?
Batch failures often point to Wi-Fi or router policy, while one protocol family failing points more toward architecture. Use Wi-Fi load and protocol guidance to separate those layers cleanly.
What should I check before replacing hardware?
Check whether the house already has overloaded Wi-Fi, weak 2.4 GHz settings, or an unclear hub role. Replacements work better after the control and network layers make sense.