Make the compatibility matrix a project deliverable
For a mixed-brand project, a compatibility matrix is more useful than a row of ecosystem logos. It should show the exact model, controller and requested function that were checked, so purchasing and installation use the same assumptions.
Describe one function per row
Separate basic device control from advanced settings or notifications. A product may be visible in a platform without exposing every native-app feature. The matrix should describe what the customer expects to use, not merely whether pairing succeeded.
Record the checked combination
Include firmware or integration references where they affect the result. Keep substitutions visible. Matter’s common framework can support interoperability, but the project still needs checks for the selected devices and the desired platform experience.
Use it in procurement and handover
Send the matrix to HomeTech with a technical sourcing enquiry and keep the accepted version in the handover pack. A future maintainer can then understand the intended combination without reconstructing it from advertisements or old quotations.
Before you buy
- Separate basic and advanced functions
- Record exact checked models
- Keep the accepted matrix