Matter Works in Home Assistant but Says No Response in Apple or Google Home

The Short Answer: Repair the Platform That Failed, Not the Device

A Matter device can work perfectly in Home Assistant while Apple Home says “No Response” or Google Home shows it offline because each platform has its own secure controller relationship with the device. Matter calls each relationship a fabric. Home Assistant, Apple Home, Google Home, Alexa, and SmartThings do not borrow one shared controller record.

Working Home Assistant control is valuable evidence: the device has power, Home Assistant's fabric is valid, and at least one local route works. It does not prove that Apple or Google's share completed, that its Matter hub is online, that its app supports the device type, or that its hub can reach the device over local IPv6.

First Confirm Which Connection You Actually Built

Several Home Assistant-to-platform paths can put the same name in two apps. They are not interchangeable, and the repair depends on which one you used.

For direct Matter sharing, the device must already appear under Settings > Devices & services > Matter > Devices. Open it, find Share device, open the nearby three-dot menu, and select Manage fabrics. Home Assistant's official instructions say the destination should appear there after a successful share; Google, for example, is shown as Google LLC.

If the destination is not listed, skip restarts and go to the next section. If it is listed, continue to the platform and network checks.

If the Destination Fabric Is Missing, Share Again With a Fresh Code

A Matter device that is already in use normally needs a new temporary invitation from its current controller. The printed QR code was made for first setup. Amazon's current Matter guidance explains that the standard's required secondary-commissioning method opens a new pairing window and creates a fresh random code.

1. In Home Assistant, open the device under the Matter integration and select Share device.
2. Generate the new QR code or numeric sharing code. Keep this screen open; the invitation expires.
3. Open the destination app's add-accessory flow. Tell it the device is already in use when that choice appears.
4. Enter or scan the temporary code from Home Assistant, not a screenshot of an old code.
5. Return to Home Assistant's Manage fabrics view and confirm the destination now appears before moving rooms or rebuilding routines.

Apple Home: Choose the Already-Paired Accessory

Apple's May 2026 instructions say to open Home > Add > Add Accessory, then choose More options and select the Matter accessory that was previously paired in another app. A recent Home Assistant Community thread describes the easy-to-miss failure: repeatedly scanning the displayed Home Assistant QR code timed out, while choosing the discovered accessory under More options and then supplying the code completed the share.

Apple also lists the paired device under Settings > General > Matter Accessories. That view can show its connected services and helps separate “the iPhone remembers this device” from “Apple Home currently has a working fabric.”

Google Home: A Google Matter Hub Is Still Required

Home Assistant's Matter Server and a Home Assistant Thread border router do not replace Google's controller. Google says each Matter app needs its own Matter hub. Google Home also requires IPv6, the local addressing system Matter uses inside the home. Before buying anything, check whether your household already has a compatible Google hub. For Matter-over-Thread, that hub must include a Thread border router, such as a Google Home Speaker (2026), Nest Hub (2nd generation), Nest Hub Max, Nest Wifi Pro, or Google TV Streamer (4K).

A Google Home Speaker, Nest Audio, Nest Mini, first-generation Nest Hub, and some compatible TVs can act as Google Matter hubs for Wi-Fi devices, but Google's current list does not give all of them a Thread radio. If a Thread lock or sensor says a hub is required, adding another app or syncing Home Assistant credentials does not create Google's missing Matter administrator.

If the Fabric Exists but the App Says Offline

Now treat this as a destination-platform problem. Do the smallest reversible checks first:

1. Test the same control in Home Assistant. If it still works, leave the device powered and paired.
2. Update and reopen the destination app. Confirm the phone is signed into the intended home and account.
3. Check the destination Matter hub. Make sure it is online, in the correct home, and current. Restart that hub once, then wait for it to return before testing.
4. Put the phone and hubs on the trusted home network. Pause a VPN while diagnosing. Avoid guest Wi-Fi and client isolation.
5. Check the device maker's app for firmware. Do not switch the device to a different vendor connection merely to update it unless the maker documents that path.
6. Confirm device-type support. Matter certification does not force every platform release to expose every device category or optional feature on the same day.

Apple's current “No Response” guidance follows the same order: update software, reopen Home, use the same Wi-Fi, restart affected accessories and home hubs, allow a Thread network to settle, and check VPN or security software. Apple puts removal near the end—not at the start.

What Each Platform Needs in 2026

This is the practical boundary between official support, local Matter control, cloud services, and a Thread route. Model and feature support changes, so use the linked platform lists before buying a hub.

Why Home Assistant Working Does Not Clear the Home Network

Matter uses local IPv6—the address system that lets Matter devices and hubs find one another inside the home. Home Assistant may have a good route to the device while an Apple, Google, Alexa, or SmartThings controller sits behind a different Wi-Fi access point, guest network, separate network segment, or device-discovery filter. A working internet connection does not prove that this local path works between every hub.

