Matter Device Shows No Response’ in Your Second Smart Home

You added a smart plug or bulb to Alexa, it works fine, and then you shared it to Apple Home or Google Home so the rest of the household could use it. Now the second app shows the tile with “No Response,” “Offline,” or a spinning icon. This Matter device no response problem has a short list of causes. Most of them have nothing to do with the device itself.

This guide walks through the diagnosis in order: symptom, likely cause, fix. Then what to do if it still won’t answer.

📌 Related reading: How to Set Up a Matter-Compatible Smart Home Device · Matter Device Won’t Pair? Check This Before You Blame the Device (2026)

Jump to a Section

• Why does a shared Matter device go silent in only one app?
• Does the second platform have its own hub?
• Could IPv6 or a VPN be blocking the second controller?
• Symptom-to-cause lookup table
• How do you re-share without a factory reset?
• When re-sharing doesn’t bring it back
• FAQ
• Sources

Why Does a Shared Matter Device Go Silent in Only One App?

A Matter device that responds in Alexa but shows “No Response” in Apple Home or Google Home (or the reverse) usually still works fine. The second platform simply can’t reach it. Matter’s multi-admin feature lets one device belong to several ecosystems at once, but each ecosystem talks to the device through its own controller on your home network.

So the device isn’t “shared” the way a file is shared. It holds a separate trust relationship with each platform. If the second platform’s path to the device is missing or broken, that app goes dark while the first keeps working.

That’s why a factory reset is usually the wrong first move. It wipes the working connection too.

Does the Second Platform Have Its Own Hub?

Every Matter platform you control a device from needs its own Matter-capable hub in the home, and a missing hub is the most common reason the second app shows “No Response.” Google’s Matter help page says it directly: you need one Matter-certified smart home hub for each Matter-certified app you want to control the device from.

In practice that means:

• Google Home needs a Google hub device on your network. Google’s own list includes the Google Home Speaker, Nest Audio, Nest Mini, Nest Hub models, Nest Wifi Pro, and the Google TV Streamer.
• Apple Home works best with a home hub. That means a HomePod, HomePod mini, or Apple TV. Apple’s support page notes that iOS 18 can manage Matter accessories without one. It still recommends setting a hub up, and remote control needs it.
• Alexa needs a compatible Echo device that acts as a Matter controller. Your phone alone isn’t the controller.

A common trap: a household with one Echo shares a plug to Apple Home from an iPhone. The pairing succeeds because the phone did the setup. Later, nothing in the home is acting as Apple’s controller, so the tile turns into “No Response.” Pairing working once proves nothing about day-to-day control.

If the device runs on Thread rather than Wi-Fi, the hub question gets one more layer. A Thread device needs a Thread border router in the home. Our Thread border router guide covers which hubs qualify.

Could IPv6 or a VPN Be Blocking the Second Controller?

Yes. Matter runs over IPv6, and Google’s “Prepare your smart home for Matter” page warns that control and other functions eventually fail when the home network lacks IPv6 support. A router with IPv6 turned off can let pairing finish and then lose control hours or days later. That delayed failure is exactly what makes this one hard to spot.

Look in your router’s admin page for an IPv6 or “LAN IPv6” setting and make sure it’s on. Some ISP-supplied routers may have it disabled. Mesh systems sometimes bury it under an advanced tab.

Apple’s “No Response” troubleshooting page also lists VPNs and third-party security software as a cause. A VPN on the phone matters less once a hub is in place. A VPN or firewall running on the router itself can still break local traffic between the hub and the device.

Two more network checks from the vendors:

• TP-Link’s multi-controller guide says the Matter device, your phone, and the Matter hub must be on the same Wi-Fi network.
• Wi-Fi Matter devices generally need the 2.4 GHz band. Guest networks and isolated IoT VLANs can keep the second hub from seeing the device even when the first one can.

Symptom-to-Cause Lookup Table

When I lined up the support pages from Amazon, Google, Apple, and TP-Link side by side, the causes sorted cleanly by symptom. Match yours below.

