4 ms·

Why would you want an open source Nest? Is there a market demand for something which is uglier, harder to use, takes more time to install, and works worse? Do

by codex 13y ago

Why would you want an open source Nest? Is there a market demand for something which is uglier, harder to use, takes more time to install, and works worse? Do you also build your own toasters or automobiles?

post_break 13y ago
Because some people are scared of Google knowing the temperature of your home. But for me, it's the tinkerer inside. I would rather build one of these than buy a nest.
atestu 13y ago
Because it's fun…?
dangrossman 13y ago
I buy connected devices so that I can, well, connect them -- I have a server running that does things like change the temperature on my Nest based on a different brand motion sensor in a different room, or based on voice input on my phone. http://i.imgur.com/8fFkdQ9.jpg http://i.imgur.com/8fFkdQ9.jpg In that dashboard of mine, you see devices from 6 different companies that I've integrated. 3 of them required reverse engineering some kind of website for remote control, even though all that website does is pass on a command from my home network back to my home network. This would break if the website goes down, the website rate limits me, the website blocks my IP, or the website owner decides to sue me under CFAA because their TOS probably didn't authorize remote control outside of their official apps. Nest is one of those websites. There's no official public API. I consider alternatives where I could just talk to the device directly a selling point, and it has nothing to do with privacy. I don't care about Google having my temperature history at all.
- uaygsfdbzf 13y ago
  > I consider alternatives where I could just talk to the device directly a selling point I've had a 3M-branded version of RadioThermostat's CT30 (programmable, wifi, cloud service with Android/iOS apps) for several years, and it has a local JSON API for inquiry and control. Docs: http://www.radiothermostat.com/latestnews.html#advanced http://www.radiothermostat.com/latestnews.html#advanced That's for direct communications on the same local network. It also talks to their cloud service; they haven't published the API for those communications. The thermostat's web control panel does let you enter your own cloud service endpoint, though, if you managed to build a compatible server. You can find people playing with API client code on GitHub by searching for "radiothermostat" or "3m thermostat".

by codex 13y ago

post_break 13y ago

Because some people are scared of Google knowing the temperature of your home. But for me, it's the tinkerer inside. I would rather build one of these than buy a nest.

atestu 13y ago

Because it's fun…?

dangrossman 13y ago

I buy connected devices so that I can, well, connect them -- I have a server running that does things like change the temperature on my Nest based on a different brand motion sensor in a different room, or based on voice input on my phone. http://i.imgur.com/8fFkdQ9.jpg http://i.imgur.com/8fFkdQ9.jpg In that dashboard of mine, you see devices from 6 different companies that I've integrated. 3 of them required reverse engineering some kind of website for remote control, even though all that website does is pass on a command from my home network back to my home network. This would break if the website goes down, the website rate limits me, the website blocks my IP, or the website owner decides to sue me under CFAA because their TOS probably didn't authorize remote control outside of their official apps. Nest is one of those websites. There's no official public API. I consider alternatives where I could just talk to the device directly a selling point, and it has nothing to do with privacy. I don't care about Google having my temperature history at all.

uaygsfdbzf 13y ago
> I consider alternatives where I could just talk to the device directly a selling point I've had a 3M-branded version of RadioThermostat's CT30 (programmable, wifi, cloud service with Android/iOS apps) for several years, and it has a local JSON API for inquiry and control. Docs: http://www.radiothermostat.com/latestnews.html#advanced http://www.radiothermostat.com/latestnews.html#advanced That's for direct communications on the same local network. It also talks to their cloud service; they haven't published the API for those communications. The thermostat's web control panel does let you enter your own cloud service endpoint, though, if you managed to build a compatible server. You can find people playing with API client code on GitHub by searching for "radiothermostat" or "3m thermostat".