A Matter code can fail because the accessory is already commissioned, not in pairing mode, too far from Bluetooth/thread infrastructure, or being added to the wrong home/admin ecosystem. Check every controller app and hub in the home for the device.
Differential
Likely causes of “Matter setup code is not working”, and how to tell them apart
- 1
The device is already commissioned to another home or controller
What separates it The code is rejected or setup stalls, and the device appears in another app or hub in the household.
How to confirm Check every controller app and hub in the home for the device.
- 2
The device is not in pairing mode
What separates it The code is right but the device has no pairing light or the pairing window has timed out.
How to confirm Power-cycle into the documented pairing mode and try again promptly.
- 3
The phone is too far from the device or the hub
What separates it Setup fails at the Bluetooth or Thread step and works when the phone is next to the device.
How to confirm Try again standing beside the device and near the hub or border router.
- 4
The code belongs to a different device or the label was misread
What separates it A code from a different accessory or an old box is being used.
How to confirm Check the code on the device or its own packaging carefully.
Before you touch a setting
Record this first — changing settings destroys the evidence
- The exact code and where it was printed, and whether the device shows in another app.
- Whether the device shows a pairing light and how long it stays on.
- The controllers and hubs in the home and whether a Thread border router is present.
Try in this order
0 of 4 completedCapture the exact symptom
ReversibleConfirm the exact code/QR belongs to the device and check whether it already appears in any controller app.
Run the smallest isolation test
ReversiblePower-cycle into documented pairing mode near the phone and active home hub/border router.
Correct only the proven cause
ReversibleRemove it from the previous fabric or use ecosystem sharing instead of repeated factory resets.
Verify before changing anything else
ReversibleControl the device from the intended ecosystem and verify it remains reachable after reboot.
Stop boundary
When this stops being a self-service repair
- !Remove the device from its previous controller or use multi-admin sharing instead of repeated factory resets.
Evidence ledger
Sources behind this answer
Exact questions
Common questions
Can a Matter device join two ecosystems at once?+
Yes, through multi-admin sharing. Start from the first controller's share option rather than resetting the device.
Why is the Matter setup code rejected?+
The code may be for another device, expired, mistyped or already used. Check the code on the device or packaging and that it matches the device you are adding.
Does the device need to be in pairing mode?+
Yes. Many Matter devices only accept setup for a short time after being reset or powered on. Put the device in pairing mode first.
Could the controller be the issue?+
Your phone's controller app and hub must support Matter. Update the app and the hub.
What if the code was already used on another system?+
The device may need a reset before it can start again, or you can use the multi-admin sharing option from the first controller.