The decision question
Which application protocol, transport, commissioner, controller, border router, ecosystem, and feature path is required for the intended connection?
This owner records one layered connection path for an intended feature; it is not a general explainer, recommendation, device activation, or badge-based approval.
Collect the required inputs
| Input | Required? | Unit or format | Evidence source |
|---|---|---|---|
| Exact device, model, generation, region, and firmware | Required | Complete device identity | Device and official documentation |
| CSA certificate and Matter version or device type | Required | Certificate record and scoped device type | CSA certified-product record |
| Transport | Required | Wi-Fi, Thread, Ethernet, or documented alternative | Exact device documentation |
| Commissioner and controller | Required | Named device/app and supported role | Current ecosystem documentation |
| Thread border router | Required | Exact model, region, account, and firmware when Thread is used | Thread and ecosystem documentation |
| Ecosystem and intended feature | Required | Named ecosystem plus exact user-visible action | Current ecosystem support documentation |
Apply the route-specific decision logic
- Record the exact device identity and intended feature before checking logos.
- Separate the Matter application layer from the Wi-Fi, Thread, or Ethernet transport.
- Verify commissioner, controller, and border-router roles independently.
- Match certification, firmware, region, and ecosystem support to the exact device and feature.
- Mark each layer PASS, BLOCKED, VERIFY, UNKNOWN, or NOT_APPLICABLE; the complete path passes only when every required layer passes.
Reader states: PASS means all required facts support the result. BLOCKED means a recorded conflict stops the plan. VERIFY identifies a named measurement or document that can settle the row. UNKNOWN means the needed fact is not established. NOT_APPLICABLE means the row is outside this exact branch.
Complete the layered connection-path compatibility matrix
Print or copy this record. Values stay in your browser and are not submitted or saved.
Evidence boundaries
The Connectivity Standards Alliance Matter FAQ describes Matter commissioning and IP transport roles at an architectural level.
The Thread Group Border Router white paper describes the border-router role connecting a Thread network to adjacent IP networks.
The Google Home supported Matter devices documents current Google Home device-type and feature support within its stated ecosystem scope.
Do not infer: Exact certificate coverage, firmware support, transport, controller or border-router role, region availability, and user-visible features remain UNKNOWN until every applicable layer is verified.
Use the completed record
This owner records one layered connection path for an intended feature; it is not a general explainer, recommendation, device activation, or badge-based approval.
- Continue with smart-display compatibility when that separate decision is needed.
- Continue with protected protocol comparison when that separate decision is needed.
- Continue with Matter, Thread, and Wi-Fi terms when that separate decision is needed.
Documented examples stay scoped
The governed build retains the already approved model-specific example at this location. It remains evidence about that named model only, never a recommendation, ranking, purchase prompt, or shortcut around the layered matrix.