Matter device pairs, then goes offline or disappears: how to fix it

You scan the QR code, the app says the new plug or bulb is ready, and it works. An hour or a day later it shows No Response, Offline or Unavailable, or it disappears from the app altogether. Or it works in Apple Home but refuses to join Google Home or Alexa.

This almost never means the device is broken. Matter adds a layer that most home networks were never set up for, and when one link in the chain is missing, things often pair fine and then fail later. Google’s own help gives one example: without IPv6 on the home network, setup can appear to work, then control stops.

This guide explains the moving parts in plain English, gives you a quick diagnosis table, and then goes through the fixes, safest first. Factory reset is at the end, on purpose.

The parts, in plain English

• Matter is a shared language for smart home devices. A Matter plug can be controlled by Apple Home, Google Home, Alexa, Home Assistant and others, and the control happens locally on your home network. The Connectivity Standards Alliance (CSA), which runs Matter, says it works over Wi-Fi, Thread and Ethernet, and uses Bluetooth only for the initial setup.
• Thread is a low-power mesh radio network, a bit like Zigbee, used by battery sensors, locks, bulbs and plugs. Thread only moves the data. Matter (or HomeKit) is what actually controls the device. In a mesh, devices pass messages along for each other instead of all talking to one central box.
• A Thread border router is the bridge between the Thread mesh and your normal Wi-Fi/Ethernet network. Thread devices can talk to each other without one, but your hubs and apps usually reach them through it (newer Thread-capable iPhones are an exception, see Step 2). You can have several on the same Thread network for better coverage.
• A fabric is the CSA’s word for a private, secure group of Matter devices and controllers. Apple Home makes one, Google Home makes another, Alexa another. Each is run by its own administrator.
• Multi-admin is the Matter feature that lets one device join several fabrics at once, so the same plug can appear in Apple Home and Alexa. You add the second ecosystem with a fresh pairing code from the first one, not with the sticker on the device.

Note: “Matter over Thread” and “Matter over Wi-Fi” devices fail for different reasons. Check the box or the maker’s page to see which yours is. Thread devices often carry the Thread logo.

Quick diagnosis

Symptom	Likely cause	Fix
“Thread Border Router Required” / “Needs Thread Network” / “Your device requires a Thread border router”	No Thread border router, or it’s off or on a different network	Add or restart a border router (Step 2)
Thread device works for a while, then drops; other Thread devices nearby are fine	Weak mesh, too far from a border router or other Thread devices on its network	Move it closer, or add a border router or powered Thread device that joins the same Thread network (Step 2)
Pairs fine, then goes No Response later	One possible cause: local IPv6 not working on the LAN (blocked, or not passing through the border routers)	Check local IPv6 and multicast (Steps 3 and 4)
Wi-Fi Matter device won’t pair at all	Device only supports 2.4 GHz and that band is off or out of range; phone on a different network (such as guest); band bridging not working	Make sure 2.4 GHz is on and the phone is on the same main network; as a workaround, try setup with the phone on 2.4 GHz only (Step 3)
Devices randomly go “unavailable” or can’t be found	mDNS/multicast blocked: guest network, AP/client isolation, VLANs, “multicast optimisation” on mesh Wi-Fi	Put everything on one flat main network (Step 4)
Thread device works in one app, can’t be added to another ecosystem’s Thread network	Separate Thread networks per vendor that don’t share credentials	Share the device with multi-admin instead of re-pairing (Steps 5 and 6)
Adding to a second app fails with “invalid code”	Used the printed QR/sticker, or the share code expired	Generate a new pairing code from the first app (Step 6)
Device disappeared from one app only	It was removed from that fabric (by you, a reset, or another app)	Share it again from the app that still has it (Step 6)
Nothing above helps, device unreachable everywhere	Device stuck or corrupt	Remove it, then factory reset as the maker describes (Step 7)

Step 1: The basics first (nothing to lose)

1. Power-cycle the device: unplug it or pull the battery for 10 seconds.
2. Restart your hubs: the HomePod, Apple TV, Nest Hub, Echo or other border router or hub. Apple and Google both list restarting the hub as a first fix.
3. Update everything: the phone, the Home/Google Home/Alexa app, the hub, and the device’s firmware through the maker’s app. Apple notes that some battery-powered Thread accessories need a firmware update to work with newer iOS versions.
4. Check you’re the right person: Apple suggests using a device signed in to the Apple Account that set up the home.

If it comes back and stays back, you’re done. If it drops again, carry on.

Step 2: Thread devices need a working border router

Thread devices can talk to each other on their own mesh, but to reach your hubs and apps over Wi-Fi or Ethernet they need a Thread border router. Some Thread-capable iPhones can pair and control compatible accessories directly (below), but an always-on border router is still what keeps them working when your phone isn’t around. Common ones:

