Short Answer: Local Control Survives, Cloud Convenience Does Not

Home Assistant can keep working without internet when the automation, device integration, and network path are local. An automation is the rule that makes something happen, and an integration is the software path Home Assistant uses to talk to a device or service. Local control means the command stays inside the house instead of going through a vendor server first. A local Zigbee, Z-Wave, ESPHome, Shelly, MQTT, or Matter path should keep working after setup if the Home Assistant hub, router, Wi-Fi, and radios still have power.

Matter is also designed for local control, and Home Assistant's official Matter docs say Matter products can be controlled without internet or cloud services. The caveat is everything around Matter: some vendors need an account before enabling Matter, Thread devices need a powered Thread border router, and voice assistants, remote access, phone notifications, cloud cameras, firmware updates (device software updates), and cloud-polling integrations that ask a vendor cloud for status can still stop or degrade.

The homeowner rule is simple: local automations in Home Assistant first, family apps second, cloud features optional.

Safe outage planning: never make locks, garage doors, alarms, cameras, HVAC, or medical-adjacent automations depend only on a smart-home app. Keep physical keys, wall controls, local sirens, manual garage release knowledge, and ordinary thermostat access.

Why This Question Is Hot Right Now

This is not a theory question. In a Reddit r/homeassistant internet-outage thread, users separated cloud Wi-Fi switches from local Shelly relays because the local Wi-Fi network can still exist while the internet is gone. Another recent Reddit thread asked for an "offline mode" while Home Assistant still works. On the Home Assistant Community forum, a May 2026 Matter thread reported an outage where Hue continued working but Matter devices failed after a restart because a beta Matter Server path appeared to need downloads. A separate Home Assistant Community post asked how to move an Alexa-centered home toward offline use.

The confusion is understandable. People use "Wi-Fi" to mean "internet," but they are not the same thing. Wi-Fi is the local radio network inside the house. Internet is the outside connection from the modem or fiber box. A Wi-Fi device can be fully local, fully cloud-dependent, or both, depending on its integration.

That is why Tara treats internet-outage planning as an architecture question, not a brand question. You need to know where each command goes, which hub owns the automation, and whether the device has a real local path.

What Still Works Without Internet?

Use this table as a practical map. It separates official support, local control, cloud dependency, Matter or HomeKit paths, and community caveats. Cloud polling means Home Assistant asks a vendor cloud service for state or control. Cloud push means the cloud sends updates to Home Assistant. Both can need internet. Local polling and local push talk directly inside the home.

Path Official support Local control and cloud dependency Matter, HomeKit, and ecosystem path Community caveats
Home Assistant local integrations
Examples: Zigbee through ZHA, Z-Wave JS, ESPHome native API, Shelly local, MQTT on a local broker.		 Home Assistant documents integration IoT classes, meaning labels for how an integration talks, such as local push, local polling, cloud push, and cloud polling. Local integrations can keep working when the outside internet is down, if the Home Assistant box, router, Wi-Fi, switches, and radio adapters still have power. HomeKit Device and HomeKit Bridge can be local paths in the right setup, but they solve different jobs from Matter multi-admin. Local does not mean indestructible. A dead router, failed USB radio, bad DHCP lease, broken local discovery traffic called mDNS, or rebooting add-on can still take devices offline.
Home Assistant Matter devices
Examples: Matter plugs, bulbs, locks, thermostats, bridges, and Thread sensors already commissioned to Home Assistant.		 Home Assistant says Matter products run locally and do not need internet or cloud services for device control. Control should be local after setup. Adding the device to a controller, vendor account setup, Matter certificate checks, add-on updates, and firmware updates can still involve internet. Matter over Wi-Fi uses the home network. Matter over Thread also needs a powered Thread border router and reachable Thread credentials. Recent forum demand shows offline Matter can still be tripped by beta server behavior, VLAN rules that split the house into network zones, IPv6 network addressing, mDNS local discovery, or restarting services during an outage.
Apple Home
Examples: HomePod mini, HomePod, Apple TV, Apple Home Matter accessories, Thread-enabled Matter accessories.		 Apple says a home hub is required to add Matter accessories to Home, and Thread accessories require a Thread-enabled home hub or compatible border router. Same-home control can be local in the right Home hub setup. Remote control, sharing, some Siri/account behavior, and iCloud-backed features need the Apple ecosystem path to be healthy. Apple can be the first Matter controller, or Home Assistant can pair first and share outward. HomeKit Device is a separate Home Assistant path for HomeKit accessories. If several manufacturers stop responding, Apple tells users to check the same Wi-Fi network, home hubs, bridges, Thread accessories, modem, router, and VPN/security software.
Google Home
Examples: Nest Hub, Nest Mini, Google Home Matter hub, Google Home app controls.		 Google says Matter is designed to work locally over Ethernet, Wi-Fi, and Thread, and Google Matter-enabled devices can act as hubs. Matter device control can be local on supported hubs. Works with Google Home cloud-to-cloud devices, remote features, voice processing, and account services are separate questions. Google Home can pair Matter devices first, then share to Home Assistant, or receive devices shared from another Matter controller. Do not treat "Google Home can see it" as proof that your exact routine, voice command, or non-Matter device will work during an internet outage. Test it.
Amazon Alexa
Examples: Echo and eero Matter controllers, Thread-enabled Echo or eero border routers, Alexa smart home skills.		 Amazon says Alexa can discover and control Matter devices over local Wi-Fi or Thread, and skill-connected devices can add Matter for local control during internet outages. Direct Matter paths can be local. Traditional Alexa smart-home skills often use cloud infrastructure, and some Amazon-managed device programs can include cloud services. Alexa can join Matter devices through multi-admin and can be useful for family voice control after Home Assistant owns the automation. Assume Alexa routines and voice are cloud-risky until tested. Keep critical automations in Home Assistant if the goal is outage resilience.
Samsung SmartThings
Examples: SmartThings compatible hubs, Edge Drivers, Matter Wi-Fi, Matter Thread, Zigbee, Z-Wave.		 SmartThings developer docs say hub-connected Matter, Zigbee, Z-Wave, and some Wi-Fi devices using Edge Drivers, the hub's local device software, run locally. Hub-connected local devices can keep working locally. Cloud-connected devices, app services, remote control, and some automations can still require SmartThings cloud paths. SmartThings supports Matter controllers and can share Matter devices with other ecosystems where device type and platform support allow it. Check whether the exact device and routine show local execution. Community reports still separate "Edge driver is local" from "every automation involving it is local."

