This week, Project Connected Home over IP became Matter, and with the new name came new information about how it will provide interoperability between certain classes of smart home devices. Now that the protocol is back in the spotlight, I’m getting a lot of questions from readers around what will happen to their existing gear, what will happen to various individual radio protocols, and what all of it means for the industry at large.
So I’m pulling everything into one big Q&A story with links to our prior coverage and thoughts on the standard. For a full rundown, read on!
What the heck is Matter? Matter is a smart home interoperability protocol that was launched by Apple, Amazon, Google, Samsung, and others back in December of 2019. The goal was to create standard data models for popular smart home devices so these devices could work with one another without having to figure out which ecosystem “talked” to the particular device a consumer wanted to buy. Instead of a consumer wondering if a Nest thermostat was HomeKit compatible, Matter will ensure that a Matter-certified thermostat will work with any Matter-compliant sensor or controller.
What the heck is Thread? Thread is a radio protocol developed back in 2014 by the folks at Nest to connect devices to the internet and to other devices. Along with Wi-Fi, it’s the chosen radio protocol over which Matter devices will communicate. Low-power devices that send small amounts of data will use Thread, while devices with access to power and those that have higher data needs will use Wi-Fi. Kevin wrote an excellent article about Thread and how it works here.
What does this mean for Zigbee, Z-Wave, or Bluetooth? For more than a decade, Z-Wave and Zigbee have reigned as the primary connectivity standards for sensors in many alarm systems and high-end home automation setups. Bluetooth over the past few years also joined the cluster of radios, with Bluetooth mesh. None of these will disappear overnight, and in the meantime we’ve explained what we think will happen for Zigbee and Z-wave here and here as well as what the role is for Bluetooth going forward here.
What does this mean for my existing smart home gear? The answer to this question very much depends on the company that makes your devices. Signify, the company that makes Philips Hue bulbs and WiZ-branded smart bulbs, is treating those product lines very differently, for example, updating existing Hue gear to work with Matter and putting out new WiZ gear next year that will be Matter-compliant, but not updating existing devices. And Google is hinting that we’ll hear more about its plans next week at Google I/O, but other brands are mum. Personally, I would feel better if my WiFi- and Thread-based devices were getting updates, as well as any devices that have a bridge containing Wi-Fi-based or Zigbee-compatible radios. (The Thread protocol uses the same radio standard as Zigbee.) But even if your gear isn’t Matter-compliant, I don’t expect it to stop working immediately. You’ll likely see a graceful degradation and a loss of support over time. I also expect that you will be able to use Home Assistant or other software to link your Matter devices to your existing setup.
I use Home Assistant; can I still use it when Matter devices hit the market? Paulus Schoutsen, the founder of Home Assistant, said via email that he’s hopeful with regards to Matter. He emailed, “We haven’t seen the spec yet, but it is supposedly based on dot dot, which itself was based on Zigbee 3.0 – which we already support. The spec is kept in a private repository that we can’t access. We’re working on joining the alliance to get access.” He also said that Silicon Labs is working on a chip that would support both Zigbee and Matter, which means users of Home Assistant, could expect hardware that will bridge their Z-wave gear to Matter. Theoretically, the developers building for Home Assistant hubs (you can buy one or load the software onto your own machine) will be able to tootle over to the Matter GitHub repository and create drivers that will let users bridge their Home Assistant setup to include Matter devices. Kevin even found instructions for building your own Thread border router in GitHub, which means people using Home Assistant could buy the radios and build the connectivity infrastructure needed. Sure, this is for hardcore DIYers, but that’s who is using Home Assistant, Open HAB, Homebridge, and some of the other open source automation platforms.
I make sensors—what does Matter mean for me? The answer here is both good and bad. The good news is that companies making sensors, lightbulbs, switches, locks, and more can focus on their core competencies and forget having to build apps, figure out cybersecurity, and architect cloud infrastructure. The bad news is that for many of the existing hardware or lighting companies backing Matter, adding a digital component to their products represented their chance to create a new business built on services or customer data. With Matter that becomes more challenging, because customers won’t need to download apps to get their shiny new connected devices onto their networks and working for them. They’ll be able to just buy a Yale lock, get it on their network, start using HomeKit or Google to build routines, and never need anything else. Sure, manufacturers will try to add cool features to their apps and will likely force users to register the devices using those apps. However, with Matter companies that want to build services using connected hardware no longer have to go to those hardware makers to build a service. I expect companies to split into making low-margin commodity Matter devices and higher-margin Matter-compliant devices that focus on physical craftsmanship and prestige branding. Doing so will work well for visible devices such as locks but likely less well for things like sensors and traditional light bulbs.
I am a commercial installer—what does Matter mean for me? This is a tougher question. Companies such as Crestron and Control4 are members of the Matter working group while Ezlo and Savant are not. By commodifying the underlying hardware in locks, lighting, TVs, HVAC, and security sensors, the overall cost of such devices should fall, because much of the complexity of building an app or integrations disappears. Theoretically, by making it easier for a consumer to install these devices in their homes and program them, professionals become less valuable. However, plenty of products — such as sound systems, security cameras, and appliances — aren’t encompassed by the Matter standard. And given that most pro installers work on expensive homes with complex needs for busy people, I don’t expect Matter to eliminate that business. But it will likely cut some of the margins for distributors and professional automation companies, and prevent them from moving too far downmarket.
Want more Matter information? I will be moderating a panel on behalf of Silicon Labs on June 8 that will feature panelists from Wyze, the Connectivity Standards Alliance, Allegion, Comcast, Nanoleaf, and Silicon Labs. I’ll be asking what comes next for the industry and what this means for various players. You can register here if you want to know more.
So far I have not seen anything official that says that being Matter-compatible will automatically mean being HomeKit-compatible, and HomeKit does have some security and privacy requirements that matter does not. Just as one example, HomeKit devices have to be able to run locally. That’s not a matter requirement although it will support local operations if desired (except, of course, for the voice assistants which are still cloud-based).
I see a lot of confusion by individual bloggers (including one which temporarily appeared on the Google site and was then withdrawn an hour or two later) from people who think that being compatible with Siri means being compatible with HomeKit, but it doesn’t. There are devices now, such as Switchbot, which will work with Siri shortcuts but which don’t come natively into HomeKit.
So it’s entirely possible that being Matter-compliant will mean “will work with Siri shortcuts“ but not necessarily with HomeKit.
So I would think one of the most popular questions in a Matter FAQ right now would be “how does being Matter-compliant affect working with Homekit?“ Apple hasn’t put out a statement on this that I’ve seen yet.
I do think that being matter-compliant would make it much easier for a device to be HomeKit compliant, and that Apple would be all in favor of that. But there are still a few other issues, including being able to run without a cloud (again, except for the voice assistants).
If you find an official statement from either CSA or Apple on what Matter will mean for HomeKit, could you please add it to the FAQ?
Answering my own question, Apple has unveiled their plans for matter and they look really good. There will be a parallel path into the same app that is used for HomeKit. Very cool.
https://developer.apple.com/videos/play/wwdc2021/10298/
Any information regarding how Matter will integrate blockchain technology? Are they developing their own proprietary ledger or utilizing existing systems?
PRIVACY??? HELLLLLLLOOOOO STACEY!!!
Bless your heart with your enthusiasm for the technological advances, but please remember privacy is non-trivial to most folks.
PLEASE ASK THE HARD QUESTIONS TOO (If you haven’t already, and it’s just not listed here AND FIND OUT IF THEIR PLANS TO SHARE THE USER’S HOME IOT SPACE WITH EACH OTHER IS IN PART MOTIVATED BY THE PROMISE OF A GREATER FINANCIAL RETURN BY SHARING ALL OF A USER’S PERSONAL HOME LIFE DATA AMONGST THEMSELVES IN THE PROCESS?
.
IF NOT CAN THEY POINT TO WHERE CONSUMERS’ PRIVACY IS BEING ENGINEERED IN?
WILL CONSUMERS BE ABLE TO VIEW THE DECRYPTED TRAFFIC
.
Really want to be excited about this but I don’t see much being said about privacy… it would be a serious downer if interoperability of competitors’ devices is being even partially motivated by basically an agreement amongst these multi billion, and trillion dollar companies to share data about the users’ lives amongst themselves for the sake of monetizing it by passing the usage data freely between the devices in the name of user friendly interoperability.
It’s hard to believe Amazon or Google— These poster child companies of profiling and profiting without end—would be getting into this game and willingly agree in the process to the door being shut on them for their usual acquisition of consumer behavior data via IOT in this case (which includes health by the way, and you can model for it…e.g. if you consider the fact that people with certain health problems may need to get up in the middle the night to use the restroom more frequently than others etc.)
If they tell you yeah we will protect consumer privacy….then perhaps it may be worth asking:
Is The value of inter-operability to Amazon and Google in particular really worth shutting off the flow of information about people’s private lives that they have always monetized as a very corner stone of their business models?
That just doesn’t seem rational unless I’m missing something here.
There’s no mention as to the whether users will have any say about whether these devices connect to the Internet either.
I’m all for encryption, but we won’t be able to inspect the traffic between these devices because of it doesn’t look like… so who can audit the ethical practices of what these companies do?
If they are making promises how are they being enforced?
Do consumers get to see exactly what’s being shared between devices?
Can consumers opt for certain devices to not be allowed to talk to each other on their own home networks?
In the case of Apple HomeKit, Will devices still be required be able to to run strictly locally?
(And the other questions that JD Roberts asked above)
Exciting technology, serious concerns about how much say the customer has about what goes on his own network, and what gets reported about him and his family.
I’m in the Data science data mining industry. Seemingly insignificant personal data about individuals enables for making inferences about an individual in a hurry, into an extent that I don’t think most people will be comfortable with if they knew what databases said about them.
PLEASE ASK THEM THE HARD QUESTIONS?
This initiative sounds very promising: one of the major issues with the 100 or so HAN protocols that I found when designing the architecture for BG’s Hive system was that they all had application level concepts in them that didn’t belong in the network stack. This made interoperability impossible. Matter is very similar to the approach that we developed: simplify the devices and manage them in software, use IPv6 as the interface layer and separate out the network/node management from the iot functionality.
They’ll be addressing some of the more egregious testability patterns next (e.g. real-time clocks in devices and bugs that are driven by the clocks over periods of months; qv time injection in all software stacks).
Building on my earlier comment, is there any information yet on how the current application level incompatibilities between ‘data models’ are going to be reconciled?
For instance, will I be able to use a Matter compliant door/window sensor to detect whether a door is open? Currently, some protocols have edge triggered models, others retain information on the current state. The former fail if a message is lost (e.g. while a mesh is reforming), the latter is a drain on batteries.