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?
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.
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.
I was hoping that at least my Home Assistant integration would keep working. That sucks terribly. Lesson of the day: Avoid any IoT device that you can't use without an external service.
FWIW, I replaced my Nests with Centralite Pearls a few years ago, and have been extremely happy with them WRT Home Assistant. The Pearl doesn't seem to be widely available anymore, but any Zwave or Zigbee thermostat + a local hub gets you a thermostat that should work with Home Assistant and will be immune to being sunsetted like this.
It’s great that it avoids pay-per-token pricing and is very powerful. The downside is right now it decides what to do and executes with very little guidance or guardrails. You basically have to shout at it or force quit to make it stop executing commands.
Its a standard practice for third party keyboards on iOS, I doubt you'll find any keyboards worth using that don't request full access. Otherwise Apple cripples the experience a lot.
Thank you for checking the app out! Ah that's too bad :(
I don't collect any data and the app only connects to the internet at launch (to check subscription status) and when you use the dictionary feature. You can choose not to allow full access and still use quite a few features!