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

Original Article ↗ Hacker News Discussion ↗

What’s Being Ended and What Still Works

  • Google is ending app/API support for Nest 1st/2nd gen thermostats; they will still function as standalone thermostats.
  • On-device scheduling and “learning” modes reportedly continue, but mobile apps, Home app control, and third‑party integrations (e.g. Home Assistant, utility programs) will stop working.
  • Some see this as “not mass bricking,” others say losing remote/app control is effectively losing the core value they paid for.

Trust, Lifetimes, and Google’s Reputation

  • Strong sentiment that Google kills too many products; multiple commenters say this is the last straw for buying any Google hardware or depending on Google services.
  • Debate over expected support duration:
    • Some argue 20–30+ years is reasonable for a thermostat tied to a home and HVAC that can last decades.
    • Others counter that buyers got ~10–14 years, which they view as acceptable for a complex connected device.
  • Several call for regulation: minimum advertised support lifetimes, or mandatory release of keys/APIs/firmware when cloud support ends, to avoid e‑waste.
  • A minority argues Google’s only obligation is to shareholders and that minimal support until it’s legally safe is “normal business.”

Cloud vs Local: Design and Business Models

  • Thread-wide “lesson”: avoid IoT devices that require a vendor cloud and don’t offer local or self-hosted control.
  • Complaints that almost all “smart” gear routes LAN‑to‑LAN control through remote servers and logins, often justified under “security” or account UX.
  • Others tie cloud-dependence to VC‑style subscription valuation and forced upgrade incentives, not technical necessity.
  • One former early Nest engineer notes that adding secure local APIs or modern protocols to 2010-era Linux devices is non-trivial, but many still argue Google could at least keep basic cloud endpoints up or expose a simple local API.

Alternatives and Local-First Setups

  • Many recommend Ecobee, though it also has cloud/API quirks; praise for HomeKit mode and open-source tools (e.g. beetstat) for history/analytics.
  • Other suggested options: Z‑Wave/Zigbee thermostats with Home Assistant, Honeywell Z‑Wave and T6, Sinopé, Venstar (documented local JSON API), cheap Zigbee/Z‑Wave units from AliExpress, Insteon, Amazon’s thermostat.
  • Repeated advice: favor devices with:
    • Local protocols (Z‑Wave, Zigbee, Matter, HomeKit, LAN APIs).
    • Optional or no cloud; no forced OTA; ideally hackable/3rd‑party firmware (e.g. Tasmota).
    • Integration with Home Assistant and isolation on dedicated VLANs.

“Smart” vs “Dumb” Thermostats

  • Pro‑smart arguments: remote control when traveling, pre‑heating/cooling before returning home, using remote sensors, handling system thermal lag, better UI than legacy programmable units.
  • Anti‑smart or skeptical views: old mechanical or simple digital thermostats last 30–50+ years, are cheap, reliable, and not hostage to corporate decisions; many “smart” features (learning, AI) are seen as gimmicky or annoying.

Hacking and Community Rescue

  • Mention of other ecosystems rescued by open source (e.g., Squeezebox/Lyrion, Tasmota), and calls for similar openness from Google.
  • One commenter is building an open-source replacement PCB for Nest 2nd gen using ESP32‑C6, reusing the existing enclosure and integrating with Home Assistant, as a way to keep the hardware useful after Google’s cutoff.