Slashdot Mirror


Ask Slashdot: Can You Have A Smart Home That's Not 'In The Cloud'?

With the announcement of Google Home on Wednesday, one anonymous Slashdot reader asks a timely question about cloud-based "remote control" services that feed information on your activities into someone else's advertising system: In principle, this should not be the case, but it is in practice. So how hard is it, really, to do 'home automation' without sending all your data to Google, Samsung, or whoever -- just keep it to yourself and share only what you want to share?

How hard would it be, for instance, to hack a Nest thermostat so it talks to a home server rather than Google? Or is there something already out there that would do the same thing as a Nest but without 'the cloud' as part of the requirement? Yes, a standard programmable thermostat does 90% of what a Nest does, but there are certain things that it won't do like respond to your comings and goings at odd hours, or be remotely switchable to a different mode (VPN to your own server from your phone and deal with it locally, perhaps?) Fundamentally, is there a way to get the convenience and not expose my entire life and home to unknown actors who by definition (read the terms of service) do not have my best interest in mind?

Yesterday one tech company asked its readers, "What company do you trust most to always be listening inside your home?" The winner was "nobody", with 63% of the votes -- followed by Google with 16%, and Apple with 13%. (Microsoft scored just 3%, while Amazon scored 2%.) So share your alternatives in the comments. What's the best way to set up home automation without sending data into the cloud?

1 of 183 comments (clear)

  1. Re:MQTT + OpenWRT-router/some other server by JaredOfEuropa · · Score: 4, Interesting

    You can mix & match with the right selection of components. I use the following, and I won't hesitate to recommend it:

    - For generic Home Automation stuff, use Z-Wave: a non-open radio protocol that has proven to be pretty robust. Z-Wave devices form a mesh network so range generally isn't a problem. And with the latest version of the standard, some security has been added as well. There are tons of items out there: switches, dimmers, thermostats, locks, sensors, remotes, and so on, from many brands, in many ranges of prices and quality.

    - You need a Z-Wave hub, and again you have several choices that do not require the cloud: Homeseer (reliable but you get nickle & dimed to death for addons, and it's less accessible to tinkering), Vera (pretty reliable, and best of all it is open to tinkering. You can write your own plugins for this hub and there is an active community of plugin developers), or OpenHAB + a Z-Wave stick (Open! But using it is still somewhat reminiscent of installing Linux in its early days). I am currently using a Vera hub

    - Your hub needs to be able to address non Z-wave devices. Most hubs do this with plugins, allowing you to include these in your setup: WiFi-enabled thermostats, Philips Hue bulbs, Alarm systems, anything networked that has an API, really.

    - For your DYI devices, use Arduino + a NRF24L01 radio module running the MySensors libraries. MySensors is an open DYI project using Arduinos, having them form a reliable mesh radio network (way better than WiFi), and you can build pretty much anything you can imagine with it, usig the libraries and a handful of lines of code. MySensors interfaces nicely with Vera, there's a plugin that will expose MySensors devices like switches and sensors as native Vera devices, allowing you to use them in scenes. For the MySensors gateway to be used with Vera, I recommend using an Ethernet Arduino for maximum reliability.

    Oh, and for anything that needs to be somewhat reliable, avoid WiFi devices. WiFi is not a very good HA platform.

    --
    If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...