←back to thread

Nest 1st gen and 2nd gen thermostats no longer supported from Oct 25

(community.hubitat.com)
280 points RyanShook | 6 comments | 05 Sep 25 21:33 UTC | HN request time: 1.048s | source | bottom
1. RyanShook ◴[05 Sep 25 23:42 UTC] No.45145024[source]▶
Can someone at Google explain why the company can’t end formal support for the thermostat but make the API open? It’s a thermostat. It has 3 real functions - cool, heat, fan. What could it possibly hurt to let owners access the endpoints without touching Google servers?
replies(3): >>45145121 #>>45145545 #>>45157917 #
2. asdff ◴[05 Sep 25 23:57 UTC] No.45145121[source]▶
But then the customer might not buy a new nest....
replies(1): >>45147735 #
3. Uvix ◴[06 Sep 25 00:56 UTC] No.45145545[source]▶
This assumes Google's servers are pushing to the thermostat. It seems more likely that the thermostats are pulling from Google's servers, so that they don't have to worry about firewalls.
4. nasretdinov ◴[06 Sep 25 09:04 UTC] No.45147735[source]▶
They might not buy a new one regardless because they are upset with the company :). Just saying
replies(1): >>45153379 #
5. ◴[06 Sep 25 22:15 UTC] No.45153379{3}[source]▶
6. fastest963 ◴[07 Sep 25 13:18 UTC] No.45157917[source]▶
With a big company like Google I'm sure lawyers are the ones preventing an open API and not the developers. The API is a liability for Google. It could infringe on patents or it could have a bug.