In reference to Ecobee’s latest product release, the Ecobee Lite, I came across this little snippet regarding Apple’s HomeKit:
But nowhere in its marketing materials is Apple’s HomeKit mentioned, despite the extra effort and cost the company has to go to in order to work with the system.Source: HomeKit is where the dearth is – no one wants Apple’s IoT tech • The Register
It would take far too much time and effort to try and counterpoint what I’m seeing as a trend of articles dismissing Apple’s HomeKit platform. That is not a battle I want to get into at the moment, but in seeing the line I quoted above, I decided to go take a look on Ecobee’s website to see about a lack of HomeKit branding:
I’m truly not trying to be facetious, but I’m seeing HomeKit prominently mentioned on their website, which to me, is the marketing material most people will be coming across when doing their homework. Did they add it after the article was written? Does the UK see a different site than we do here in the US?
“And it’s not compatible with Thread or ZigBee or Z-Wave,” Hemphill adds. But even more damningly, he says that literally none of his customers are asking about it.
I’m working on a HomeKit integration for a large home automation product company and their customers are asking for it, which is why they are integrating it. What are his customers asking about? Thread, a wireless mesh networking protocol?
Consumers new to home automation don’t know any of the standards he just listed out, but if you are an Apple user, it is becoming more likely you will have heard about HomeKit. In the long run, Apple user’s will ask and know something about HomeKit and Android user’s will come to learn and ask about Google Weave (a.k.a Nest Weave), once Google releases their full IoT platform into the wild.
And that’s because right now, you can go buy products that work and are cheap and don’t need HomeKit. All the big names on Apple’s list of certified products – from Ecobee and Honeywell thermostats to August and Schlage door locks – work perfectly well without HomeKit.
Cheap means not secure to my ears.
And they will all work with the larger IoT ecosystem once the industry figures out how to start working with one another.
So if you are a company with a very large user base, a lot of capital, a focus on privacy and security, a vast ecosystem of proprietary hardware and software, you should not implement something proprietary and secure but should wait until the industry figures out how to work with one another?
I just can’t get on board with that logic.