Direct answer
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. For Matter controller commissioning, first confirm the code, reset state and nearby active controller before adding.
What this covers
- Matter controller commissioning with this exact failure state
- Diagnosis across controller/hub eligibility versus Bluetooth, Thread/Wi-Fi and prior commissioning
- Customer-accessible observation, settings and external components
What it does not cover
- ×A displayed manufacturer error code with a different documented meaning
- ×Live electrical, sealed-system, internal battery-cell or gas repair
- ×A claim that every model exposes identical controls
Capture the exact failure state
ReversibleRecord whether the feature is absent, disabled, powered but unresponsive, or showing a message. Expected behavior: add an eligible accessory to one fabric using its private setup code.
Isolate the component boundary
ReversibleConfirm the code, reset state and nearby active controller before adding. Test the simplest supported configuration with unrelated accessories and optional services removed. Boundary to separate: controller/hub eligibility versus Bluetooth, Thread/Wi-Fi and prior commissioning.
Correct only the proven cause
ReversibleRemove from the old fabric or use multi-admin sharing rather than repeated resets. Restore only the failed prerequisite or path; do not change working layers.
Verify and stop safely
ReversibleRepeat from a cold start and complete one normal use. Keep setup codes private and do not reset shared security devices casually.
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 should I check first when Matter controller commissioning has this problem?+
Confirm the code, reset state and nearby active controller before adding.
Why not factory-reset immediately?+
The useful boundary is controller/hub eligibility versus Bluetooth, Thread/Wi-Fi and prior commissioning. A reset can erase state without proving which side failed.
When should I stop troubleshooting?+
keep setup codes private and do not reset shared security devices casually.
Answer for the exact device and software version shown above.