The Outage Test That Actually Answers the Question

Do not wait for a storm or ISP outage. Test the house on purpose during a calm hour.

  1. Keep the local network powered. Put the Home Assistant hub, router, Wi-Fi access point, network switch, Thread border router, Zigbee coordinator, and Z-Wave stick on a UPS if outage behavior matters. If the router is off, "local control" has nowhere to travel.
  2. Disconnect the outside internet, not the home network. Unplug the modem's internet feed or the router's internet port. Do not turn off the router or Wi-Fi. The point is to simulate no outside internet while the home network stays up.
  3. Open Home Assistant locally. Use the local URL or app while your phone is on home Wi-Fi. If you only know the remote URL, fix that before you call the system outage-ready.
  4. Trigger real automations. Walk past a motion sensor, press a wall button, open a contact sensor, change a thermostat mode, and run a lighting scene. Watch whether the automation fires without cloud delay.
  5. Check the integration class. In Home Assistant docs, local push and local polling are the friendlier outage paths. Cloud push and cloud polling need internet for the integration path.
  6. Test family apps honestly. Try Apple Home, Google Home, Alexa, and SmartThings separately. Touchscreen/app control, voice control, routines, and remote control can behave differently.
  7. Record failures by cause. Mark each failure as power, home network, radio, local discovery or network addressing, cloud integration, voice assistant, remote access, notification, camera cloud, or firmware/update path. That turns a vague outage into a fixable list.

The Matter Details Homeowners Need

Matter is the shared smart-home language used by many newer devices and ecosystems. It can run over Wi-Fi, Ethernet, and Thread. Thread is a low-power wireless mesh for small devices such as sensors, plugs, bulbs, and locks. A Thread border router is the bridge between that Thread mesh and the normal home network.

The good news: Matter control is local at the protocol level, and Home Assistant's Matter implementation is officially certified. The caveat: local control does not remove every internet touchpoint. A device may still use a vendor app for setup or firmware updates. A controller may need Matter certificate checks when adding a device. A mobile phone may hold the Thread credentials needed to add a device. A cloud voice assistant may be the convenient interface even though the device itself is local.

That means Matter is a strong outage ingredient, not a complete outage plan. A Matter plug paired to Home Assistant can be local. A Matter plug paired to Google Home and shared to Home Assistant can also be local for device control. But if the only way the family uses it is "Hey Google, turn off the lamp," you must test whether that command still works when the internet is down.

What Usually Breaks During an Internet Outage

Cloud integrations

Cloud integrations are the obvious failure point. If a switch, thermostat, camera, appliance, or bridge only talks through a vendor account, Home Assistant may lose control even though the device is physically on the same Wi-Fi. Home Assistant's IoT class labels are the first place to check.

Voice assistants

Alexa, Google Assistant, and Siri can be useful family interfaces, but voice is not the same as local automation. A Home Assistant automation can run locally while a voice command fails because speech recognition, account routing, or cloud skill fulfillment is unavailable. Treat voice as convenience unless you have tested the exact local path.

