setup · reviewed answer

Add one Matter device to a second smart-home ecosystem

Use the first ecosystem's multi-admin or sharing flow to generate a fresh setup code for the second ecosystem. The code printed on the device may not be the correct code after commissioning.

Direct answer

Use the first ecosystem's multi-admin or sharing flow to generate a fresh setup code for the second ecosystem. The code printed on the device may not be the correct code after commissioning.

What this covers

  • A Matter device and two ecosystems that both support that device type and Matter version
  • The exact condition described in the direct answer
  • Customer-accessible observations and controls

What it does not cover

  • ×A different model, region or software interface that contradicts the cited source
  • ×A displayed code with a separate manufacturer meaning
  • ×Live electrical, gas, sealed-system or battery-cell repair
Try in this order0 of 4 completed
  1. Establish the exact starting state

    Reversible

    Confirm a working primary fabric, compatible hub/controller, same local network and administrator access in both ecosystems.

  2. Separate the fault or decision boundary

    Reversible

    Check device-type support and Thread-border-router requirements in the destination ecosystem before removing anything.

  3. Apply the narrowest correction

    Reversible

    Open the primary ecosystem's sharing or multi-admin flow and enter the newly generated code in the destination app.

  4. Verify before escalating

    Reversible

    Control the device from both ecosystems and test automations without deleting it from the first.

Evidence ledger

Sources behind this answer

Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.

Exact questions

Common follow-ups

What is the short answer to “Add one Matter device to a second smart-home ecosystem”?+

Use the first ecosystem's multi-admin or sharing flow to generate a fresh setup code for the second ecosystem. The code printed on the device may not be the correct code after commissioning.

What should I check before changing anything?+

Confirm a working primary fabric, compatible hub/controller, same local network and administrator access in both ecosystems.

How do I know the action worked?+

Control the device from both ecosystems and test automations without deleting it from the first.

When should I stop?+

Removing or factory-resetting the accessory can break the working fabric and require physical recommissioning.

Change recordAug. 17, 2026 — Added as a distinct setup intent with its own scope, diagnostic boundary, verification and first-party source.
Report a correction
Wrong device or version?

Match the path before repeating the steps.

Match another device