How Can One Matter Device Connect to Two Smart Home Platforms?

Add one Matter device to two smart home platforms: fabrics, Multi-Admin, sharing, automation conflicts and removing a controller.

Your Matter light already turns on and off normally in one app. Now you want to add it to another platform. You take out the box and scan the QR code again, but the device repeatedly fails to add.

Can a light recognize only one platform? Do you have to factory-reset the device to switch apps?

Matter supports adding the same device to multiple control systems. For a device that has already been paired, you should generally open “Share device” or a similar option in the existing platform, then follow the second platform’s setup process, rather than treating it as a brand-new device.[1][2][3]

“Sharing” can be misleading here. It does not necessarily mean giving the second platform access to your account on the first, nor does it mean merging all the settings in the two apps. A better way to understand it is that the same device is authorized to accept another control relationship.

The opening is a hypothetical scenario. This article explains Matter’s multi-platform setup based on official developer and support documentation; it does not include hands-on setup testing with any specific combination of device, phone, or platforms. Button names, supported device types, and features depend on the actual products and their current versions.

1. One Light Can Have Two Control Identities

First, separate three questions: which network the device is connected to, which platform is authorized to control it, and which room that platform places it in.

These things are related, but they are not the same.

Wi-Fi, Ethernet, or Thread primarily determines how a device transmits data. In Matter, a Fabric is a security domain: nodes within it use the appropriate identity credentials to establish protected communication. Google’s official introductory documentation describes part of the commissioning process as configuring Fabric credentials for a new node.[1]

The same device can join more than one Fabric. This is commonly called Multi-Admin. Different Fabrics have their own operational credentials and communication relationships and can operate independently.[1]

You can think of them as two sets of keys that the device recognizes. But that analogy explains only the authorization relationship; it does not mean every setting is isolated.

Both platforms still control the same physical light. When platform A turns it on, platform B does not gain a separate light. Shared device states such as on/off and brightness still need to be read or subscribed to by each platform according to its implementation; there is no guarantee that both apps’ screens will refresh at exactly the same moment.

Google’s documentation specifically distinguishes each Fabric’s identity credentials from the device’s shared data model and network configuration.[1] Adding a second platform therefore does not mean connecting the device to a second, independent Wi-Fi or Thread network.

2. Why Might Scanning the Box’s QR Code Again Not Work?

During initial setup, the device is in a state where it can be added, and the phone follows the prompts to complete setup using a QR code or numeric code.

Once the device is in use, it cannot automatically grant control to someone simply because they open another app nearby. Granting a new platform access requires an appropriate commissioning window and pairing information.

Google’s Multi-Admin developer documentation describes this process explicitly: join one Fabric first, then reopen the commissioning window and add another Fabric.[2]

Home Assistant’s official instructions are closer to everyday use: select Share device for a device already added to Home Assistant, then scan the QR code or enter the sharing code in another platform. The documentation says this sharing path does not require pressing the device’s hardware button again.[3]

So the initial QR code on the packaging and the pairing information supplied by an existing platform’s sharing process should not be treated as interchangeable in every situation. Having a QR code in hand does not mean the device is currently allowing a new platform to join.

Different platforms may also provide system-level options. Apple’s support documentation says that, to add a Matter accessory already paired with another app to Home, you can select “More options” under “Add Accessory” and then select the accessory.[4]

This means the exact steps may not always involve manually copying a string of digits. What matters is following the correct process for adding a Matter device already in use, rather than insisting on one particular way of scanning a code.

3. A Reasonably Reliable Order for Adding the Device

The following sequence is based on official procedures. It is not a button-by-button guide that applies to every brand.

First, confirm that the original platform can still control the device. If it cannot, check the device’s power, network connection, and platform status first. Sharing will not automatically fix a device that is already offline.

Next, confirm that the target platform supports this type of device. “Supports Matter” does not mean it supports every device type, every feature, and every firmware combination. Apple lists the accessory categories supported by Home separately; Home Assistant also notes that generic Matter control may not provide every feature available through a manufacturer-specific integration.[3][4]

Open the sharing or pairing option in the existing platform. Follow the current app’s prompts to generate pairing information. If it has expired, obtain new information through the same option. Do not keep reusing an old screenshot of a sharing code.

In the target platform, choose to add a Matter device and follow the prompts. If the platform offers an option for an “already paired device,” “More options,” or sharing directly to another app, follow the relevant official instructions.

After adding it, test it from both sides. For example, turn the light on in platform A, check its status and turn it off in platform B, then return to platform A to verify the result. For devices where you need dimming, color temperature, or sensor readings, test each feature you actually use.

At a minimum, record the device model, firmware version, names and versions of both platforms, and the specific actions that succeeded or failed. That gives you something to compare against after a future upgrade or controller change.