• Apple: HomePod mini, HomePod (2nd generation), Apple TV 4K (2nd generation), and Apple TV 4K (3rd generation) Wi-Fi + Ethernet model. The Wi-Fi-only Apple TV 4K (3rd generation) is not on Apple’s Thread list. Apple also says iPhone 15 Pro and later on iOS 18 can pair and control Thread accessories without a hub, but a home hub is still recommended so things work when your phone isn’t home.
• Google: Nest Hub (2nd gen), Nest Hub Max, Nest Wifi Pro (Wi-Fi 6E) and Google TV Streamer (4K). Google’s current list also includes the Google Home Speaker (2026). Note the Nest Hub (1st gen) is a Matter hub over Wi-Fi only, without Thread.
• Amazon: Amazon says Thread-enabled Echo and eero devices have built-in border routers, including Echo (4th Gen) and Echo Hub. Amazon’s lists change as new models arrive, so check your exact model on Amazon’s Thread device list.
• Home Assistant: with a Thread radio running the OpenThread Border Router.

What to check:

• Is the border router on and on the same network as your phone and the device? Google’s troubleshooting specifically says other border routers must be powered on and on the same Wi-Fi.
• Apple TV on Ethernet: Apple’s own fix for Thread errors includes switching an Ethernet-connected Apple TV to Wi-Fi on the same network as your iPhone. Try it if the Apple TV is your only border router.
• Distance: Home Assistant notes you need a border router near the device when you first add it, with your phone close to both. After that, the device needs a path through the mesh. A lone battery sensor at the far end of the house is the classic dropout. A Thread network can use several border routers, and the Thread Group notes that mains-powered devices extend the mesh of the network they’re on. So add a border router or a plug-in Thread device nearer the sensor, but only if it joins the sensor’s existing Thread network. One that starts its own separate Thread network (Step 5) won’t extend the sensor’s mesh.
• Interference: Thread uses the same 2.4 GHz band as Wi-Fi. Home Assistant notes Thread channels 11 to 24 can overlap Wi-Fi, and channel 26 is least likely to clash. Only change channels if you run your own border router and understand it. Some Thread devices don’t move to the new channel by themselves and have to be added to the network again. In Home Assistant the switch happens about five minutes after you ask for it; don’t restart the border router or change anything else while it’s pending.

Gotcha: Google suggests a quick Thread test: in the maker’s app, turn Bluetooth off on your phone and trigger the device. If it still responds, Thread is doing the work, not a direct Bluetooth link.

Step 3: Local IPv6 and the right Wi-Fi band

Matter depends on IPv6 inside your home. This is different from IPv6 on your internet connection (the ISP or WAN setting). Home Assistant says you need neither an IPv6 internet connection nor a DHCPv6 server, just local IPv6 and multicast travelling freely on the LAN. Thread itself is IPv6-only.

Google says IPv6 must be enabled on your home wireless network, and that without it setup may appear to succeed but control eventually fails. So broken local IPv6 is one possible cause of “pairs, then goes offline”. It isn’t the only one, so check Step 4 too.

• What has to work: IPv6 between your phone, your hubs and controllers, and your Thread border routers on the local network, with IPv6 multicast not filtered (Step 4). Switching on IPv6 for your internet connection doesn’t prove any of that, and turning it off isn’t by itself the cause. Don’t change WAN or ISP settings just for Matter.
• Where to look: if your router has a setting that blocks or filters IPv6 on the LAN, or a firewall rule dropping IPv6 between local devices, that’s worth checking. The names vary by router, so check its manual.
• Wi-Fi Matter devices: Home Assistant notes they often use 2.4 GHz only, so that band must be on and reach the device. Your phone doesn’t normally need to be on 2.4 GHz itself: Google notes most routers let 2.4 GHz and 5 GHz devices talk to each other, as long as they’re on the same network (not a guest network). If setup keeps failing, Google’s workaround is to connect your devices to the 2.4 GHz band only while you set up, then switch back.
• Bluetooth on: setup uses Bluetooth Low Energy. Google says the phone needs BLE 4.2 or newer.

Step 4: Don’t let your network hide devices from each other

Matter devices find each other with mDNS (multicast DNS: “who’s there?” messages shouted to the whole local network). Anything that blocks multicast or splits the network breaks discovery, and devices go “unavailable” seemingly at random. Home Assistant says Matter is designed for ordinary home networks and recommends keeping things as simple and flat as possible.

Check for these, in order:

1. Guest network: guest Wi-Fi is deliberately cut off from the main network. If the device, the hub or your phone is on it, they can’t see each other. Move them all to the main network.
2. AP isolation / client isolation: a router or access point setting that stops wireless devices talking to each other. It’s often on by default for guest networks and sometimes on IoT networks. Turn it off for the network your smart home uses.
3. VLANs / separate IoT networks: Home Assistant says Matter may not get along with VLANs and multicast filtering, and asks that Wi-Fi devices and Thread border routers be on the same VLAN as the controller. If you put smart devices on their own VLAN, put your HomePod, Nest Hub or Echo there too, or use one network for the lot.
4. Mesh Wi-Fi and “multicast optimisation”: Home Assistant warns that router or access point settings that “optimise” multicast, and badly behaving IGMP snooping, can harm Matter discovery. Its Thread docs also list mesh access points blocking multicast as a pairing failure cause. If your mesh system has options like these, try turning them off.
5. VPN or security software on the phone: Apple lists this as a cause of Thread errors. Pause it while adding devices.

