Compatibility check 1: Matter controller role
For matter hubs and bridges, record the exact value, standard, measurement, or supported condition behind Matter controller role before checkout. A broad category label does not prove that the selected variant fits. Confirm the manufacturer, complete model, hardware revision, electrical rating, protocol, controller support, included parts, and region rather than assuming similarly named products share limits.
Compatibility check 2: Thread border-router role
Test Thread border-router role across the actual fixture, circuit, controller ecosystem, radio path, owner account, and manual fallback—not a product-photo setup. If this matter hubs and bridges fit depends on a neutral wire, hub, bridge, account, subscription, compatible controller, professional installation, or reliable cloud service, confirm the exact part, service, or behavior as part of compatibility.
Compatibility checks 3 and 4: bridged protocol and device limits; multi-admin sharing, local control, and account ownership
For matter hubs and bridges, bridged protocol and device limits and multi-admin sharing, local control, and account ownership are the limiting conditions most likely to surface only after installation. Measure the smallest clearance, weakest connection, least compatible user or device, and the most demanding normal task. Passing an ideal bench test is not enough.
Prove fit in a reversible order
Use this sequence: inventory radios and controllers, update them, commission one device to the primary fabric, test local control, then share to secondary ecosystems. Keep labels, packaging, manuals, and the previous system until the product works through normal use and a recovery test. Photograph wiring, measurements, or assembly states that would be difficult to reconstruct.
A failed fit check is a stop signal
Stop when the advertised box does not provide the required controller or border-router role, or platform sharing removes important device features. Do not repair a fundamental mismatch with unapproved accessories, copied settings, or community anecdotes. Use platform-native controllers when it meets the job with a clearer compatibility path.