Short Answer: Find the Failed Layer Before You Rebuild Anything
The most useful first test is not a reset. It is checking where the device still works. If every Matter-over-Thread device is unavailable in Home Assistant but still responds in Apple Home, Google Home, Alexa, or SmartThings, the low-power Thread network is carrying traffic. Start with Home Assistant's Matter Server—the local service that maintains its trusted device connections—and the network path between Home Assistant and the Thread border router.
If the same devices are offline in every app, look at the Thread side: the border router, powered devices that relay Thread traffic, radio interference, or device software. If only one sensor has failed, do not treat the whole house as broken. Check that device's power, location, software version, and nearest powered Thread route.
Before updating, download Matter diagnostics, save the Matter Server log, and make a Home Assistant backup. Then update one relevant component at a time, wait for any migration and reconnection to finish, and retest. The sections below show the exact safe order.
Reset-last rule: factory resetting erases the device's Thread network membership and its trusted links to Home Assistant, Apple Home, Google Home, or another controller. It can turn one offline device into a full re-pairing and automation-repair job.
The Four Layers That Can All Say “Unavailable”
Matter-over-Thread combines two different jobs. Thread is the low-power radio network. Matter is the common language and security relationship that lets Home Assistant control the device. Home Assistant can show the same word—unavailable—when either job fails.
A Thread border router, such as a HomePod mini, compatible Apple TV 4K, Nest Hub (2nd Gen), Nest Wifi Pro, Home Assistant Yellow, or a Home Assistant Connect radio running OpenThread, connects the Thread mesh to your normal Ethernet or Wi-Fi network. It forwards encrypted traffic; it is not the automation brain.
A powered Thread router is different. A mains-powered plug, bulb, or other eligible Thread device may relay messages inside the mesh. Most battery sensors sleep to save power and do not extend range. Finally, a Matter fabric is the trusted relationship between a controller and a device. Apple Home and Home Assistant can each have a separate fabric on the same device.
Use the Symptom Pattern to Pick the Next Check
| What you see | Most likely area | Do next | Avoid |
|---|---|---|---|
| One battery device is offline | Device power, firmware, wake cycle, or its local mesh path | Wake or power-cycle that device, inspect its last-seen time, and test it closer to a powered Thread router. | Restarting every hub or rebuilding the Thread network |
| Several nearby devices fail together | A powered Thread router or radio-coverage branch | Check whether a powered plug, bulb, or border router in that area lost power or disappeared from the Matter Server map. | Assuming battery sensors will relay for one another |
| All Thread devices fail, but Matter-over-Wi-Fi still works | Thread border router, Thread mesh, IPv6 route, or OpenThread app | Check the Thread integration, border-router status, OpenThread Border Router app logs if used, and local IPv6 reachability. | Deleting the Matter integration |
| Thread devices work in Apple or Google but not Home Assistant | Home Assistant Matter Server, Matter fabric, or local path to the border router | Update and restart Matter Server, then check IPv6, multicast, and whether the device still appears in Matter Server. | Factory resetting a demonstrably healthy device |
| Thread and Wi-Fi Matter devices both fail | Matter Server, integration, host networking, or a recent update | Check Matter Server first and review its logs or backup history before changing the radio network. | Changing the Thread channel |
The Recovery Order That Preserves Your Pairings
1. Let the Network Settle, Then Scope the Failure
After a Home Assistant update, Matter Server restart, border-router restart, or full power outage, give powered routers and sleepy devices several minutes to reconnect. Do not stack more restarts while the mesh is still rebuilding its routes.
Before restarting anything else, open Settings > Devices & services > Matter, use its menu to select Download diagnostics, and save the current Matter Server log. Go to Settings > System > Backups > Backup now and include the Matter Server app and configuration. Then test one affected device in every controller that already knows it, one Matter-over-Wi-Fi device, and one non-Matter Home Assistant device. Write down the first failure time and what changed immediately before it. This separates a device problem from a Thread problem, and a Thread problem from a Home Assistant controller problem.
2. Check Matter Server Before the Thread Radio
Open Settings > Devices & services > Matter. This integration is Home Assistant's connection to the local Matter Server. Then open Settings > Apps > Matter Server and confirm the app is running. Update Home Assistant, Matter Server, and the OpenThread Border Router app when you use it. Home Assistant's June 23, 2026 Matter upgrade moved the server to matter.js, improved reconnection, and added a clearer Thread and Wi-Fi network view.
Go to Settings > Apps > Matter Server > Open Web UI, choose Thread, and inspect the network map. Look for the border router, the affected device, its reported role, and whether a group of devices vanished behind the same powered router. Refresh before trusting an old gray or missing connection. The view fills progressively, some devices do not expose every diagnostic, and roles can change. The map is evidence, not a reason to reset everything it cannot currently draw.
If Matter-over-Wi-Fi devices are also unavailable, stay on the Matter Server and host-networking path. A Thread radio change cannot repair a controller that has lost every Matter device.
3. Check the Thread Network and Its Border Router
Go to Settings > Devices & services > Thread > Configure. Confirm that the network carrying the affected devices is still listed and has an active border router. Seeing several network names does not mean devices can move between them; different Thread networks can use different credentials—the network name and password-like key used during setup.
If Home Assistant owns the Thread network, check that its OpenThread Border Router app is running and that the radio is still attached. If Apple, Google, Amazon, IKEA, Aqara, or SmartThings owns the network, check that the platform's border router is powered and healthy. Restart one relevant border router, then wait and retest. Power-cycling every router at once removes the redundant paths you are trying to diagnose.
Do not create a new Home Assistant Thread network as a quick fix. A second network does not strengthen devices that remain on the first one. It can also make the phone used for pairing choose the wrong credentials next time.
4. Check Local IPv6 and Device Discovery—Even If the Internet Works
Thread is an IPv6-only network. In this context, IPv6 means the local addressing Home Assistant uses to reach devices through the border router; your internet provider does not need to give you public IPv6 for local Thread to work.
Home Assistant, Matter Server, and the border router need a clean local route. Home Assistant's official Thread troubleshooting says the host and home router must support IPv6, and routed setups need IPv6 forwarding. Mesh Wi-Fi, guest networks, client isolation, firewalls, and separate VLANs—separate network segments—can block the local device-discovery traffic called multicast DNS, or mDNS, even while ordinary web browsing works.
- Keep Home Assistant and the Thread border router on the same trusted LAN while diagnosing.
- On a virtual machine, confirm that its network is bridged into the LAN and has working local IPv6—not only IPv4.
- For a self-managed Matter Server container, follow the matter.js host-network and IPv6 requirements. Do not copy Linux forwarding settings from a border-router guide onto a host that is not acting as a router.
- On a routed or VLAN setup, verify IPv6 routing and multicast forwarding rather than opening broad internet-facing firewall rules.
- Check mesh Wi-Fi settings for client isolation, multicast filtering, or mDNS controls. Do not blindly disable every network-protection feature.
If devices work in Apple Home but not Home Assistant, this local path is especially important: the Apple controller may be beside the Thread mesh while Home Assistant sits across a filtered network boundary.
5. Read the Log Clue Before Choosing a Fix
| Log clue | Plain-English meaning | Check next |
|---|---|---|
Resolving (no address known) | Matter Server has not learned a usable local address for the device. | The device, border router, Thread address publication, and mDNS path |
ENETUNREACH or route unavailable | Home Assistant has no working IPv6 route to the device. | Border-router status, IPv6 route advertisements, VM/container networking, and recent prefix changes |
| Address resolves, then CASE or retransmission timeout | Discovery worked, but the device did not answer the secure Matter session. | Device attachment, Thread route, firewall state, and the border router |
Repeated ChannelAccessFailure | The radio repeatedly found its channel too busy. | 2.4 GHz congestion and the coordinated channel-change path |
NoAck | A message was not acknowledged. This can be normal while a battery device sleeps. | Persistent errors on an always-powered device point more strongly to range, power, or hardware |
An mDNSPlatformSendUDP ... error 99 message tied to an internal Docker veth interface is documented by Home Assistant as commonly cosmetic. Do not rebuild the Thread network because of that line alone.
6. Treat One Failed Device as One Failed Device
For one sensor, lock, shade, plug, or bulb, check its power and firmware before moving infrastructure. Wake a battery device using the maker's documented action, or power-cycle a mains-powered device once. Test it temporarily nearer a powered Thread router that belongs to the same Thread network.
If a whole cluster fails behind one powered device, restore that routing device first. If the failed device works in another Matter controller, use that working platform to confirm firmware and status. Home Assistant's Matter page also shows the network name and device role for paired devices, which can help confirm that you are looking at the right mesh.
7. Change the Radio Channel Only When the Logs Point There
Thread, Zigbee, Bluetooth, and 2.4 GHz Wi-Fi share busy radio space. Home Assistant documents repeated ChannelAccessFailure messages as evidence that the Thread radio cannot get airtime. A sleeping battery device can produce an occasional NoAck; persistent errors from an always-powered device point more strongly to range, power, or hardware.
If the evidence shows interference, use Home Assistant's coordinated Thread channel-change tool. It schedules the move so devices can follow. Do not manually erase the network or select channel 25 or 26 only because it fixed someone else's house; Wi-Fi layout, Zigbee channel, region, and hardware all matter. Our Thread channel guide covers the safe sequence.
8. Repair Only the Controller Relationship That Failed
If the device is healthy in another ecosystem but Home Assistant cannot restore its secure Matter connection, the last repair before a factory reset is the Home Assistant fabric—its trusted controller relationship—not the whole Thread network. Take a Home Assistant backup and save the device's original setup label first.
Do not repeatedly share a device that Home Assistant still lists. That can leave stale or duplicate nodes. First save diagnostics and verify that another controller still operates the device. If the Home Assistant relationship truly must be removed, record its device controls—called entities—and automations, then use Delete on that device's Home Assistant page. Do not remove the remaining working platform from Manage fabrics, and do not use this path when Home Assistant is the only controller.
Only after the old Home Assistant relationship is cleanly removed should you use the working controller to generate a fresh Matter sharing code and add the device in Home Assistant as one that is already in use. The fresh code is temporary; it is not the original box QR code. This keeps the device on its existing Thread network and preserves other controllers. See our guide to adding an existing Matter device to Home Assistant without a factory reset.
When a Factory Reset Is Finally Reasonable
A device-level reset becomes reasonable when the device is offline in every controller, cannot rejoin after its documented power or wake procedure, has current firmware, and still fails beside a known-good router on the correct network. It is also appropriate when ownership changes or the remaining fabric records cannot be recovered safely.
Before resetting, photograph the setup code, note the device name and automations, take a Home Assistant backup, and confirm the maker's exact reset steps. Reset only that device. Do not delete the Thread integration, erase the border router, or rebuild unaffected devices around it.
Locks, alarms, shades, and HVAC: keep a physical key, manual control, or safe fallback available. Do not test a smart lock while away from home, defeat an alarm's safety path, or repeatedly cycle HVAC equipment simply to see whether Thread reconnects.
Will Buying Connect ZBT-2 Fix It?
Not when the current Thread network still works. Home Assistant can control Matter devices through supported third-party border routers. If an Apple TV or HomePod carries the device and Apple Home still responds, adding ZBT-2 does not automatically repair Home Assistant's Matter fabric or a blocked IPv6 route.
A Home Assistant-managed border router is useful when you have no suitable border router, want Home Assistant to own and diagnose the Thread network, or have decided to migrate away from an unstable third-party route. That is a planned network choice. Adding it as a second, unrelated Thread network gives existing devices no extra range.
Use our Thread border-router decision guide before buying hardware, and our range guide if the map shows a real coverage gap.
What Stays Local, and What May Still Need the Cloud?
Once a device has been paired, normal Matter commands can travel locally from Home Assistant through the border router to the Thread device. Home Assistant automations can keep working during an internet outage, and the border router cannot read the encrypted Matter command it forwards.
The internet may still be used for vendor firmware, product accounts, remote access, voice assistants, certificate information during setup, and vendor-only features. An internet outage is therefore a useful clue: if local Home Assistant control stops but the Thread border router and home LAN stay powered, investigate the local path rather than assuming Thread itself requires cloud service.
Tara's Recommendation
Build the diagnosis from the outside in: scope the failure, check Matter Server, confirm the correct Thread border router, verify local IPv6 and multicast, then inspect the affected mesh branch or device. Change the radio channel only with evidence. Repair one Matter fabric before erasing the device.
A calm Thread installation has one intentional network, stable powered routes, a recorded owner for its credentials, current firmware, and a backup made before changes. Tara packages those choices into a local-first plan so a restart does not become a weekend rebuild.
Frequently Asked Questions
How long should I wait after restarting Home Assistant?
There is no universal timer. Give powered Thread routers several minutes to form routes and sleepy battery devices time to check in. If nothing improves, stop waiting and use the symptom table: compare another controller, Matter-over-Wi-Fi, and one nearby Thread device.
Will syncing Thread credentials bring an offline device back?
Usually not. Credential syncing helps the phone place a new device onto the intended Thread network. An already paired device needs the existing border router, local IPv6 route, and Matter fabric to work. Sync credentials when pairing fails or the phone chooses the wrong network—not as the first repair for a device that was already working.
Why does the device work in Apple Home but not Home Assistant?
That is good evidence that the device, its power, and the Thread mesh are alive. Check Home Assistant's Matter Server, its fabric record, and the local IPv6 and mDNS path to the Apple border router. Do not reset a device that another controller can still reach.
Can I add a second Thread border router for reliability?
Yes, when it joins the same Thread network and uses the same credentials. Multiple border routers on one mesh can add resilience. A second router that creates a separate network does not help devices on the first mesh.
Does Matter-over-Thread need the internet?
Normal local control does not. Setup, remote access, firmware, accounts, and voice services may. See our guide to Home Assistant and Matter without internet for the exact boundary.