Problem statement
The Matter specification evolves on a roughly six-month cadence, and the HA Matter Server (matter.js) tracks it as closely as resources allow. In practice, each spec release introduces more features than any single controller-side implementation cycle can absorb. Over time, this creates a growing delta between what the current Matter spec defines, what matter.js implements, and what the official C++ Matter SDK exposes as reference behavior.
Without a structured effort to map this delta, prioritization decisions for future roadmap cycles rely on incomplete information. Features may be missing from HA's Matter implementation not because they were deprioritized, but because they were never systematically evaluated. Conversely, effort may go toward areas that matter.js already covers adequately, while genuine gaps go unnoticed until a user files a bug or a device fails to behave as expected.
This opportunity is about creating a clear, shared picture of where HA's Matter implementation stands relative to the current spec and the official SDK. The output is not a delivery in itself, but the factual foundation for scoping future activities with confidence.
Community signals
More of a public housekeeping activity.
Scope & Boundaries
In scope
Not in scope
Foreseen solution
No response
Risks & open questions
No response
Appetite
No response
Execution issues
No response
Decision log
Problem statement
The Matter specification evolves on a roughly six-month cadence, and the HA Matter Server (matter.js) tracks it as closely as resources allow. In practice, each spec release introduces more features than any single controller-side implementation cycle can absorb. Over time, this creates a growing delta between what the current Matter spec defines, what matter.js implements, and what the official C++ Matter SDK exposes as reference behavior.
Without a structured effort to map this delta, prioritization decisions for future roadmap cycles rely on incomplete information. Features may be missing from HA's Matter implementation not because they were deprioritized, but because they were never systematically evaluated. Conversely, effort may go toward areas that matter.js already covers adequately, while genuine gaps go unnoticed until a user files a bug or a device fails to behave as expected.
This opportunity is about creating a clear, shared picture of where HA's Matter implementation stands relative to the current spec and the official SDK. The output is not a delivery in itself, but the factual foundation for scoping future activities with confidence.
Community signals
More of a public housekeeping activity.
Scope & Boundaries
In scope
Not in scope
Foreseen solution
No response
Risks & open questions
No response
Appetite
No response
Execution issues
No response
Decision log