logo elektroda
logo elektroda
X
logo elektroda

Google ends support for Nest Learning Thermostat (1st and 2nd generation) - from 25 October 2025

p.kaczmarek2 420 4
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
📢 Listen (AI):
  • Nest thermostat with blue display set to cooling at 75°F
    Google has announced the end of support for older models of the Nest Learning series of thermostats. From 25 October 2025, these devices will no longer connect to Google Nest or Google Home apps. This means that equipment advertised as smart will suddenly lose much of its functionality and disappear from the app panel itself.

    This applies to the Nest Learning Thermostat 1st gen (2011), 2nd gen (2012), and 2nd gen EU (2014) models.

    What exactly will happen to the thermostats?
    - The thermostat will be disconnected from the app and removed from your account.
    - You will not be able to control it remotely, check status or receive notifications.
    - Integrations with assistants and features such as Home/Away Assist will stop working.
    - Nest Protect will no longer work with the thermostat (no emergency shutdown).

    The device will continue to operate locally: control directly on the thermostat, support for schedules and temperature modes, access to settings available on the device itself. However, software and security updates will no longer be made available, which may affect long-term functionality.

    Source: https://support.google.com/googlenest/answer/16233096

    And what are the comments from users?
    https://news.ycombinator.com/item?id=45147385

    1. Preference for thermostats that are compatible with local automation - many users appreciate devices that work with Home Assistant and ZigBee/Z-Wave, highlighting that this increases independence from cloud-based services and makes them independent of manufacturers' decisions.
    2. growing reliance on open-source solutions - some point out that they are developing open-source versions of Nest thermostats themselves, continuing the life of the hardware with local software and without dependence on Google.
    3. Outrage at the manufacturer's decision - frustration towards Google/Nest is strong as users feel let down by the withdrawal of support, although the hardware technically still works.
    4. Profitability of advanced thermostats - some people feel that it is not at all necessary to overpay for 'smart' hardware with a closed cloud infrastructure when a solid cheap thermostat can last decades without issue.
    5. difficulty in finding durable and locally-enabled products - users complain that it is difficult to find devices that offer a modern user interface and at the same time work without internet connectivity.
    6) Growing consumer awareness - more and more people admit that when buying smart appliances, they are starting to choose those that can be connected to Home Assistant and are independent of remote services.
    7. Confidence in brands such as Honeywell and Reolink - there is an emerging recognition that it is worth investing in equipment from manufacturers that offer local control and do not make the user dependent on subscriptions or the cloud.
    8. Practical concerns about the future of equipment - users note that equipment ceases to be 'smart' once support leaves and local operation becomes a key feature for longer life.
    9. Frequent comparisons to ordinary 'dumb' thermostats - some argue that a traditional, reliable mechanical thermostat can last for generations, putting current digital products in an unfavourable light.
    10. Encouragement of changes to the IoT business model - comments suggest that the technology company should allow the user to manage the device locally even after support ends, rather than forcing the user to buy new hardware.

    My comment: here we have the typical problem of subscriptions and cloud services. The customer supposedly 'buys' the product outright, but the manufacturer can still disable or functionally restrict it at any time. In practice, this is acquiring the rights to use the hardware while remaining at the mercy of the manufacturer, who may deliberately restrict older product series to sell more newer copies. Most users don't give it a second thought, but in effect hand over control of their own device to a corporation. So instead of actual ownership, we have a kind of lease with unclear terms, where a software update can introduce restrictions instead of improvements, and the end of support becomes an excuse for 'forced' hardware replacement. This leads not only to additional costs for the user, but also to waste and faster product obsolescence. For this reason, I recommend buying products that at least give some sort of local control option, completely without the cloud.

    Information about the Nest thermostat range: https://en.wikipedia.org/wiki/Nest_Thermostat
    Source of title image: https://en.wikipedia.org/wiki/Nest_Thermostat#/media/File:Nest_front_official.png (Public Domain)

    Cool? Ranking DIY
    Helpful post? Buy me a coffee.
    About Author
    p.kaczmarek2
    Moderator Smart Home
    Offline 
    p.kaczmarek2 wrote 12728 posts with rating 10551, helped 593 times. Been with us since 2014 year.
  • ADVERTISEMENT
  • #2 21655572
    pikarel
    Level 39  
    I fully agree with the opinion of my colleague @p.kaczmarek2.
    It's a good thing that my gas boiler, which is 25 years old, has a thermostat on the knob and I only occasionally clean the thermocouple of carbon build-up by applying a brass brush to it.

    The big-business jerks are not in short supply; after a little 'mint' they reveled in the goggles.
    And what will you do?
    You will do nothing.
    :) .
  • ADVERTISEMENT
  • #3 21656220
    DJ_KLIMA
    Level 25  
    And that's how you make $, good but not too cool. To make it cool, buy new, it'll be cool, but you don't know how long it'll be cool.
  • ADVERTISEMENT
  • #4 21656470
    Erbit
    Level 38  
    I have had home automation for over 10 years. Among the company devices, I have devices like Sonoff with Tasmota software preloaded. All the automation components (and I have close to 200 of them) work locally. This makes me independent of the whims of the manufacturers. Many of the Sonoff components have 'outdated software' but I don't feel the need to upgrade because 'everything works'.

    From the very beginning, I have relied on independence. The only 'drawback' of this solution is that if I want to switch something on while I am away from home, I have to set up a VPN tunnel first. This is a few extra clicks.

    For the same reason I created the "Gervase" project - a module for voice communication. Unfortunately, in this case the engines converting speech to text installed locally are not yet efficient and too demanding in terms of hardware, so I used external engines. However, the project has never been completed and is not usable. Sometimes I turn it on "for fun" when I want to show something to the children.
  • #5 21687089
    aadeer
    Level 16  
    DJ_KLIMA wrote:
    And that's how $ is made, good but not too cool. To make it cool, buy new, it'll be cool, but not sure how long it'll be cool.

    Somewhere in the smart home topics there were a lot of complaints about Matter, including I think @p.kaczmarek2 . But it could be a solution. The disadvantage is the lack of flashing - probably some EU law, I haven't delved into that yet - either it's the new directives or the radio.

    But on the other hand - assuming everything will be in one standard, then without playing around with tasmots or esp-home (I have a few things on it, still sonoff products on ESP8266), matching names, addresses you will be able to connect such a device from the market immediately to your network/hub. It doesn't need to be connected to the internet and dependent on the cloud, just a few rules on the router to control it and that's it...

    What annoys me at the moment is the situation with PV inverters, recuperators, furnaces. Each device would want internet access, communication via the manufacturer's cloud and yet a separate app for each.

    Erbit wrote:
    locally installed speech-to-text engines are still not very powerful and too demanding in terms of hardware, so I used external engines.
    .

    This was the case, say, 2 years ago. Check out the Whisper model from OpenAI. I have a note-taking system made on it, I send a voice message (admittedly via Telegram, about which opinions vary), the note falls into a folder on my home server already in text form....
📢 Listen (AI):
ADVERTISEMENT