Searching for why Matter devices keep going offline usually starts after the third time a lock shows “Unavailable” in Home Assistant or “No Response” in Apple Home, then comes back on its own an hour later. For a device that previously worked, check the controller, transport and device state before repeating commissioning. Thread devices also depend on a border router for access from the LAN; a full battery does not prove that the rest of that path is available. Here are the five places the path breaks, in the order to check them.
First, sort your outages by transport
Which devices dropped, and when, does most of the diagnosis.
- Every Thread device went at once, Wi-Fi devices fine: the border router.
- One battery-powered Thread device drops on a schedule (about every 30 minutes, or overnight): sleep or subscription.
- Several devices lose control after previously working: investigate the network path in cause 4.
- The manufacturer app says offline while Home Assistant or Apple Home controls it fine: the app, not the device.
The transport comparison covers why the two radios fail differently.
Cause 1: the border router went away
When several Thread devices disappear together, check whether their border router lost power, rebooted for an update, or lost its LAN connection. Compare the outage time with the hub’s availability before resetting individual accessories.
A second border router can provide another path when both share the device’s Thread network and have useful coverage. Confirm network membership before buying another box. The Thread border router guide covers count and placement; check controller uptime separately if the same hub also hosts it.
Cause 2: two Thread networks pretending to be one
This is the sneaky one. Each ecosystem historically formed its own Thread network with its own credentials, and devices cannot roam between them.
The Thread Group admits this hurts: “This fragmentation of Thread devices over multiple networks could weaken the overall mesh network resilience and connectivity” (Thread Group). Thread 1.4’s answer is credential sharing, “a secure procedure that allows sharing administrative access to an existing Thread network and extracting its network credentials,” so a new border router joins the existing mesh instead of forming its own (Espressif).
On Home Assistant this surfaces as the “preferred network” setting: a March 2026 core issue documents an IKEA Thread motion sensor that became “Unavailable” about 30 minutes after pairing on Home Assistant 2026.3.3; the fix was to mark the Sonoff dongle’s Thread network as preferred, factory-reset the sensor and pair it again (home-assistant/core #166317). The Thread border router guide explains how to check which networks the routers actually share.
Cause 3: battery devices sleeping through their subscription
Battery Thread devices are Sleepy End Devices, “normally disabled, wakes on occasion to poll for messages from its parent,” and each one “attaches to exactly one Mesh Extender” (OpenThread). Silicon Labs’ Matter SDK defaults the idle poll to 30000 ms, and while asleep the device “relies on its associated Thread router to buffer any incoming message” (Silicon Labs).
The controller holds a subscription and expects periodic reports. When the parent goes away, or the subscription lapses, the controller marks the device unavailable. Matter’s Intermittently Connected Device design exists for this: the check-in protocol “is a fail-safe mechanism which allows an ICD to notify a registered client that it is available for communication when all subscriptions between the client and ICD are lost” (Silicon Labs). Older devices lack it, which is why the reset ritual works. Apple’s No Response steps: “Disconnect third-party Thread accessories from power for 5 minutes by unplugging them or removing their batteries. Then reconnect third-party Thread accessories and wait 10 minutes for the Thread network to stabilize” (Apple Support). That forces a fresh parent and a fresh subscription. If the same sensor drops every few days, give it a mains-powered Thread plug or bulb nearby as a second parent.
Cause 4: your network is filtering multicast or IPv6
Local IPv6 and mDNS must reach the controller for both Matter transports. A changed access-point setting, client isolation or VLAN boundary can interrupt an installation that previously worked, including the LAN side of a Thread border router. Follow IPv6 requirements for Matter and Thread for multicast behavior, host routes and discovery checks; keep that network investigation separate from replacing the device or recommissioning it.
Cause 5: it is the app, not the device
If your controller runs the device fine but the manufacturer’s app says offline, the app is what is offline: Matter control is local, and the vendor app usually talks to a cloud over a separate channel. The offline behaviour post covers which pieces need the internet.
A diagnostic order that does not waste your evening
- Border router: powered and connected to the controller’s LAN. Compare hub uptime with the outage.
- Thread networks: Home Assistant’s Thread page lists every border router and its network. Aim for one, marked preferred.
- A sleepy device on a schedule: pull the battery for five minutes, wait ten, give it a mains-powered neighbour.
- Network path: follow cause 4 and change one setting at a time so its effect is clear.
- Only then the device itself: firmware, signal, and whether it is actually faulty.
Zigbee people will recognise the list; the Zigbee “unavailable” guide on homeassistanthq.com follows the same discipline with a coordinator in place of a border router. Keep the protocol distinction clear: Zigbee uses its own coordinator and mesh, while this guide addresses a device already commissioned through Matter.
Related across the network
- Home Assistant Hardware: What to Run It On — homeassistanthq.com
- Home Assistant OS vs Container: Which Install Method to Pick — homeassistanthq.com