4. Control From Both Platforms Does Not Mean Their Configurations Will Sync

This is another common misunderstanding after adding a device to multiple platforms.

The light appears in both apps, so you expect the “Living Room” assignment, “Movie Mode” scene, and “turn off the light at 10 p.m.” automation you set up in the original app to come across too.

Do not treat Multi-Admin as a cross-platform configuration migration tool. It allows a device to join multiple Fabrics; it does not promise to copy each platform’s accounts, rooms, automation rules, or interface settings.[1][2]

Some setup processes may carry over the device name. For example, some direct-sharing options listed in Home Assistant’s documentation include its device name.[3] That does not mean rooms and automations will migrate in full. Check what the target platform has actually imported.

Also bear in mind that two platforms may send different commands to the same device.

Suppose platform A has a rule to turn off the light at 10 p.m., while platform B has a rule to turn it on when someone passes by. If the light comes back on after 10 p.m., both rules may be working as intended; it is not necessarily a commissioning error.

In practice, I recommend choosing one platform for your main automations at first, while using the other for viewing status and manual control. If you do need rules running on both, document their triggers, execution times, and exceptions. This is management advice, not a Matter requirement.

5. Troubleshoot Thread Border Routers and Control Permissions Separately

If the device uses Thread, there is another layer to consider.

A Thread border router connects the Thread network to an external IP network, while a Matter controller interacts with the device through Matter. One physical product may perform both roles, but the roles themselves should not be conflated.

Home Assistant’s documentation gives a straightforward example: using another brand’s Thread border router does not mean you must add the device to that brand’s ecosystem. The border router can simply carry communication traffic.[3]

When troubleshooting, ask these questions separately:

  • Can the target controller reach the device over the existing network?
  • Has the device accepted the target platform’s Matter identity and authorization?

Network connectivity does not imply authorization; a correct sharing code cannot substitute for a working network path.

For a closer look at the local network and IPv6, read “Why Does Matter Use IPv6? Can It Work Without IPv6 Enabled at Home?”. When adding a device to multiple platforms fails, distinguishing a network discovery problem from a commissioning authorization problem is more useful for troubleshooting than immediately replacing the router.

6. If You No Longer Want to Use a Platform, Do Not Rush to Reset the Device

Whether you are adding a second platform or leaving one, first establish the scope of the action you are about to take.

Apple’s support documentation lists “remove from iCloud Keychain,” “remove from one connected service,” and “remove from all connected services” as distinct operations. Removing an accessory from a single service takes away the corresponding app’s ability to control it.[4]

Home Assistant also provides an option to manage a device’s Fabrics and remove a specific controller.[3]

So, if you only want to leave one platform, first look for the relevant service or Fabric management option and read its confirmation prompt carefully. Do not treat “remove a platform,” “delete a pairing record saved on this phone,” and “factory-reset the device” as the same action.

If the original platform is no longer available or device information has been lost, you may need to follow the manufacturer’s recovery procedure. Whether a reset is necessary depends on the device’s specific state; you cannot conclude that it is required solely because the second platform cannot add the device.

Once multi-platform setup is complete, what is worth checking is not how many times the device icon appears, but whether both platforms have the right control permissions, whether the features you use work, and whether the two sets of automations conflict.

Checking those points is what turns Multi-Admin from a term on a specification sheet into a genuinely useful everyday capability.

References and Scope of Verification

Sources checked on: 2026-11-07. This article explains the basic mechanism and official setup paths; it does not guarantee that any particular combination of two platforms and a Matter product can be connected successfully. It does not assume a fixed sharing-code validity period, a universal capacity limit, or an untested success-rate figure.

  1. Google Home Developers: The Fabric. Consulted primarily for security domains, operational credentials, and Multi-Admin; independent Fabrics are not presented as meaning that all device states are independent.
  2. Google Home Developers: Multi-admin for Commissioning API on Android. Used to verify the mechanism for joining Fabrics in sequence and reopening the commissioning window; the API development process is not treated as a user-interface guide for every app.
  3. Home Assistant: Matter integration documentation. Consulted primarily for “Multi fabric,” “Sharing a device across platforms,” “Removing a device from a Matter controller,” and the explanations of Thread border routers and feature support. Specific options described in the article represent only that platform’s documented processes.
  4. Apple Support: Pair and manage your Matter accessories. The page lists a publication date of 2026-05-07. Used to verify the option for adding an already paired accessory, supported categories, and the distinctions among removal operations.

Cover reused from this site’s Matter series: an AI-generated concept illustration of home networking, not a diagram of permissions or a tested topology.

Discussion

Share a question or your experience. Comments appear after moderation. Your email is never displayed publicly. Comment privacy

Loading comments…