3 ms·

I don't trust advertising companies with more intimate data about things inside my home. A phone and computers is bad enough. Fortunately there's a good solutio

I don't trust advertising companies with more intimate data about things inside my home. A phone and computers is bad enough. Fortunately there's a good solution for me (today) and for everyone (hopefully soon). Home Assistant [1] has been a Github-topping repo for a while. You've seen it here on HN several times [2]. It's a Python 3 open-source home automation platform that runs on a Raspberry Pi or other home server. Local data, local control. It's been being bootstrapped by tinkerers who can handle YAML config files for a while but is getting much fancier these days. When Google shut down Revolv hubs in 2016, they posted rationale about why your hub should be open and local [3]. This kind of move further justifies the argument. As big companies clamor over access to your home, let's take a stand by demanding open standards, local data options, and local control. [1] https://www.home-assistant.io/ https://www.home-assistant.io/ [2] https://news.ycombinator.com/item?id=15521743 https://news.ycombinator.com/item?id=15521743 [3] https://www.home-assistant.io/blog/2016/04/05/your-hub-should-be-local-and-open/ https://www.home-assistant.io/blog/2016/04/05/your-hub-shoul... [4] https://www.home-assistant.io/blog/2018/09/17/thinking-big/ https://www.home-assistant.io/blog/2018/09/17/thinking-big/

joelhaasnoot 7y ago
One of the tough things about open source software and especially HomeAssistant (long time user here!) is that HomeAssistant connects to many services, a lot of which use some sort of oAuth protocol, which in turn requires a client key/client secret, which can't be embedded in the software. For Nest, it requires every installation/user to create a new key/application with Nest/Google, for what in many ways is the same software. There must be a better way - in the end all that's being given back is a client key which is used in the actual authentication.
- mindslight 7y ago
  Another way of looking at it is that the problem is better attributed to OAuth / centralized web services. Nest/Google is responsible for making you go through that developer rigmarole to simply use your device. Next time, choose hardware with a better user experience! Both perspectives have their validity of course. Your description is more applicable to someone interested in moving to Home Assistant after already having bought a bunch of proprietary devices. These network effects are exactly why it's so damn important that open protocols and projects are adopted and become standard, rather than these dead end "service" worlds of Google et al.
hanklazard 7y ago
100%. I’ve also been using HA for a while now and have been very impressed. Tons of integrations including a number of z-wave and WiFi thermostats — so you don’t have to bother with this Nest / Google nonsense if you don’t want to. As HA approaches version 1.0, I hope more people will jump onboard.

joelhaasnoot 7y ago

One of the tough things about open source software and especially HomeAssistant (long time user here!) is that HomeAssistant connects to many services, a lot of which use some sort of oAuth protocol, which in turn requires a client key/client secret, which can't be embedded in the software. For Nest, it requires every installation/user to create a new key/application with Nest/Google, for what in many ways is the same software. There must be a better way - in the end all that's being given back is a client key which is used in the actual authentication.

mindslight 7y ago
Another way of looking at it is that the problem is better attributed to OAuth / centralized web services. Nest/Google is responsible for making you go through that developer rigmarole to simply use your device. Next time, choose hardware with a better user experience! Both perspectives have their validity of course. Your description is more applicable to someone interested in moving to Home Assistant after already having bought a bunch of proprietary devices. These network effects are exactly why it's so damn important that open protocols and projects are adopted and become standard, rather than these dead end "service" worlds of Google et al.

hanklazard 7y ago

100%. I’ve also been using HA for a while now and have been very impressed. Tons of integrations including a number of z-wave and WiFi thermostats — so you don’t have to bother with this Nest / Google nonsense if you don’t want to. As HA approaches version 1.0, I hope more people will jump onboard.