this is a good step. i worked in automation/controls (commercial, residential and industrial) for almost a decade (2000-2009) and personally dealt with the nightmare of interop. the number of times i had to glue disparate control systems together with relay closures and switch inputs was insane. and yeah, we had these issues with wireless. it was compounded by the company i worked for supporting enocean, zwave and zigbee.
Amazon, Apple, Google, and the Zigbee Alliance to develop connectivity standard
41–50 of 364 posts
Re: Amazon, Apple, Google, and the Zigbee Alliance to develop connectivity standard
#42[deleted]
Re: Amazon, Apple, Google, and the Zigbee Alliance to develop connectivity standard
#43Why not openthread? It's already there, it's open source, and from my somewhat limited experience, works well.
Openthread is purely a networking solution. It does not address application-layer messaging. This effort is to unify the application layer. (ie, "light = on" messages).
Re: Amazon, Apple, Google, and the Zigbee Alliance to develop connectivity standard
#44> The goal of the Connected Home over IP project is to simplify development for manufacturers... > The industry working group will take an open-source approach for the development and implementation of a new, unified connectivity protocol and increase compatibility for consumers. Curious if I as a hobbyist will benefit from this? Or if this will become a: it works perfectly, but only if all your devices connect to ou…
Perhaps. The Phillips Hue lights use an open standard, I bought a usb device that could talk it (ZigBee Light Link) but then it turned out that production devices used a master key.
Here's a discussion of the master key being leaked:
https://news.ycombinator.com/item?id=9249753
But I looked it it before that and never tried to look it up again.
So likely so, and with today's encryption it probably won't get hacked for hobbyists to use/learn/play but of course I guess the argument is that the Hue Bridge and other devices will have an API.
Re: Amazon, Apple, Google, and the Zigbee Alliance to develop connectivity standard
#45How will this relate to 6lowpan, the already existing IP standard for IoT? Or will CHoIP sit on higher level (like eg mqtt)?
6lowpan only addresses running IPv6 over 802.15.4 PHYs. It defines how to compress IPv6 headers to fit into 802.15.4 MTUs.
CHoIP will define application-layer messaging that runs over IP, regardless of PHY.
So, you can run CHoIP over 6lowpan (this is essentially what CHoIP on Thread would be).
Re: Amazon, Apple, Google, and the Zigbee Alliance to develop connectivity standard
#46I am curious if they will include cameras (security / door), because the characteristics of the payload are quite orthogonal to the characteristics of the payload of other smart home devices.
>because the characteristics of the payload are quite orthogonal to the characteristics of the payload of other smart home devices. how so?
Lights and switches are generally basic async polling and commands versus live streaming video and constant video uploading to a cloud storage service.
Re: Amazon, Apple, Google, and the Zigbee Alliance to develop connectivity standard
#47I am curious if they will include cameras (security / door), because the characteristics of the payload are quite orthogonal to the characteristics of the payload of other smart home devices.
I doubt some of they PHYs have the bandwidth to support streaming video, but there have been some good efforts in the IETF to maximize streaming protocols over low-bandwidth connections.
But the whole point of CHoIP is that PHY doesn't matter, so you can configure your camera using IP messages over BLE, and then the camera connects to services over WiFi to stream.
Re: Amazon, Apple, Google, and the Zigbee Alliance to develop connectivity standard
#48Earlier quoted context omitted.
Consume IP addresses? There are a bazillion IP addresses. Or are you stuck on IPv4?
I'm on IPV4. It's not about how many IP addresses I have available, it's that all those smart devices can pollute the list of devices connected my wifi network. I like to know what's on my wifi network, and because my memory isn't what it's used to be, I find myself having to assign names to all the smart wifi devices in my Unifi controller.
A common solution (and one HomeKit enabled routers implement) is to relegate all IoT products to their own network
Re: Amazon, Apple, Google, and the Zigbee Alliance to develop connectivity standard
#49Smart home is the poster child for "The good thing about standards is there are so many to choose from."
Randall gets it [1].
Re: Amazon, Apple, Google, and the Zigbee Alliance to develop connectivity standard
#50> The goal of the Connected Home over IP project is to simplify development for manufacturers... > The industry working group will take an open-source approach for the development and implementation of a new, unified connectivity protocol and increase compatibility for consumers. Curious if I as a hobbyist will benefit from this? Or if this will become a: it works perfectly, but only if all your devices connect to ou…
My guess: first of all, "for security reasons" your DIY device will need to be certified, any existing SBCs will need to be replaced/extended to support new type of network and due to bloated protocol specs with a myriad of abstraction levels will render it almost impossible to implement it on your own and the open source library that can do that will implement the standard as specified whereas all proprietary solutions will have some quirks and little differences from official standard making it very hard to connect to anything from your open source lib. Also the sophistication of the new standard will exceed the capabilities of any arduino forcing you to replace any boards you have with new ones that have AVR uc with Connected Home hardware support.