Remote access and notifications

If the home has no internet, you are not going to reach it from outside through Nabu Casa, VPN, Tailscale, reverse proxy, or a vendor app unless there is another outside internet path, such as cellular backup. Phone push notifications can also depend on Apple, Google, Home Assistant Cloud, or vendor cloud messaging. Local sirens, dashboards, wall tablets, and SMS through a separate cellular device are different designs.

Cameras and recordings

Cloud cameras are often the first disappointment in an outage. A camera can still have power and Wi-Fi but lose cloud recording, cloud alerts, thumbnails, or app access. If recording matters during internet outages, use local camera standards such as RTSP or ONVIF, a local NVR (network video recorder), or another documented local recording path. For privacy, do not create hidden recording behavior that household members do not understand.

Updates, firmware, and reboots

A system that controls devices locally while running can still need internet during setup, updates, add-on startup, certificate checks, or firmware downloads. The May 2026 Home Assistant Community Matter thread is a good warning: do not assume a beta add-on restart during an outage behaves the same as a stable already-running local controller. If outage reliability matters, test a controlled restart without outside internet after updates.

Where Should Important Automations Live?

Put important automations in one local system. For most Tara-style homes, that means Home Assistant. Apple Home, Google Home, Alexa, and SmartThings can still be useful for family dashboards, voice shortcuts, and platform-specific devices. They should not each run their own version of the same motion light, lock routine, water shutoff, or garage alert.

Keeping automations local does not help if the integration underneath them is cloud-only. Check both layers: where the rule runs and how Home Assistant reaches the device.

For safety devices, make the automation helpful but not the only line of defense. A leak sensor should have a local alarm or visible dashboard state. A lock should have a physical key or keypad fallback. A garage door should keep its ordinary wall button and manual release. A thermostat should still be usable from the wall. A camera plan should distinguish local recording from cloud notifications.

The Best Practical Setup

If you want the home to feel normal during an internet outage, build it this way:

  1. Use Home Assistant as the local automation brain. Keep lights, sensors, leak response, occupancy, basic climate logic, and security-adjacent alerts in one place.
  2. Prefer local device paths. Zigbee, Z-Wave, ESPHome, Matter, local LAN device interfaces, HomeKit Device, and local MQTT can all be good when configured plainly.
  3. Keep the network alive. A small UPS for the hub, router, access point, switches, and radio bridges matters more than another app.
  4. Use family apps as control surfaces. Share Matter devices or selected Home Assistant entities to Apple Home, Google Home, Alexa, or SmartThings only where they make the house easier to use.
  5. Document cloud dependencies. Write down which devices lose remote access, voice, firmware updates, cloud recordings, push notifications, or account features when internet is gone.
  6. Run a quarterly outage drill. Unplug the outside internet feed, test the top 10 automations, then fix one weak path at a time.

Tara's Interpretation

The internet outage question is really a trust question. A homeowner does not care whether a device is Wi-Fi, Thread, Zigbee, Z-Wave, HomeKit, Matter, or cloud polling. They care whether the hallway light turns on, the leak alert happens, the thermostat is usable, and the house does not become confusing when Comcast, fiber, or a vendor cloud has a bad day.

Tara's bias is boring local control: Home Assistant owns the important automations, the network and radios stay powered, family apps get only the surfaces they need, and every cloud feature is treated as convenience. Matter helps because it gives modern devices a local cross-ecosystem path. It does not remove the need for a plan.

These guides cover the setup decisions that usually decide whether outage mode is calm or confusing.

FAQ

Will Home Assistant keep working if the internet is down?

Yes, for local integrations and local automations, as long as your Home Assistant hub and local network are still powered. Cloud integrations, remote access, push notifications, cloud speech, cloud cameras, and voice assistant paths may fail or degrade.

Do Matter devices need the internet?

Matter device control is local. However, setup, vendor app enrollment, certificates, firmware updates, Thread credential sharing, remote access, and platform features can still need internet. Test the exact device after setup.

Will Thread devices work without internet?

Thread devices can keep working locally if the Thread border router, home network, and controller are powered and reachable. Thread does not remove the need for a router, IPv6, local discovery traffic called mDNS, and a healthy controller.

Will Alexa or Google Home still control my lights?

Sometimes, especially with supported Matter paths, but do not assume it. Non-Matter cloud skills, voice processing, routines, and remote features can still depend on cloud services. If the light must work, put the core automation in Home Assistant and test the voice path separately.

How do I test safely?

Keep power on, unplug only the outside internet feed from the modem or router, then test local dashboards, automations, wall switches, Matter devices, Thread devices, family apps, and cameras one by one. Do not test by cutting power to the whole network unless you are specifically testing UPS behavior.