Matter 1.5.1 refines camera streaming and controls. Its release does not prove that your chosen platform supports every camera feature.
The Connectivity Standards Alliance released the update on March 31. Camera categories were introduced in Matter 1.5 in 2025; this release works on implementation details that can affect several viewers, recordings and related doorbell functions.
For a household choosing a camera, the useful question is which actions work in the app it intends to use—not simply whether a standards logo appears on the box.
A camera is several services in one product
CSA describes improvements including multiple optimized media streams, expanded media support and refinements to pan, tilt, recording configuration and related devices. Those mechanisms can help implementers deliver a more coherent experience.
They do not settle where recordings are stored, what an alert includes or which functions appear in a particular controller. A live image is not equivalent to a recording history. A working motion event is not proof that a doorbell call supports two-way audio.
Paul Lamkin’s April 1 contributor coverage puts the release in the context of refining the earlier camera debut. That reporting does not replace model- and platform-specific evidence for the buying decision.
Use a checklist of actions you actually need
Make the purchase requirements explicit before comparing products:
| Desired action | Evidence to request for the exact combination |
|---|---|
| See a live view in the household’s chosen app | Supported camera integration, firmware and controller version |
| Review an event later | Recording destination, retention and access method |
| Receive a useful doorbell alert | What the platform exposes when the button is pressed |
| Speak to a visitor | Explicit two-way audio support, not just video support |
| Adjust a movable camera | The controls actually available through that platform |
| Share access with another resident | Roles and functions available to that person |
This is a requirements checklist, not a set of tests already passed by a camera. Manufacturer documentation should identify what works through Matter and what still requires the vendor’s app or service.
If a product is also a hub or bridge, ask which component carries the certification and which camera actions it exposes. Otherwise, a badge attached to the overall product can encourage an assumption about video support that the specific implementation does not justify.
Completed standards work is not completed app work
October 12 verification update: Home Assistant’s camera-foundation roadmap item is closed as completed. Its stated scope explicitly excluded making every camera feature available to users. That is a concrete example of why a completed technical milestone should not become a claim of complete consumer functionality.
A platform needs a usable interface and support for the particular actions, not only an underlying data model. Do not read the issue’s earlier description of missing foundations as an unchanged current condition, either. The relevant claim is its scope, alongside its completed status.
Open interoperability could give households more choice of app and future replacement hardware. Vendors may gain access to more ecosystems. Early buyers could pay for a camera whose most important functions still require the same subscription or app they hoped to leave.
Before purchase, verify the functions on both sides of the combination. During the return window, try the ordinary sequence that matters to you: notice an event, inspect it, speak if needed and find the recording later. A successful pairing screen is only the start of that sequence.
Frequently Asked Questions
Did Matter first add cameras in March 2026?
No. Matter 1.5 introduced the category in 2025. Version 1.5.1 refines it.
Does Matter compatibility remove the need for every subscription?
That cannot be inferred. Storage and additional services depend on the actual product and platform arrangement.
Does a live view mean two-way audio is supported?
No. Confirm the separate action in the controller you intend to use.
What does a closed platform roadmap issue establish?
Read its scope and the current product documentation. Foundation work can be complete while user functions remain separate.
Should I buy on a promise of a future update?
Tie the purchase to functions available for your exact combination. Treat an undelivered roadmap item as an uncertainty, not a feature you already own.