• Keep the Matter controllers and border routers on the same trusted LAN while testing.
• Disable client isolation on the trusted smart-home network; do not place one hub on guest Wi-Fi.
• Temporarily pause VPN or third-party phone security software only long enough to test the local pairing path.
• If your router separates devices into network segments, often called VLANs, verify IPv6 routing and local device discovery across the intended boundary. Do not open ports to the public internet.
• For Thread, confirm the device still has a powered border router for the Thread network it originally joined. A second unrelated Thread network does not help.

Google warns that setup can appear to work without IPv6 before control fails later. Apple likewise tells households with several unresponsive brands to check the same Wi-Fi, router, home hubs, VPN, and security software. Those checks are more useful than resetting a device that Home Assistant can demonstrably reach.

An Online Device Can Still Have Missing Features

“It paired” and “it exposes every feature” are separate questions. Apple, Google, Alexa, SmartThings, and Home Assistant each map the Matter device types and optional features they support. A lock can provide basic lock control in one app while a platform-specific key, UWB unlock, access-code screen, history view, or firmware tool remains in another.

HomeKit Bridge also cannot turn a normal Home Assistant lock entity into a natively certified Apple lock with every secure Apple feature. Direct Matter sharing creates a real second fabric, but even that does not promise Home Key or a vendor-only feature. Check the lock maker's exact model documentation before removing the connection that currently provides a household-critical feature.

How to Replace Only the Failed Fabric

If the destination is listed in Manage fabrics, its hub and local network are healthy, and it still cannot control a supported device, remove and rebuild only that destination relationship.

1. Record the destination app's room, routines, scenes, names, and any family permissions tied to the device.
2. Take a Home Assistant backup and confirm Home Assistant still controls the device.
3. In the Home Assistant Matter device, open Manage fabrics and remove only the failed controller.
4. For Apple, follow Home Assistant's Apple cleanup prompt as well. In Settings > General > Matter Accessories, remove only the stale Apple Home connected service or Keychain record the prompt identifies. Never choose Remove From All Services while Home Assistant should keep working.
5. Restart the destination Matter hub, wait for it to return, then generate a fresh sharing code from Home Assistant.
6. Add the already-paired device in the destination app and confirm the destination reappears under Manage fabrics.
7. Test device control from both platforms before rebuilding the saved routines.

Do not delete the Home Assistant device, remove Home Assistant's own fabric, or erase the Thread network. Those actions destroy the known-good half of the setup without repairing the other controller.

When a Factory Reset Is Finally Reasonable

A factory reset is reasonable only after the device fails in every controller, the documented power or wake procedure does not restore it, current firmware does not help, and a clean single-fabric re-add has failed. It can also be necessary for an ownership change or a maker-documented recovery procedure.

Before resetting, photograph the original setup label, save automations and access details, take a Home Assistant backup, and check the maker's exact reset steps. Reset only the affected device. If Home Assistant still operates it, you have not reached this point.

What Stays Local and What Still Uses the Cloud?

After commissioning, each Matter controller can send normal commands locally over Wi-Fi, Ethernet, or Thread. Home Assistant does not relay its working Matter command through Apple, Google, Amazon, or Samsung, and those platforms do not need Home Assistant to remain online for their own valid fabric.

Cloud services can still handle remote access, account and home membership, voice recognition, app synchronization, firmware delivery, vendor-only features, and some setup checks. This is why one platform can say offline while another still works locally—and why “Matter is local” does not mean every surrounding app feature is account-free.

Tara's Recommendation

Use Manage fabrics as the fork in the road. If the destination is absent, repeat sharing with a fresh temporary code and the correct already-paired-device flow. If it is present, repair the destination hub, local IPv6 path, and device support. Replace only that fabric after saving its routines.

Keep one known-good controller alive throughout the repair. A working platform is not a nuisance to erase; it is your proof that the device can be recovered without a factory reset.

Frequently Asked Questions

Why does my Matter device work in Home Assistant but say No Response in Apple Home?

The two platforms have separate Matter fabrics. Check whether Apple appears under Home Assistant's Manage fabrics. If it does, update and restart Apple Home and its home hub, check the same trusted Wi-Fi and VPN settings, and verify Apple supports the device type. Do not reset the device while Home Assistant still works.

Does Apple Home need a home hub for Matter?

Not in every local case. Apple says iOS 18 or later can add and control Matter accessories without a home hub, and an iPhone 15 Pro or later can locally manage supported Thread accessories. Apple still recommends a home hub for the best experience, remote access, automations, and stronger Thread coverage.

Why does Google Home ask for a hub when Home Assistant has a Thread border router?

A Thread border router carries packets; it is not automatically Google's Matter controller. Google requires its own compatible Matter hub and IPv6. For a Thread device, choose a Google Matter hub that also contains a Thread border router.

Can I reuse the QR code printed on the device?

Use the fresh temporary code from Home Assistant's Share device flow. The original code may work only when the device and both controllers support the optional original-code method and the device is deliberately put back into pairing mode.

Will HomeKit Bridge give a Matter lock Apple Home Key?

Do not assume it will. HomeKit Bridge exposes Home Assistant entities through a virtual bridge; it is not the same as directly adding a compatible physical lock to Apple Home. Home Key, UWB unlock, and other secure platform features depend on the exact lock, certification, firmware, and direct connection path.