How Do You Re-Share the Device Without a Factory Reset?

You can re-share a working Matter device by removing it from the second app only and generating a new pairing code from the app where it still works. The first platform’s connection stays intact the whole time.

1. Remove the dead tile from the second app. Delete the device in Apple Home or Google Home (whichever shows “No Response”). Leave the first app alone.
2. Fix the hub and network gaps first. Confirm a hub for the second platform is online and IPv6 is on. Re-sharing into the same broken setup gives you the same result.
3. Generate a new code in the first app. In Alexa, Amazon’s help page says to open Devices, pick the Matter device, choose Other Assistants and Apps, then Add another. That produces an 11-digit pairing code. Google Home and Apple Home have their own share option that creates a temporary code or QR code.
4. Use the code quickly. Amazon says its code is only valid for 15 minutes. TP-Link’s guide lists shorter windows elsewhere: 3 minutes for a Google Home pairing code and 5 minutes for Apple Home. Have the second app open before you generate it.
5. Don’t stack codes. Create one code, use it, then make the next. Don’t generate codes in several apps back to back.
6. Enter the code in the second app’s add-device flow. Choose the option for a device that’s already set up, or enter the code manually instead of scanning the box.

One detail trips people up constantly. Amazon notes that the QR or pairing code printed on the device or its box is only for first setup or after a factory reset. TP-Link says the same thing. If you scan the sticker for the second platform, it will fail. That has nothing to do with the device being faulty.

When Re-Sharing Doesn’t Bring It Back

If the tile is still dead after a clean re-share, work down this list in order. Stop as soon as it comes back.

1. Check the device in the first app. If it’s now unresponsive there too, the problem moved from “second platform” to “device or network.”
2. Update firmware. Apple’s page suggests checking the manufacturer’s app for firmware updates.
3. Restart in the right order. Apple’s full restart sequence is modem and router first. Then bridges and hubs. Then the accessories. Your phone goes last.
4. Give Thread time. For Thread accessories, Apple says to disconnect them from power for 5 minutes. Reconnect, then wait 10 minutes for the Thread network to stabilize before judging the result.
5. Check for overlapping automations. Google’s Matter page notes that only one platform can actively control the device at a given moment. Two platforms firing schedules at the same time can look like dropouts.
6. Factory reset as the last step. Reset following the maker’s instructions, add it to your main platform, then share outward again. Expect to rebuild automations on that platform, since they don’t carry over.

If an Echo shows the device offline only when a routine or alarm runs, that’s a different bug. Our Alexa offline-alarm fix covers it.

A last practical tip before you buy anything new: a lot of “which ecosystem should I pick” regret is really this problem. The device usually isn’t the wrong choice. The second platform just never got a hub. Sort out the hub and IPv6, and most mixed iPhone-and-Android households can run Alexa, Google Home, and Apple Home side by side on the same Matter gear.

FAQ

Can I use the Matter QR code on the box to add a device to a second app?

No. Amazon’s help page says the code on the device or box is only for first setup or after a factory reset. For a second platform, generate a new pairing code from the app that already controls the device.

Do I need a separate hub for each smart home platform?

Yes, if you want reliable control from that platform. Google states you need one Matter-certified hub per Matter app you control the device from. An Echo covers Alexa only, not Apple Home or Google Home.

Will removing a Matter device from one app break it in the others?

Deleting it from one app normally removes only that platform’s connection, so the others keep working. A factory reset is different: it wipes every platform at once, and you have to share it out again.

Sources

• Google Home Help — Set up, manage, and control Matter-enabled devices with Google Home
• Google Home Help — Prepare your smart home for Matter
• Amazon — Set Up an Alexa-connected Matter Device to Another Voice Assistant
• Apple Support — If your HomeKit or Matter accessory isn’t responding in the Home app
• Apple Support — Pair and manage your Matter accessories
• TP-Link — How to add your Matter-Certified device into multiple controllers

Checked against the official help pages above as of October 5, 2026 — 6 sources. Menu names and code time limits change with app updates, so follow what your app shows if it differs.