All my IoT devices are in a wifi without any internet access.
More like 'WLoT' (Wireless LAN of things)
That's pretty much all I want from home automation as well. I see the value in being able to say "Alexa, turn down the lights" and having AWS do the voice recognition - but given that I can't trust services to stay more than a few years, I'm not going to invest in it.
Apple sells Apple Home Hub, I wonder if that's their "central control system" so that the Apple Home devices can be a bit dumber, but also it means there's a central firewall and system that can look for updates.
Also if you can install the "cloud-end" on your own device, when the company goes Nest, it means you can at least run an old version to keep your "IoT" gadget running, and it'll be running on the (hopefully) firewalled local hub.
Apple doesn't sell a "home hub" product. But their smart speaker (HomePod), TV set top box (Apple TV) and tablets (iPad) can all function as a gateway for HomeKit devices to be securely controlled from outside the LAN without the devices themselves having to be very smart or secure.
Totally feasible to make a killer wireless AP that's Apple branded and connects better to the ecosystem, but that doesn't seem to be the direction Apple is going.
It's a shame they stopped investing in them and missing the whole mesh Wi-Fi development. Also in this age where they're touting "privacy first" and iTunes is on the endangered list, not supporting iOS device backups over a LAN is a huge deficiency.
The management solution in my home is OpenHab2, but Home Assistant also works fine.
https://www.home-assistant.io/components/ https://www.openhab.org/addons/
There are a few other products I use (for blinds, windows, heat), but you can often simply search the above two lists and read through the documentation whether they need internet (or "cloud") access or whether theyre totally local.
I personally prefer OpenHAB over HomeAssistant, but the thing that annoys me about OpenHAB2 is that it doesn't have even rudimentary built in user management with authentication. The docs basically tell you to use something like Nginx to do that for you.
if you want a super simple setup, they have manual guides for setting it up. And if you just want remote access and don't need Alexa/Google integration, it almost as simple manually.
It's the opposite of interchangeable.
It's true that they're mostly proprietary, and Apple runs its own services, and I hate iTunes these days.
But—and I realize not everyone feels the same way—but at this time they are literally the only b2c company that has any credibility around privacy.
They feel to me—and again, not everyone agrees—they feel to me like the only hardware company that thinks of their users as their customers, and not as cattle to be sold to crapware vendors and search engine behemoths.
I can think of a few: Purism, System76, OSMC, Mycroft... they're smaller and less well-known than the big players of course, and they're not all perfect, but they treat their users as customers unlike many companies these days.
Busy at work, but when I have a chance I'm going to do some DuckDuckGo-ing of these names.
And since were mentioning smaller but still highly useful vendors who treat their users with respect, DuckDuckGo.
Right now Apple makes buckets of cash from their hardware, but if they ever need to tighten their belt you can bet that the extra revenue from selling your data will be extremely tempting.
My A/C is on Wifi though, and the cloudy controller web page is using a REST API (undocumented but simple enough to sniff and fake), so that's the only outlier so far.
Even if I wanted to pay a subscription fee to some external service for my hub, the risk of service disruption, hacking of my network, and/or misappropriation of my personal data are just too high.
I'll have to give Node-RED a go once I find some spare time to tinker.
Remember when built in intercom systems in the home were considered advanced?
http://mentalfloss.com/article/510559/what-smart-home-techno...
Dunno. Maybe. But for me to be interested in something it still has to be something that is going to pay back my fiddling in probably ten years, where I can expect to have to replace it, and I'm still not impressed by any of the the demos I've seen. I'm just not that inconvenienced by having to turn on lights.
I think everyone is getting at least 20 years out of their Ethernet connections, likely more. That's not as durable as electical cables but good enough for most cases (plenty of things need updates after 20 years in a building).
- digital currencies
- smartwatches
- smart homes (Bill gates had his house 'smart homed' to the wazoo with tens of NT servers taking care of everything, like switching lights on and off)
- food delivery startups Webvan, Kozmo,
- livestreaming (JenniCam)
1) Go with a cloud service using products exclusively made by a single major company, like Google or Amazon. This is simpler to setup and maintain but more expensive.
2) Go with an open source solution, like Home Assistant. Cheaper option with more control but requires a lot of time to learn, setup and maintain.
Both options should be considered safe at this point.
Edit: added emphasis on "made by" since many were missing that nuance. Buying a single brand of HA from a single company should be considered safe.
I'm not talking about buying compatible devices made by other manufacturers, this API issue shows is that isn't safe.
And in this case, Google just gave all their customers using the Nest API the finger. How is it safe to trust them going forward?
Get open source hardware and software that you can maintain yourself or suck it up and cough up the dough.
Making any company a single point of failure is a bad idea. You are basically giving up your freedom of choice for maybe some convenience, but don't confuse it with guarantee of sustained service.
IMO buying any hardware tied to a SaaS is a dumb idea.
You mean like Nest? Not a good example.
Better advice is buying something non-cloud based which uses established standards and which works entirely within your LAN.
If the company goes down, at least you can interact with the devices using the standards they were built on (Zigbee, z-wave, etc).
Reread my original comment. I say you'd be safe if you buy products made BY a single company. This API effects those who bought things that are made by other manufacturers.
3) Find a local home automation company and look at their offerings. There's a chance you'll find people willing to sell you actual products that are optionally Internet-connected, but not Internet-first, and are not tied to a garbage SaaS. They'll install and service them for you too. Key words here are "home automation"; I find looking for this phrase instead of "IoT" to weed out a lot of garbage.
They're firewalled to my LAN and integrated into iOS using Homebridge running on my Synology NAS.