Does Matter Work Without Internet? Offline Limits

The search phrase “does matter work without internet” gets asked for two reasons: the fibre just went down and the lights stopped responding, or someone is deciding whether to buy into Matter and wants to know what happens when it does. The short answer is yes for control and no for the moments around control. A Matter device already paired to a controller on your LAN keeps taking commands with the WAN unplugged. First-time pairing, remote access, voice assistants and most manufacturer apps are a different story, and every major platform’s documentation says so once you read past the headline.

What the platforms actually promise

Matter is a local IP protocol. Commands go from a controller to a device over Wi-Fi, Ethernet or Thread with no cloud relay in the middle. The Home Assistant Matter docs put it plainly: “Matter products run locally and always allow local control, with device control done without the need for any internet connection or cloud services.”

The commercial ecosystems agree, with a qualifier each. Google’s Matter help page says that “when you give smart home commands to your Matter-enabled devices from within your home, these commands are carried out locally,” and in the next breath that “while you’re away from your home, these commands are carried out by connecting to the cloud over the internet.” Amazon’s developer documentation sells a Matter connection to device makers because it “enables Alexa to control your device locally during Internet outages or when your add-on isn’t available.” Apple’s home hub page frames the hub as the thing you set up “to control your smart home accessories while you’re away from home”: the hub does the local work, iCloud does the remote work.

So the protocol keeps its promise. The question is which parts of your setup are Matter and which are the wrapper around it.

The parts that still need a WAN

Commissioning. Pairing a new device is the one step that is hard to do fully offline. During commissioning the controller runs device attestation, checking the device’s certificate chain (DAC, then PAI, then a PAA root) to confirm it is a certified product. The PAA roots are published in the CSA’s Distributed Compliance Ledger, and as Silicon Labs’ DCL documentation explains, “the Certification chain must start with a trusted root certificate. This is where the DCL comes in.” A controller that has never synced those roots fetches them from the internet. On top of that sit the platform accounts: Apple’s troubleshooting steps require you to “turn on iCloud Keychain and two-factor authentication,” and its Matter accessory page notes that “paired Matter accessories sync using iCloud Keychain.” Home Assistant adds that “some vendors may require you to set up an account before you can enable Matter support for some products.” Pair everything while you are online; treat an outage as a control-only window.

Remote access. By definition. Google’s page is explicit that away-from-home commands go through the cloud, and Apple’s hub exists for it. Remote access with no vendor cloud means a VPN into your LAN plus a local controller, which is a homelab project rather than a Matter feature.

Voice. Speech recognition on a HomePod, Nest speaker or Echo runs in the cloud. The Matter half of “turn off the lamp” is local; the half that turns your voice into a command is not.

Manufacturer apps. This is where people get burned. The Matter Alpha explainer by James Bruce describes an August 2024 test in which “nearly all of my Matter devices” worked offline through Apple Home while the same devices “all failed to work through the manufacturer’s own app unless they had Bluetooth control.” A Govee lamp answered the Home app and was reported offline by the Govee app at the same moment. The device was fine; the vendor app was talking to a server it could not reach.

Firmware updates. Home Assistant’s update entities “check the DCL every 12 hours for updates.” A background job, not an outage problem, but it stalls until the WAN returns.

Thread and border routers during an outage

A Thread border router “works as a special hub to connect all of your Thread devices together by creating a wireless Thread network,” and its job is to move IPv6 packets between that mesh and your LAN. The WAN is not in that path. A HomePod mini or Nest Hub keeps routing Thread traffic whether or not it can reach Apple or Google.

What is less documented is what a consumer hub does after a power cycle with no internet. The border router half should rejoin the mesh. Whether the controller half is fully functional before it has phoned home is vendor behaviour none of the support pages spell out, so do not assume it. Running two border routers with the same Thread credentials, covered in the border router placement guide, removes a single reboot as a failure point; it does not fix a controller that insists on the cloud.

Building a setup that survives the WAN dropping

Four decisions do most of the work.

1. Put a local-first controller on the fabric. Home Assistant runs its controller as the Matter Server app, described in the docs as “a separate process” connecting “your Matter network (called Fabric in technical terms) and Home Assistant.” Add the OpenThread Border Router app and a supported radio and the whole path is on your hardware. The catch is that apps need the Supervisor, so Home Assistant OS or a VM; the install method comparison on Home Assistant HQ covers why Container installs make this harder.

2. Use multi-admin instead of picking a side. A device can sit on the Apple or Google fabric and the Home Assistant fabric at once. Keep the phone ecosystem for the family and the local controller for automations, so an outage takes out the convenient interface but not the house. The Matter controller explainer walks through sharing a device across fabrics.

3. Keep IPv6 and multicast flowing on the LAN. Google warns that without IPv6 “the setup process may initially appear to succeed at times” but “control and other functionalities eventually fail,” and Home Assistant’s troubleshooting section insists that “IPv6 (multicast) traffic travels freely from your network to the Home Assistant host.” An IoT VLAN with no mDNS reflection breaks Matter whether the internet is up or not; the UniFi VLAN segmentation guide covers the reflection you will need. If pairing fails before you ever reach an outage, start with why Matter pairing fails.

4. Rehearse it. Pull the WAN cable from your router, leave the router and switches powered, and walk the house. Lights and plugs on the local controller should respond; vendor apps and voice assistants should not. A device that stops working through Home Assistant was never on the local path, and a Sunday afternoon is a better time to learn that than a storm.

None of this makes a smart home that needs zero internet, and it does not need to. The cloud is fine for the remote and voice layers. What Matter buys you is that the boring, load-bearing part, a switch telling a bulb to turn on, has no server in the way.

Related across the network

• Zigbee vs Z-Wave vs Thread: Which Mesh to Build — homeassistanthq.com
• Home Assistant Hardware: What to Run It On — homeassistanthq.com
• Home Assistant OS vs Container: Which Install Method to Pick — homeassistanthq.com
• Zigbee Devices Going Unavailable: How to Fix It — homeassistanthq.com
• A $200 N100 Homelab: 11 Services, ~8W Idle, Low Maintenance — minilabhq.com