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

I got burned recently by Ecobee in the same way. The problem with 'smart' interfaces for traditionally mechanical devices is that the useable lifetime (support period) of low-end microprocessors and software, especially online APIs, is often far shorter than the mechanical device it's attached to.

Similar to how people that keep cars around for 10+ years are stuck with dated and worthless 'infotainment' systems, Google and Ecobee can't even honor their product for long enough to outlast the HVAC units.

What burns me is that it wouldn't be much of an ask for them to push one final (optional) update that would open LAN-only access to core functionality. I and many others in the HA/ESPHome community have written hardware integrations to devices over RS485/UART with unpublished/black-box protocols, so a simple HTTP API would have an integration within days.

It would maybe cost an engineer at Nest/Ecobee a day or two of work, and the goodwill would make me far more likely to purchase a newer model. As it is, I've committed to avoiding (where possible) devices that aren't local-first.

If your car is old enough to have a standard DIN radio, you can easily replace it with a modern CarPlay/Android Auto unit. And cars that are new enough to have CarPlay/Android Auto built in seem to be generally holding up. It’s really just cars from a specific window (after they started putting nav systems and screens, before adopting CarPlay) that age really badly.