For those wondering, I’ve been looking into the details of the Matter 1.5 release and thought some others might appreciate some of this info about what is possible with Cameras on Matter now, to know what Wyze COULD offer if they add Matter support to their current &/or future cameras.
Matter 1.5 formally introduces a family of camera device types, not just a single “camera.” These include Camera, Snapshot Camera, Intercom, Video Doorbell, and Audio Doorbell (It also supports Floodlights/Spotlights on Cameras that have those and explicitly allows PTZ controls for all pan cameras)
Comprehensive Feature Support Matrix for Matter 1.5 Cameras
| Feature Domain | Specific Capability | Matter 1.5 Support | Technical Implementation / Cluster |
|---|---|---|---|
| Video Transport | Live Streaming | Supported | WebRTC with TCP/UDP transport 1 |
| Multi-Stream Config | Supported | Camera AV Stream Management | |
| Remote Access | Supported | STUN and TURN protocols 8 | |
| Doorbell Functions | Button Press (Ringing) | Supported | Boolean State / Switch Cluster |
| Intercom (2-Way Audio) | Supported | WebRTC Audio Channel 9 | |
| Physical Control | Floodlight (On/Off) | Supported | On/Off Cluster 9 |
| Spotlight (Brightness) | Supported | Level Control Cluster 9 | |
| Pan-Tilt-Zoom (PTZ) | Supported | PTZ Control Clusters 18 | |
| Storage & Recording | Query Storage Status | Supported | Storage Management / Media Clusters 2 |
| Configure Recording | Supported | Event/Continuous Mode Config 1 | |
| Retrieve Clips/Snaps | Supported | TCP Transfer / Snapshot Cluster 9 | |
| Energy & Power | Real-Time Consumption | Supported | Electrical Energy Measurement 4 |
| Cost & Carbon Data | Supported | Tariff & Cost Clusters 24 | |
| AI & Intelligence | Person/Pet/Vehicle | NOT Supported | No cluster for classification 4 |
| Motion Detection | Supported | Occupancy Sensing / Boolean State 3 | |
| Audio Detection | Partial | Generic Boolean State (True/False) 12 | |
| Configuration | Detection Zones | Supported | 2D Cartesian Zone definitions 9 |
| Privacy Masks | Supported | Geometric masking of video feed 18 | |
| Sensitivity Control | Supported | Boolean State Configuration 15 | |
| Power Mgmt | Battery Optimization | Supported | “Snapshot Camera” device type 9 |
| Extensibility | Custom Features | Possible | Mode Select Cluster (e.g., Night Vision/IR) 23 |
Note, it seems it may only support an image as a notification and may not support sending a “Text” notification through the camera (it’s possible that the platform itself would have to decide what the text of the notification is)
FYI, the fact that AI detections are not supported is not an accident. From what I am reading, this omission is likely not an oversight but a strategic compromise. The ostensible rationale given is that standardizing AI metadata is incredibly complex; defining a universal taxonomy for every possible object (Person, Dog, Cat, Bird, Package, Face, Car, Truck, Bicycle) is a big undertaking. But the real reason appears to be that retaining proprietary control over high-value AI alerts protects the subscription business models of major manufacturers like Google (Nest Aware) and Amazon (Ring Protect). If Matter commoditized AI alerts, users could buy inexpensive hardware and rely on generic hubs for advanced filtering, undermining the recurring revenue streams that sustain the industry giants, so they didn’t allow it and came up with excuses to prevent it. The truth is that they could easily standardize a few of the most important detections (Person, Package, Vehicle, Crying, etc) and create a standardized binary sensor for it that the camera can toggle on and off. This would allow Local Edge AI or Cloud AI to support AI detections through Matter and would actually be as easy as the same way they support the motion detection binary sensor or Sound detection. They are just purposely compromising to appease the greed for the time being.
Matter 1.5 will allow your cameras to work together, but it will not yet allow them to think together. You will gain a unified viewing experience and basic automations, but for the foreseeable future, the advanced AI features you pay for will likely remain locked within the manufacturer’s own application.
Maybe it will happen later though. For now, this means that while Matter is still AWESOME, it’s still not as good as a “Works with Home Assistant” level integration. 
Speaking of which, With Matter Bridge on Home Assistant, I suspect that if Wyze just integrated with Home Assistant then Matter Bridge will be able to convert their cameras to work with Matter through the Matter Bridge and Wyze won’t actually have to spend all the R&D adding back support for Matter to old model cameras as the Home Assistant Matter Bridge will likely be updated to do all the work for them. Then Wyze can just focus on adding native Matter support to all the new cameras. Everyone wins!
“Clever” Workarounds: The Mode Select Cluster
While Matter 1.5 lacks explicit clusters for “Night Vision” or “AI Detection Types,” manufacturers are finding ways to expose these features using generic clusters. A prime example is the Mode Select cluster.
- Scenario: A manufacturer wants to let users toggle “Night Vision” between Auto, On, and Off.
- Standard Way: There is no “Night Vision” cluster in Matter 1.5.
- The Workaround: The manufacturer implements a generic Mode Select cluster. They define three modes: “Mode 1 (Auto)”, “Mode 2 (On)”, “Mode 3 (Off)”.
- Result: The Matter hub sees a generic “Mode” setting. The user can change it from Apple Home or Google Home. While the hub might not know semantically that this controls infrared LEDs, the functional control is achieved without a proprietary app. Research indicates companies like Aqara are already using this “Advanced Matter Bridging” technique to expose local features like night vision or specific detection modes to third-party apps.
Other info for those interested:
At the heart of the Matter 1.5 camera specification is the adoption of Web Real-Time Communication (WebRTC) as the mandatory standard for video and audio streaming. This decision represents a significant departure from older, fragmentation-prone protocols like RTSP (Real-Time Streaming Protocol) or proprietary cloud-relay mechanisms often used by legacy manufacturers.
WebRTC was selected for its unique ability to establish peer-to-peer connections directly between the source (the camera) and the client (the smartphone, smart display, or hub) through a browser-based architecture. In the context of Matter 1.5, this means that when a user opens the Apple Home app or Google Home app to view a camera feed, the video data travels the shortest possible path between the devices, often staying entirely within the local network (LAN) if both devices are on-site. This architecture drastically reduces latency—often to sub-second levels—which is a prerequisite for the interactive “Two-Way Talk” features demanded by modern consumers.
Note that Wyze already supports WebRTC. It has been using this to connect to Google Home and Alexa since at least 2021 or so…so the cameras have already been using this protocol.
3.1 Streaming and Multi-Stream Support
Matter 1.5 supports Multi-Stream Configurations. This is a sophisticated feature that allows a single camera hardware unit to generate multiple distinct video feeds simultaneously, each with different encoding parameters.
In practice, this allows a Matter camera to send a 4K, high-bitrate stream to a local Network Video Recorder (NVR) for archival purposes, while simultaneously sending a lower-resolution, bandwidth-optimized stream to a smartphone over a cellular connection. This negotiation happens via the Matter protocol, allowing the viewing device (the client) to request the stream that best matches its display capabilities and network conditions. The support for multi-stream is essential for the modern smart home, where a user might want to view a camera feed on a small Apple Watch screen (requiring low resolution) and a large 85-inch television (requiring 4K) at the same time.
Energy Management and Carbon Data
Matter 1.5 significantly expands Energy Management capabilities, which is highly relevant for hardwired or PoE cameras.
- Cost & Carbon: Devices can now report real-time energy consumption, estimated costs, and carbon impact.
- Application: A PoE security system can now report its exact energy footprint to the home controller. If the home enters a “Green Mode” to save energy, the controller could use this data to power down non-essential floodlights or reduce the recording resolution to save processing power.
Anyway, that’s a short combined summary from around 30 sources. Thought I’d save some of you the time and answer the most applicable questions some of us likely had about it. 
Now that we’re all up to date on what “Supporting Matter” would or could mean, I am definitely more interested in getting Matter support than standard RTSP. I would fully support Wyze in making Matter a priority on all cameras that can support it. I hope Wyze soon updates this wishlist from “In Progress - Researcing” to “In Progress - In Development”. I will certainly be asking them about Matter in future AMA events.