I am waiting for cheaper leak sensors (Matter over Thread) to be released 
$100 for the Eve leak sensors is a little pricey
3 Likes
This is absolutely the main point. At best, it will slow down adoption considerably. At worst, manufacturers may decide it isn’t worth it. By not insisting on minimum standards for certification and clear descriptions of what each device can do, I think this will be seen as a massive missed opportunity rather than the breakthrough for home automation that it could have been. It is indeed early days, but there is little indication that it will actually improve in these important respects. Simply adding more and more device types to the standard does not help in this respect.
4 Likes
The Nanoleaf Sense+ is already out in US (still not in EU) and the advertised Matter compatibility of side buttons is not there 
. Instead, after people preordered it, they’ve changed the product page to add a “coming soon” to the Matter support of side buttons.
2 Likes
All of my lights are Nanoleaf M/T and I could just use their proprietary protocol but that’s not how I roll…
2 Likes
1 Like
The valve doesn’t support Matter, it’s Zigbee. The Aqara hub is required and acts as a Matter bridge to other smart home platforms.
5 Likes
The whole selling non matter devices as matter is wrong in my view. Undermines the whole matter ethos.
7 Likes
(Oops!)
It’s sort of like saying I can communicate in French. This is true – as long as I have a translator with me. But anyone who simply expects from my statement that I speak French is going to be disappointed.
3 Likes
BTW: The Aqara Hub M3 is still at Matter version 1.1 and their Camera Hub G5 is at 1.2.
2 Likes
2 Likes
That’s a good metaphor.
I don’t have a problem if, say, I’m setting up a business meeting and I get a message that “Mr. Kim does not speak English, but he will bring his own translator with him.”
For certain kind of meetings, I might want to see the translator’s credentials.
So that’s essentially what we have here. The matter bridge is certified. And it’s going to serve as the translator.
I’m happy with that and I don’t consider it deceptive as long as it’s clearly stated in the product description, which aqara has typically done.
From a practical aspect as A consumer, I have found that the bridge device is greatly increase. The number of devices I can have simultaneously connected to multiple home automation platforms, and have expanded the number of devices I can use in my setup.
Setup hasn’t been quite as easy as I like, particularly with SmartThings, but it’s been OK.
I think the Phillips Hue bridge has been an excellent industry model for how a well engineered bridge design can result in a greatly improved customer experience. So I personally don’t have any issue with that being a large part of the Matter experience at this time. 
1 Like
Edited since the docs are available now.
That FlicScript is a good idea, in Flic site states that “you can now subscribe and send commands to and from any [Matter 1.2] matter device”, and indeed the docs are already at Flic Hub SDK Documentation .
It can be pretty powerful, could even be the ultimate Matter automation machine with total control and being able to use all the features that smart home platforms don’t let you use, all in one automation. It’s like if the Matter SDK of any platform, usually restricted to developers, would be directly available in the automation engine.
That’s cool! Simple example, say you want to step the brightness of a light 10%. In SmartThings you would have to create a custom capability and a whole driver that handles all the Matter commands and events of the light (because you would need to replace the stock driver with yours), all that just for a line of code to send a “StepLevel” command. With the script you just send the command to the light!
The functions are quite low level: subscription, sendCommand, writeAttribute, but it’s indeed powerful.
Would be nice if the Rules API had something like that for Matter devices (a generic sendCommand and writeAttribute). Sometimes writing a custom driver feels overkill when you just want to send a simple command that is not exposed (like stepping a brightness) or set an attribute (like the power on state).
6 Likes
Really looking forward to this:
Temp, humidity, AirQuality, fan control, HEPA filter monitoring, PM 2.5 concentration, and tVOC clusters.
My current air purifier is a Tuya device in disguise.
The long awaited Eve app for Android has arrived, listed as ‘Eve for Matter’. I’ve not seen any comment on it, possibly because there is very little to comment on.
It currently only supports the Eve Thermo on Google Home. Not having such a device that is all I can say as it literally has no other functionality I can test.
Having exited and reopened the app it was immediately forcing me to connect to Google again even though it is already connected to two Homes. Repeating the process was more successful, bringing up the expected home screen.
1 Like
The main developer has left Eve Systems just days before the release of the app.
Yes, I saw that.
I just opened the app again. It opened to the home page but shortly after spontaneously asked me if I’d like to connect to Google (even though I was still already connected twice). This time it was politely on an app branded page rather than a black generic looking one. My options were to ‘Connect’ or to back out using the phone navigation.
1 Like
The Android app only works with Google Home as it was built on the Google Home APIs released earlier this year. Eve CEO Jerome Gackel said that these enabled the company to “turbo-charge the development of Eve for Android.” Felber said support for additional platforms, including Amazon Alexa and Samsung SmartThings, is coming in future versions.