Direct answer
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. 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
ReversibleLog the trigger, duration, indicator state and whether physical movement or temperature changes it. 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. Hold every variable constant except one cable, location, load or host at a time. 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. Replace or reconfigure the one variable that reproduces the drop.
Verify and stop safely
ReversibleRun beyond the previous failure time and through sleep, movement or load once. 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.