We know that bulbs, plugs and switch have the right chip
I thought that the integration would be from ST to the Sense Hub. That way we can access the sensors that it has access to as well as the other devices. I would also like this connection to be local. Will the sensors be accessible by ST?
Why would you tie your company name to Matter if literally none of your products that are released, releasing, or due to release are known to actually work with Matter? Could you possibly be any more dishonest about it? I don’t think so.
What about the cameras? How do we get that integration into ST via Matter? That doesn’t seem to lineup.
If you guys don’t want to do it, why not just bring an open API and let the community do it for you? Hell, out the api behind cam plus if you’re worried about extra ongoing costs.
In the post above about SmartThings integration, it doesn’t seem that hubs can talk to hubs in the matter protocol, or at least the ST integration won’t be allowing that.
ST will need to be able to talk to the devices directly.
I am not sure if that is what the above means. I think for Samsung they are not allowing that but for Matter it seems you can interface with other ecosystems. I sure hope so.
:::::::
https://www.threadgroup.org/
"Matter communicates over Wi-Fi, Thread, or proprietary bridges. "
:::::::
++++++
"With Samsung SmartThings adopting Matter, it will be possible to add devices that previously couldn’t connect to the SmartThings app or hub and, in reverse, connect SmartThings compatible devices to other Matter-enabled smart home ecosystems. For example, an Eve LED light strip that previously only worked with Apple’s HomeKit could be added to and controlled by the SmartThings app. "
++++++
–
Because it’s pay for play. We have no idea what it means to be Matter compliant by being outside the association. We had to pay and be part of the CSA to be able to understand what it will take to create a device and what are the impact on the overall business.
We were starting to have also some pushes from our partners to join the Matter initiative to continue working on some initiatives.
The reality of Matter is that it is still a moving target and we are not ready to talk about our plans with Matter. We are definitely interested and are looking at the impact on the current products, futures products and more importantly the current ecosystem that we have.
Also be sure that despite having 200 companies in Matter, you can be sure that not all of them will adopt Matter. I think all the traditional players will and we want to be one of them but timing is also going to be important.
Hubs can talk to hubs in Matter. For example, Hue has announced their Hue bridge will be a Matter certified bridge and expose its devices for Matter controllers to integrate with. A Matter bridge makes its connected devices accessible to any Matter controller on the network/LAN, includes SmartThings hubs, Samsung TVs, etc. Samsung has chosen to only make the SmartThings Hub a Matter controller and not a bridge. So a SmartThungs hub will connect to other Matter devices and bridges, but it will not expose its own zigbee/zwave devices to other Matter controllers (i.e. HomeKit). Yes, its all very confusing, and as Frederik alluded to, the spec isn’t finalized.
Cameras are not included in Matter for the moment but there is no reason why they can’t be in the future but right now, I’m not aware of any work in that area.
For the integration, a matter compatible devices will be able to enable Matter enabled ecosystems. So SmartThings is saying, that they will enable their ecosystems with Matter. Matter devices should be able to join multiple Matter ecosystem at the same time.
I guess there is enough in Matter to do a full livestream session but for the devices to be Matter compliant, there are multiple ways: But for Wyze Sense Sensors, we can make the new hub Matter compliant and use it as a bridge/gateway. There is a provision in Matter to do just that. Since we are using the same processor than the camera (not ESP32) and it is not supported by default by Matter, we would have to recompile the entire Matter SDK to make sure it is working properly. It should be easily doable since it is using Linux Embedded if my memory serves me correctly.
Thanks @Frederik - I appreciate the frankness in discussion on this topic. It is quite refreshing.
Really, I’d like to be able to have an image captured and sent alongside the notification from SmartThings based on a trigger (e.g. motion sensor triggers when home is set to “away”). This is possible with (some) camera integrations on the SmartThings platform.
It sounds like for those of us that wanted to use Wyze cameras as part of a smart home system… we’re out of luck. At least for the next several more years or so.
Thanks for the transparency @Frederik. Camera streams and images may not be supported by the Matter spec currently, but I wonder if you could at least expose the motion and switch capabilities to matter? That way some functionality could be had between those devices and Matter controllers.
There is what I want to do and what Wyze can do. Two VERY different things! 
Yes, I would like all the sensors, bulbs, plugs and Lock exposed through Matter at its launch time. But for the moment, this is a lot of work that needs to be done. Making the devices themselves compliant is not excessively difficult but we have to build up the expertise and divert some of the resources that are currently working on the engineering of the current products to work on that.
Again, it would be too long to talk about all the work that needs to be done. But there are some obvious questions like: should we keep both wyze IoT implementation and add Matter? That would most likely be possible because of the hardware limitation. So should we remove Wyze IoT and replace it with Matter? Sounds like a good idea but then how do we integrate the device in the Wyze ecosystem… Well, it means that we have to have some other means of communication with the cloud and also have a way of representing generic devices in the Cloud…
If we keep pulling on that thread, we end up with a massive amount of work that has to be achieved before we can even put a Matter device on the market.
The TL;DR is that right now, we are actively looking at Matter. I’m the POC for Matter for Wyze. I’m running several (raspPi) prototypes to understand the maturity and the complexity and develop the expertise around Matter. I’ve briefed the upper management on the business challenges and technical opportunities around Matter. I’ve also started to develop a plan for the adoption of Matter but we have not committed the development time for the moment on Matter because we have a serious backlog of features for the current products for the coming months and to support the launch of the products that have already been committed.
One thing I did not touch on was the API for the cameras. We have been working since December 2018, yes that far out, on adding the support for WebRTC to most of the video products. We have seen the benefit in the last months with Alexa and Google but this is going to open up the possibilities to connect to many other applications.
One of the thing that becomes possible is the ability to display a WebRTC session in a web browser almost natively. Most of the partners I’ve talked to (outside of Amazon and Google) have a WebRTC strategy. So there is an opportunity to have the video feeds to be dispatched. The engineering team I know is working on a comprehensive overhaul of the back end that should bring us closer to an official API. It’s not decided for the moment if we will have one or not but it was not possible before and it is becoming possible.
My 3rd party integration vision relies on people doing the work to integrate with us and not the other way around as it is not scalable in the long run and that requires an official API. Now you know where I stand on the topic. 
A LAN accessible WebRTC address per camera would be very cool so its usable in things like SharpTools.io
After 3 years and almost 900 posts in this thread, we appreciate someone from Wyze finally coming in and talking tech about this topic. Thank you for that.
Thanks for responding. Does the v3 cam have the chip also? I will be waiting to buy any additional Wyze products until I know for sure what I am buying will work with Matter unless you offer some type of ‘upgrade’ option for those those of us that have already invested in the Wyze Ecosystem to lessen or nullify additional costs just to have equipment that is Matter compliant.
Sorry I missed the post about Cameras not being included…
I really hope you do consider to include Cameras in Matter as the are extremely important to work with devices and dashboards in a Smarthome Security set-up. Especially when using a dashboard and to work with lighting…
There is not a Matter chip as Matter is a purely software based solution but some of the chips are optimized for Matter or in the case of ESP32 have the SDK compiled and tested as part of the Matter development process.
The only requirement that Matter is putting in place is that the device should be supporting IPv6 and (optionally) Bluetooth for provisioning. So there are a lot of devices that are meeting that criteria. But since Matter is still under development, we have no idea the memory size that will be required, the amount of compute that will be required too, which makes predicting which existing devices to be compatible near impossible.
So specifically on the camera v3, I’m pretty confident that we have the amount of compute. I’m not about the amount of flash memory that we have and I don’t know how much work it will take to get Matter working with the ingenic T31X and last I don’t know how much it will take to make sure that we are not breaking any of the integration that we have with the Wyze ecosystem and the support for WebRTC. We are just too early to answer that.
I’ve been following that thread from day 1 and I happened also to be a (light) SmartThings users ever since Wink decided to mock with what they had… 