Risk: changing VLANs, firewall rules or isolation settings can expose devices you meant to keep separated, or cut off other devices. Note down each setting before you change it, and change one thing at a time.

Step 5: Separate Thread networks don’t merge on their own

Each brand usually creates its own Thread network the first time you use its products. Home Assistant spells it out: these are separate networks with different credentials, and devices can’t roam between them. So a HomePod’s Thread network and a Nest Hub’s Thread network sit side by side, each with its own devices.

This is why “it’s on Thread, and I have two border routers” doesn’t always help: the second one may be running a different Thread network.

What to do:

• Simplest: keep each Thread device on the ecosystem that first added it, and use multi-admin (Step 6) to control it from the others. Matter traffic crosses over your normal IP network, so that works fine.
• Sharing credentials: some systems can join an existing Thread network instead of starting a new one. Google says the Google TV Streamer can create a new Thread network or join an existing one, and stores Thread credentials in your Google Account. Amazon describes customers sharing Thread credentials with Alexa. Home Assistant can import credentials through its companion app, and its border router can join an existing Apple or Google network. How much of this you control, and from where, varies by ecosystem and software version.

Step 6: Add a device to a second ecosystem (multi-admin)

Before you start: the QR code or number printed on the device is for first-time setup or after a factory reset only. To add an already-paired device to another app, generate a new, temporary pairing code from the app that already has it. The code expires within minutes, and typically works once. If it fails, make a fresh one.

From Google Home: touch and hold the device’s tile › Settings (or More) › Linked Matter apps & services › Link apps & services. Pick the other app (it must be installed), or choose Use pairing code or Share with QR code, then add the device in the other app with that code.

From Apple Home: open the accessory’s settings in the Home app. Device makers’ instructions (for example TP-Link’s Tapo FAQ) describe an option called Turn On Pairing Mode, then Copy Code. Apple’s own support pages don’t document this button, so the label may differ on your iOS version. Apple also stores paired Matter accessories in Settings › General › Matter Accessories via iCloud Keychain, and other Matter apps can offer to add one from there.

Into Apple Home from another app: in Home, tap Add (+) › Add Accessory › More options, then pick the accessory. Apple says to generate the pairing code in the other app.

From Alexa: in the Alexa app, open the device’s settings › Other Assistants and Apps › Add Another. Alexa shows a setup code (usually 11 digits) to enter in the other app. Amazon’s menus change often; if yours look different, follow Amazon’s help page “Set Up an Alexa-connected Matter Device to Another Voice Assistant”.

If a device vanished from just one app, don’t reset it. Share it again from the app that still controls it. And if you remove a device from Apple Home that you also use elsewhere, Home Assistant points out you should also remove the Apple Keychain entry. Apple’s Matter Accessories screen lets you remove it from one connected service, from all of them, or from Keychain.

Step 7: Factory reset, the last resort

Stop if: the device still works in any ecosystem. Share it from there instead (Step 6). A factory reset wipes the device’s own pairing data, so no app can control it until you add it again. The apps’ entries may stay behind as unreachable devices, and automations may need repairing or recreating afterwards. Whether they survive depends on the platform.

When nothing else works:

1. Remove it from each app. This is a separate step from the reset: resetting the device doesn’t delete it from the apps. Google Home › device settings › Remove device (Google says this also resets the device’s settings and its automations or routines in Google Home); Apple Home’s accessory settings or Settings › General › Matter Accessories; and Alexa’s device settings. This avoids unreachable ghost entries left behind. Note which automations used the device first.
2. Factory reset the device. There is no standard Matter reset. The method varies by maker and even by model, so use the maker’s instructions. Google’s help says to contact the manufacturer if setup still fails, and recommends a factory reset before moving a device to a different home.
3. Add it again with the printed QR code, close to a border router (for Thread), or with your phone on the same main network as the device’s 2.4 GHz Wi-Fi (for Wi-Fi).
4. Then share it to your other ecosystems from that first app (Step 6), and repair or recreate any automations that broke.

Gotcha: keep the device’s setup code. Take a photo of the QR sticker or the card in the box when you first unpack it. Without it you may not be able to set the device up again after a reset.

Avoid next time

• Keep local IPv6 working and smart home gear on one flat main network, with no guest network or client isolation.
• Have at least one always-on Thread border router, ideally two on the same Thread network, spread around the house.
• Pick one “home” ecosystem to add each device first, and use multi-admin for the rest.
• Save every device’s setup code before the box goes in the recycling.