This isn’t even just automation by the way. On Alexa every time a smarthome device is accessed it has to go through the internet (with the one exception being Hue lights, because that came out before all of this other mainstream IoT home automation crap). There was one time when the company who makes my z-wave bridge had a server problem and I couldn’t use Alexa to control anything in my house for a week. If a company that makes one of your devices goes out of business or shuts off their servers that device will stop working with Alexa permanently.What I like about HomeKit automation is that it’s controlled on a device in your house (AppleTV, iPad, and now HomePod).
While I’m a little frustrated at the rate Apple is adding new automation features (with each major iOS release), I do like that HomeKit automation isn’t dependent on someone’s server on the internet (IFTTT) to function.
Not that my internet goes down a lot, but it’s nice to know that my HomeKit automation jobs will run if it does.
But yeah, until HomeKit matures a bit more, I have a primary controller that I use for my more complex automations. Not that they’re truly complex, but today’s HomeKit can’t do them.
Not to mention any security issues that could crop up because for example your front door lock HAS to be accessible by an API in the cloud somewhere for it to work with Echo.
This is part of the reason I say HomeKit is more advanced, it accesses everything locally with only one conduit to the outside world being controlled and secured by Apple. And if you don’t care about remote access you don’t even need that. It’s just a more secure and well thought out system from the ground up.
Last edited: