A camera can be Matter-certified and still send you back to its vendor app for recording or motion features. That is the smart-home buying problem Matter has reached in 2026: the badge can confirm a common protocol without confirming a complete experience in your controller.

Matter 1.6 makes that distinction impossible to ignore. The standard is adding shared administration and better commissioning at the same time that Matter 1.5 cameras are exposing uneven platform support. Buyers should stop asking only, “Does this device support Matter?” and start asking, “Which parts of this device does my controller support today?”

The specification is moving faster than the buying shorthand

The Connectivity Standards Alliance’s Matter 1.6 release does not lead with a new device category. It leads with system behavior.

Its new Joint Fabric option lets multiple user-authorized controllers co-administer one shared Matter network. A device added to that fabric can be available to every participating controller, while administrators can be added or removed separately from the devices. The Alliance specifically identifies mixed-platform households, new-construction handoffs, and professionally managed properties as useful cases.

Matter 1.6 also adds full NFC-based commissioning. Earlier NFC support could carry setup information but still relied on Bluetooth Low Energy to finish onboarding. The new flow can complete the commissioning exchange over NFC, including before some installed devices are fully powered. That could make awkward ceiling fixtures and in-wall products easier to provision before final installation.

Those are meaningful infrastructure improvements. They are not promises that Apple Home, Google Home, Alexa, SmartThings, Home Assistant, or any other controller has implemented them already. The Alliance explicitly says device makers and ecosystems will ship 1.6 capabilities on their own timelines.

That lag is now the compatibility issue buyers need to track.

Controllers have become the real feature gate

Homey’s Matter 1.5 certification announcement is useful because it describes what controller readiness looks like rather than treating Matter as a logo.

The certification applies to Homey Pro models from 2023 through 2026, Homey Pro mini, and Homey Self-Hosted Server. Homey Pro and Pro mini include a Thread Border Router. The self-hosted product can add Matter-over-Thread devices when the household already has a compatible Thread Border Router.

Homey also says its Matter Bridge can share supported devices with Apple Home, Google Home, Amazon Alexa, Samsung SmartThings, and Home Assistant even when those devices do not natively support Matter. That can preserve some value in an existing Zigbee, Z-Wave, Bluetooth, infrared, RF, Wi-Fi, or cloud-connected setup.

But bridging and native support are not the same thing. A bridge can expose only the device types and controls that both sides understand. The practical question is not whether an old device becomes “Matter” in the abstract; it is whether the specific state, command, sensor, or automation you rely on survives the bridge.

This is why controller release notes now matter as much as product listings. A current controller can turn a standards update into useful features. A lagging controller can make a newly certified device behave like a basic accessory.

Cameras show exactly where the badge stops

Cameras are the sharpest current test because their useful behavior extends far beyond on/off control. Live video, snapshots, two-way audio, pan and tilt, detection zones, recording, local storage, alerts, and privacy controls all have to pass through the controller cleanly.

Matter Alpha’s survey of certified cameras reports that Tapo has certified three 4K models under Matter 1.5.1, EZVIZ has certified its C6c 4K, Ulticam’s certified IQ V2 remains delayed, and Aqara’s G350 provides the clearest shipping example.

That shipping example is also the warning. In Matter Alpha’s SmartThings test, the Aqara G350 exposed live video, snapshots, two-way audio, volume controls, and night-vision settings. Pan-and-zoom controls appeared in SmartThings, but the current camera firmware did not enable pan-tilt-zoom through Matter. Motion-triggered recording and some video settings were also unavailable, leaving the Aqara app necessary.

The same report says Home Assistant’s Matter backend contains camera capabilities while the user-facing camera implementation is still being built. In other words, certification, controller plumbing, visible entities, and complete feature support are four separate milestones.

For a buyer, “Matter camera” is therefore the beginning of verification, not the end. Check the exact hardware revision, controller, firmware, live-view path, recording path, and vendor-app dependency before replacing an existing camera.

Simpler devices still need a transport check

The SwitchBot Battery Circulator Fan 2 Pro report shows the other side of the market: a relatively simple endpoint where Matter can remove a hub from the purchase.

HomeKit News reports that the fan uses Matter over Wi-Fi, does not require a SwitchBot hub for Matter connectivity, and can expose power, speed, modes, schedules, and automations to compatible platforms. The report names Apple Home, Alexa, Google Home, Home Assistant, and Homey among the supported ecosystems. SwitchBot claims up to 70 hours of battery operation depending on speed, with AC and USB-C power available as alternatives.

That is a clearer interoperability proposition than a camera’s, but it still carries two separate engineering questions. Matter defines the application behavior; Wi-Fi is the network transport. Moving the fan to a patio or another room may solve a power-placement problem while creating a coverage problem. Battery runtime also depends on how aggressively the fan is used.

The buying lesson is precise: confirm both the Matter control surface and the radio conditions where the device will live. A standards badge cannot compensate for weak Wi-Fi, an overloaded controller, or a feature your chosen ecosystem has not exposed.

A five-part compatibility check for the next purchase

1. Match the controller version, not just the logo

Look for the device category and functions in your controller’s current release notes or support documentation. “Matter supported” is too broad when platforms implement versions and clusters on different schedules.

2. List the functions you would lose without the vendor app

For a camera, test recording, event history, privacy mode, detection, pan and tilt, and remote viewing. For a fan, test speed control, modes, schedules, and manual fallback. Decide which missing function would make the purchase pointless.

3. Separate Matter from its transport

Matter can run over Wi-Fi, Thread, or Ethernet depending on the product. Thread needs a compatible Border Router. Wi-Fi needs reliable coverage at the installation point. The Matter badge does not answer either network question.

4. Plan the ownership and handoff path

Joint Fabric is designed to make shared control cleaner, but Matter 1.6 adoption will take time. Until your ecosystems support it, document which account commissioned each device, which controller owns the automation, and how a future resident or family member receives access.

5. Keep one recovery path

Prefer devices with a physical control, local fallback, documented reset process, and clear firmware policy. Cross-platform control is valuable, but recovery should not depend on every platform staying healthy at once.

The takeaway

Matter is succeeding well enough that compatibility has moved up a layer. The protocol can define shared language, commissioning, and administration; the controller still decides how much of the product you can actually use.

For the next purchase, treat certification as an eligibility check. Treat controller support, exposed features, network transport, and recovery as the real buying decision.