The Zigbee Alliance this week offered — nine months after announcing it was forthcoming — an update on Project Connected Home over IP, an effort by Apple, Amazon, Google, Samsung, and others to create some kind of interoperability standard for the smart home. There are A LOT of cooks in this kitchen, with 145 separate companies and more than 1,300 individuals signed working on CHIP. It is a titanic effort.
The good news is that the standard is still on track, with a certification coming later this year and actual certified products anticipated in 2021. The Alliance also provided a list of devices that CHIP will focus on; it includes lighting, HVAC, locks, security, shades, and more, but neither smart speakers nor white goods, such as large appliances. And to round things out, it offered a GitHub repository and a detailed look at some of the levels where CHIP will seek standardization. But in many ways, the update was disappointing.
It was disappointing because CHIP represents such a huge shift in thinking about the smart home, one that could have incredibly important repercussions for the brands building connected devices. They want to know how things will work and what to expect, and they want to know as soon as possible because they still need to get products out the door. Even consumers aren’t sure if they should buy new gear or wait for CHIP.
In the meantime, developers are wondering how they should design their products and outfit their electronics to handle the inevitable updates. Indeed, based on my panel discussion during Silicon Labs’ Works With conference on Wednesday, I think most companies are participating in the CHIP groups so as to ensure their older devices aren’t rendered obsolete and that devices in development will continue to work with minimal changes.
But there are no guarantees. For example, none of the participants on the panel — which had representatives from Assa Abloy, IKEA, Philips Hue, and ADT — knew how CHIP might handle device provisioning or backward compatibility. So I thought it might be worth compiling a list of things we don’t know about CHIP. This list includes questions I had sent to the Zigbee Alliance all the way back in April and others I had sent ahead of the panel discussion with the hopes of getting an answer at the event.
The Alliance has answered a lot of the questions, especially those around timing and what the project plans to cover. But there are a few unknowns still out there.
So here are most of the questions I’ve posed to the group, and where possible, the answers I’ve been able to glean from the Github repository and various panels that have included CHIP members.
There is some real momentum here. During the Works With panel, Sujata Neidig, who is the head of marketing at NXP and represented Project CHIP, said we should see a draft by the end of this year and products in the market by this time next year. As for developer resources, Google showed off an example app using CHIP over Thread (it’s at 1:33 in the video), which was pulled from the Github repository. A spokeswoman for the Zigbee Alliance says that developers should look to their silicon partners for information about resources and dev boards.
The more detailed stack diagram shared in the Github repository answers some of those questions. It’s clear that CHIP will have security elements, frameworks for the aforementioned device types, and what I think are pre-configured ways for devices to interact with each other (see the interaction model actions noted in the diagram). There will clearly be some rules on how devices communicate, but what those will be remains unclear. The panelists said they expect CHIP to outline a common way to get devices onto a network, but didn’t say how that might happen. During a demonstration by Google of a CHIP device getting added to a home network, the device was discovered and labeled (incorrectly in the demo) by a Google Hub Max and then the user entered a PIN code to add the device to the network.
We don’t yet have an answer to that question.
That is another question that we don’t know the answer to yet.
Based on the stack diagram and the fact that the CHIP news this week included bridges as a device type that the group will focus on, local communication could still happen and is likely, but it’s unclear if CHIP plans to address cloud-to-cloud interactions.
To be sure, smart speakers aren’t even a device type that the project lists as a focus area. Regardless, its perspective is important here, but it hasn’t offered that yet.
Even on the panel, participants in the project didn’t have answers to those questions, although they obviously hoped their existing gear would still work with a software update as opposed to having to physically replace their devices.
We don’t have guidance around this yet. Notably, developers in the chat associated with the Works With event were also curious about this.
Also unclear.
Samantha Fein Osborne, the director of global marketing at Samsung SmartThings who also heads up the Project CHIP marketing committee, told me “CHIP is an acronym and its a working name,” which leads me to think that we’ll see something different and more permanent for the standard and formal certification.
Unclear, but as someone who is so bad at branding (I have two web sites and two brands associated with a media business run by one person), even I think a separation should happen at some point.
So, we actually know a lot more today than we did in December — or even back in April, when I last wrote about Project CHIP in depth. But there’s still plenty more to wonder about.
This is the final episode of The Internet of Things Podcast, and to send us…
This article was originally published in my weekly IoT newsletter on Friday August 18, 2023.…
This article was originally published in my weekly IoT newsletter on Friday August 18, 2023.…
Verdigris has raised $10M for smarter buildings: I am so excited by this news, because roughly eight…
Amazon's head of devices, David Limp, plans to retire as part of a wave of executives that…
If you need any more indication that Matter is not going to kill all of…