Occupancy Without Identity: What Matter 1.5.1 Means for Sovereign Buildings

In March 2026 the Connectivity Standards Alliance shipped Matter 1.5.1, a maintenance release that mostly exists because Matter 1.5 finally put cameras and video doorbells into the standard. Multi-stream video and audio, HEIC snapshots, HLS and DASH upload via CMAF, more honest pan-tilt-zoom behavior, and chime or intercom refinements: that is what 1.5.1 actually is. It is not a Thread rewrite, and it is not permission to hang an RGB camera in every corridor.

For building owners, that distinction matters more than the spec sheet. Once cameras are a first-class Matter device type, vendors will sell video as the default occupancy sensor. Lighting, HVAC, access, and insurance underwriting will all be asked to consume identity-grade footage. Fotonara’s position is simpler. Occupancy is a facilities signal. Identity is a legal event. They should not share a pipe.

A building needs to know that a space is occupied. It almost never needs to know who is in it.

What 1.5.1 actually changed

Matter 1.5, released in November 2025, added cameras, video doorbells, closures, and a set of energy and metering clusters. Version 1.5.1, dated 31 March 2026, is the cleanup pass. The CSA’s own notes are camera-first:

• Multi-stream video and audio, so one camera can feed a high-resolution recorder, a lower-resolution mobile view, and an analytics path without spinning up independent streams for each consumer.

• HEIC snapshots, which are smaller than JPEG at comparable quality.

• Full HLS and DASH upload for recorded video using the CMAF Interface-2 profile.

• PTZ behavior that still works when the camera’s home position sits at the edge of its rotation range.

• Chime devices that can play a requested sound, not only the default tone, plus clearer intercom signaling and integrated-chime support.

Those are interoperability fixes. They make Matter cameras less painful to ship. They do not decide the architecture of a sovereign building. You can put a Matter doorbell on the public entry and still refuse cameras in suites, corridors, and care rooms. Specification is not deployment.

Why RGB occupancy is a liability

Cloud cameras were already a bad fit for commercial real estate. Recurring storage fees, vendor lock-in, and a server in another country holding a record of who walked a floor at 2 a.m. are operational and legal costs, not features. Matter 1.5.1 makes the camera cheaper to integrate. It does not make the footage cheaper to defend.

Canadian privacy law, tenant statutes, and senior-housing regulation all treat biometric and identifiable video as a different class of data from a binary occupied/vacant bit. Once a feed can reconstruct a face, a gait, or a care routine, you have created a record you must retain, protect, and eventually produce. Insurers notice. So do residents. The 2026 IoT security conversation is no longer about whether a gadget can phone home. It is about whether the building can prove it never did.

That is why Fotonara designs occupancy as a local, non-identifying signal. Depth and presence sensing without RGB, processed on-site, consumed by Home Assistant over Matter on Thread. No biometrics. No vendor cloud. No monthly archive of people. The lighting layer, the HVAC setpoints, and the security logic all get what they need: a room is empty, a room is occupied, a door should lock.

Local mesh, not a camera backbone

Thread is already in the ceiling if the lighting is Matter-native. High-efficiency photonic fixtures at roughly 240 lumens per watt are on 24 hours in the spaces that matter, powered, and geometrically distributed. That is a better radio mesh than a handful of battery sensors and a Wi-Fi camera pointed down a hallway. Use the lighting layer as the always-on fabric. Use occupancy as a privacy-preserving input to that fabric. Keep cameras, if you need them at all, at the perimeter where identity is an explicit choice.

The rest of the stack stays DC-native and Class 4 where the electrical design allows it: packetized, fault-managed power, local control, no requirement that every watt transit a cloud broker. FluidAra utility walls and the rest of the Fotonara kit exist so adaptive-reuse and net-zero projects can drop that stack into an existing shell instead of ripping the building back to studs. None of that requires a video plane.

How to read the spec without getting captured by it

If you are writing a 2026 smart-building brief, treat Matter 1.5.1 as three separate decisions:

• Perimeter video. A Matter doorbell or intercom at a public entry can be local-first, multi-stream, and still not an occupancy system.

• In-unit and in-corridor sensing. Occupancy, lighting, and HVAC should run on anonymous presence, Thread, and on-prem Home Assistant. Do not upgrade those rooms to cameras because the standard now has a camera cluster.

• Data residency. If a stream exists, decide on day one whether it ever leaves the property. Zero-cloud is still the only architecture that survives a vendor sunset, a subpoena, or a failed SaaS invoice.

Fotonara will keep shipping Matter over Thread, including 1.5.1 device types where they belong. We will not pretend that a better camera codec is a privacy policy. Occupancy without identity is the product requirement. The specification is just the transport.

Sales and technical questions: sales@fotonara.com. Fotonara Inc., Canada.