Matter

Matter commissioning code is rejected

The controller says the pairing code is wrong, expired or already in use.

Applies to
  • Matter devices
  • Matter controllers and hubs
  • Thread devices during commissioning
Last verified2026-10-14
Quick answerTroubleshooting · last verified 2026-10-14

The controller says the pairing code is wrong, expired or already in use. Most common cause to check first: Code already used to commission the device elsewhere

Applies toMatter devices, Matter controllers and hubs, Thread devices during commissioning
CategoryMatter
Escalate whenIf the code was already used, the device is still claimed by the previous controller: remove it there first rather than retrying the code.
Last verified2026-10-14
How to cite this pageIoT Atlas. "Matter commissioning code is rejected". https://hi-spark.net/troubleshooting/matter-commissioning-code-rejected.html Last verified 2026-10-14.

Likely causes

  • Code already used to commission the device elsewhere
  • Typing errors in the manual pairing code
  • Device not reset to commissioning mode
  • Controller firmware too old for the device
  • Thread border router unavailable for Thread devices

Quick checks

  • Check whether the device already appears in another ecosystem
  • Verify the digits on the label or in the app
  • Confirm the LED shows commissioning mode
  • Update the controller app and hub firmware

Step-by-step fix

1

Remove the device from any ecosystem that already has it

2

Reset the device to commissioning mode

3

Choose add device in the controller app

4

Enter or scan the code once, without blind retries

5

For Thread devices, confirm the border router is online first

Frequently asked questions

Why does this happen: Matter commissioning code is rejected?

The controller says the pairing code is wrong, expired or already in use.

What is the most likely cause?

Code already used to commission the device elsewhere; Typing errors in the manual pairing code; Device not reset to commissioning mode.

What should I check first?

Check whether the device already appears in another ecosystem; Verify the digits on the label or in the app; Confirm the LED shows commissioning mode; Update the controller app and hub firmware.

How is it fixed?

Remove the device from any ecosystem that already has it; Reset the device to commissioning mode; Choose add device in the controller app; Enter or scan the code once, without blind retries; For Thread devices, confirm the border router is online first

When should the case be escalated?

If the code was already used, the device is still claimed by the previous controller: remove it there first rather than retrying the code.