Nest 1st Gen and 2nd Gen Thermostats No Longer Supported From Oct 25
Posted4 months agoActive4 months ago
community.hubitat.comTechstoryHigh profile
heatednegative
Debate
80/100
IOTSmart HomeGoogle Nest
Key topics
IOT
Smart Home
Google Nest
Google is ending support for 1st and 2nd gen Nest thermostats, sparking frustration among users about the lack of long-term support for 'smart' devices and the implications for IoT security and sustainability.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
3m
Peak period
110
0-3h
Avg / period
13.3
Comment distribution160 data points
Loading chart...
Based on 160 loaded comments
Key moments
- 01Story posted
Sep 5, 2025 at 5:33 PM EDT
4 months ago
Step 01 - 02First comment
Sep 5, 2025 at 5:36 PM EDT
3m after posting
Step 02 - 03Peak activity
110 comments in 0-3h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 7, 2025 at 6:20 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45143879Type: storyLast synced: 11/20/2025, 8:23:06 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Since it's Homekit compatible though, you can go that route. HA easily discovers anything HK compatible as soon as you connect it to your network. So you connect Ecobee to HA with the HomeKit protocol in lieu of connecting it with Apple's stuff.
[1] ...and anything's better than the asinine on-device UI that Ecobee "updated" to a couple years ago (ask yourself: what would a foolish inexperienced "uX dEsIgNeR" do to ruin a plain old thermostat UI? It's that.)
Of course the app stops working, but that’s expected from a WiFi product.
Thankfully the open source beetstat makes ecobee a lot more useful, with full history and graphs for heat/cool runtime, aux heat, indoor/outdoor humdity, etc
at least they dont seem to be planning a mass bricking.
But yes, this is why I'm staying away from Gemini. Seems like an amazing product! But no way am I putting my AI eggs in the Google basket.
Yes it was an unfortunate autocorrect and it’s now too late to fix it!
The day the kill that, is the day a new hell is trust upon you.
As it were, appreciate the life you have right now that AI doesn’t have ads, it’s coming.
https://news.ycombinator.com/item?id=45141343
That’s just today’s nonsense tacked on to tomorrow’s tool.
I’m talking about Apple and OpenAI having all your context and an ads-baked-in system where you work out hard on Thursday and on Friday as you are passing by a advertising-buyer ice cream shop that your phone tells you that you earned whatever flavor it knows you like.
https://www.youtube.com/watch?v=4Z4RKRLaSug
So for the owners of Gen 1 and 2 thermostats, your rule of thumb isn’t helpful like it is for post 2014 purchases.
Not really. The BOM of a smart thermostat is nearly equal to a dumb one right now. What adds cost is reliability. Hardware reliability costs engineering time and expensive component choices. Software reliability requires engineering resources and a mindset beyond optimizing quarterly returns.
There is no legitimate reason a fancy thermostat should be e-waste after ten years.
I wish the internet of things was soo much better than it is. There was a dream once of a world that worked efficiently, and then profit models came in and destroyed it.
I guess it would be cute to get some analytics dashboard, but that’s about where my interest ends.
Adjusting the thermostat (which is downstairs) from bed.
At the airport - oh shit did I turn off the AC for the two weeks we'll be away? Ok I just did.
I am a HA guy and prior to my ecobee I ran an American Radio Thermostat with local HA support and you could control over curl. But the wifi module was so old that no modern device connected to it when I had to reset it up.
But I agree zwave plus HA are a great option too.
That said, I'm quite annoyed that Google is nuking my perfectly functional thermostat, and I will be buying an Ecobee to replace it, and integrating it with home assistant.
Convenience and comfort are nice.
We do the same thing with the air conditioning, but the AC cools the house a lot faster than the radiators heat it. But it's still nice that the house automatically transitions to away and turns off the air conditioning during the day when nobody's home.
I have the same thing and to be honest, if I had to replace a $200 thermostat every 2 years I would gladly do it. In fact, this whole thing has made me go and research which thermostat will fit where I live.
1. A non-smart device that will work forever but looks and feels like it's still in the 90s
2. A device with a nice, responsive UI, but destined for the landfill because it's chained to a cloud service.
Why are these things mutually exclusive? Across so many product categories, there's seemingly few or no options for a nice UI but without dependence on an Internet service that will inevitably shut down.
Not that straightforwardly in Nest's particular case to be fair, but a lead in to other products, and Nest was perhaps bought by Google before having to worry too much about profit margins(?).
Can a $20 Honeywell thermostat do that with wireless sensors? If it can, I will get one.
What made it worth it was being able to turn off the air or heat when you weren't home automatically. Now all or the "AI training" garbage? Yeah, forget that. I used to work in an office with a nest and it was torture if you showed up too early if stayed a little too late.
It doesn't need to be cloud-connected to do so, but that's not a feature I'm aware a $20 Honeywell has.
Being able to use the temp reading in a specific room is choice.
These mofos are too greedy to do this.
Both Zwave and Zigbee build mesh networks with multiple routes. Wifi devices ... don't. Wifi is fine for IoT but it isn't optimised for it. My fridge/freezer uses wifi as does my oven and microwave. It doesn't matter if they lose comms sometimes and there is no choice anyway.
My light switches are Zwave. Thanks to way modern UK wiring is done, most of my switches end up with an extra conductor and so are permanently powered and act as hubs for the battery powered window sensors and the like.
My cameras are all PoE ethernet, including the door bell. All Reolink.
I have two UPSs with at least 30 mins run time. I could easily put in a genny or a battery or even use my car (EV) but its not important enough (yet). So far everything will work without the internet.
I have deployed two VLANS for IoT - THINGS, and SEWER for the really worrying gear on it!
Home Assistant runs the show.
I worked for a company that converted a legacy wire protocol with no QoS guarantees to be used over a proprietary modification of Zigbee. One of the managers complained that their volume control would randomly climb to the max loudness. The protocol used press/release packets for button presses and if the volume-up release packet was lost due to interference, you got a runaway increase in volume from the system assuming it was still held down. This usually happened when the channel assignment was in a band used for active wifi.
If the medium was ATM or hard wired ethernet then sure why not send button presses. Those are reliable media.
The obvious fix would be transmit "vol+1/Pressed" on button press and "vol+1/Release" on button release. On receipt of v+1 do just that and no more. Note a /Release to colour a widget correctly, perhaps. Holding down V+ would transmit multiple v+1 or use a wheel as an old school Walkman did to send actual values.
Nothing new is old or something 8)
The key is do not buy smart devices with Wi-Fi. There are better products for serious people. Everyone here with a Zigbee or Z-Wave product probably learned that the hard way first. ;)
I think the valuation thing is what drives 90% of this stuff. Whereas an established company like Honeywell is more interested in building products and selling a lot of them, so they're going to charge you 5-10x of the cost of a Nest for the same feature set but with a local-first implementation instead of a cloud-first implementation.
I don't think I would ever buy a hardware product from a company billing themselves as a VC-backed startup.
Also, FWIW the Nest is a perfectly functional thermostat even if you never hook it up to their app. We found the scheduling and learning features to be really annoying so we turned them all off and never connected ours to the cloud.
> so [companies like Honeywell] are going to charge you 5-10x of the cost of a Nest for the same feature set but with a local-first implementation
"Established" companies also see the long-term value of subscriptions and are also hopping on that bandwagon.
Additionally, customers are extremely sensitive to up-front price, so a product that's more expensive up-front but with no subscription fee and longer-term value will have trouble finding a foothold in the market compared to cheaper but subscription-based alternatives. Especially if the alternatives are "1 year free!" as they usually are.
A Nest is ~$150, so I'm curious where these $750-1500 thermostats are...
Seems like you get a Honeywell thermostat for almost exactly the same price, if you don't care about cloud connectivity.
Nests performed well in unique spaces with different heating and cooling profiles, not to mention different kinds of shoulder seasons.
The real difference is that these are not american sv vc backed companies like nest or ring. they are chinese companies set on disrupting those vc backed companies using this local first mindset as the differentiator.
If you have the latest models you’re not dependent on the cloud, and it’s unfortunate Google didn’t add this functionality to these retired models.
I have a Honeywell t6 that I got when they installed a new unit - Honeywell INSISTS that you create an account and download the app to connect it to your home network
Thankfully this is bullshit and you can connect it directly from the thermostat to HomeKit - you will not find a single piece of documentation on this though and will be told it’s not possible
The real kicker is that there is a notification to register your device that you can’t get rid of unless you register your device
You can only snooze it for a couple weeks at a time
How I’d love to have one on one conversations with the evil people who approve this type of crap
You’re still in the return window when you are presented with the service ToS.
I wonder if that's because the ones that would be upset never bought them in the first place.
Google does quite literally owe their shareholders ROI, by law.
Why would one expect them to do anything other than the minimum support period and expense that they can get away with that won’t trigger a class action?
There are no surprises or bait and switch here. Nobody was promised eternal support or updates.
It’s a business, not a charity.
Serious answer: I do not expect any specific lifetime at all (though legal return period is an obvious floor), but at a bare minimum I do expect (and think should absolutely be mandated by law) that power be intimately tied to responsibility. Ie., it's fine if a hardware vendor decides to retire their cloud services (or OS updates or the like) in 1 year or 10 years or 20 or 30, but IF they cease to support it, THEN they must also remove any technical obstacles to hardware owners pointing it at another service of any kind. So any signing keys required, code, docs/APIs etc. Decide that a given product no longer makes commercial sense for you to produce or support? Sure, fine, it happens. The problem is then ensuring the hardware/software dies with that.
The basic issue is that these places generally want to have their cake and eat it too. They want all the financial power of a monopoly tie-in and feudal rent extraction, but no responsibilities to go with it and the ability to force customers onto new stuff (or nothing). That should be illegal. Honestly, I think any tie-in should be illegal, fully accessible local APIs should be required and any 1st party subscription should earn its place on its merits.
But at a minimum, no one should be able to have it both ways. If they want power over their customers, they should have responsibility proportional to that. And conversely if they go full open source community friendly hackable from day 1 (and are fully upfront about that), I'm fine saying they have very minimal long term responsibility. There can and should be room for many different approaches to the market, but not extractive lock-in.
Lyrion Music Server (formerly Logitech Media Server) is open-source server software for Squeezebox audio players, https://lyrion.org/
Tasmota is open-source firmware for ESP8266 and ESP32-based devices, https://templates.blakadder.com/preflashed-stand.html & https://github.com/tasmota
Some IP cameras have open firmware replacements.
Some Chromebooks are supported by mainline Linux.
Well, that, and the moving target of updating an "app" every year for all the breaking changes Google and (especially) Apple do to the mobile OS. Although honestly I'd rather have a QR code that links you to a PWA hosted on the thermostat itself.
If I want to change the volume of my "smart speaker" from my phone that's also on my LAN, it shouldn't require a round trip to a server on the Internet, or an account with credentials, or any of that nutty stuff.
My theory is that it checks boxes for "sEcUrItY."
There aren't enough enthusiasts who know the first thing about computers or security to be a market for any mass-market hardware, so they're designed for the proverbial "grandma" to be able to plausibly use. Therefore, you can't ask them to establish, remember, and maintain the secrecy of any credentials.
Therefore, they either need to make the devices permissively trusting on the LAN (which IoT devices got a lot of criticism for a few years ago) or they need these fluffy login methods that introduce dependencies: Usually they require email for forgotten-password recovery, SMS for a "sEcOnD fAcToR", and of course, because it would confuse people if the control only worked on the LAN without integrating into a home hub, they need every device to connect directly to the cloud and therefore for the app control to go through the WAN. Or at minimum, the LAN<->LAN communication is only permitted by possession of a JWT or similar that's been recently authorized by the cloud server.
* technically still does, but they tried to switch before they backpedaled
"Smart" home devices work as expected for about a year and then they fail in new and exciting ways, and then you replace them.
* There are internet-connected controllers and local controllers so you'd also want a local controller. I've used an Aeotec Z-Stick for ZWave devices for around a decade, it plugs into USB, HomeAssistant accesses it directly, and the ZWave network itself is connections between the Z-Stick and the devices without the internet.
Source: I own one. :)
Curious to hear what local polling or local push thermostat you settled on with HA support!
And is actively trying to prevent hackers from running stuff locally.
https://www.youtube.com/watch?v=66j9dsPhAjE
Then they couldn't resist fiddling with the UI. Every new update changed the UI such that I had to relearn how to operate it.
That was the last straw, so I disconnected it from my wifi and just used it as a standalone thermostat.
> "Smart Local Control" home devices work as expected until the electronics fail
ftfy.
Recently one of my Zigbee-controlled thermostats started pumping cold air constantly. To fix it, all I had to do was open and examine the board; one of the varistors got some battery acid on it when I had an alkaline battery burst in the unit. Because it was a no-name with an actual PCB, I was able to solder a new varistor in place, and it works good as new.
So I would say that "Smart Local Control" isn't the problem, but rather the ability to repair the thing. Also, the thermostat was $45 when I purchased it 5 years ago, so it was a good investment IMO. I think that's why everyone is upset about the Nest gen 1 and 2 sunsetting; there should be no reason that these devices should be breaking now (no failing electronics) but they die anyway because the company is too cheap to keep an extra endpoint running.
1. That you can buy a smart local control device.
2. That the electronics were designed with appropriate thermal management so they don't fry themselves quickly. Smart bulbs are the most notorious offenders here, but the problem is widespread.
Also, that posts says the thermostat will still work locally so the failure state of the "smart" device here is that it became a "dumb" device after a decade+.
[1] - https://en.wikipedia.org/wiki/Google_Nest#Nest_Learning_Ther...
Release years aren’t purchase years.
Everyone didn’t have the same purchase year.
And, it’s just a thermostat. When they first came out it was a little novel. Not anymore.
Temperature is a solved problem and algorithm.
There’s no real reason to discontinue them - they do the same thing they always have, connected to the same shared infrastructure.
I highly doubt the cost of cloud, tech increased or decreased since then.
It feels like a form of forced planned obsolescence. Maybe some growth or product folks not hitting their bonus lol.
Gen 1 and Gen 2 were unique also don’t have microphones in them. I know Gen 2 handled microbursting well not sure about other gens.
The truth is the cloud is someone else’s computer and the cloud always costs someone else, if not the customer.
Maybe nests aren’t being replaced fast enough or new nest purchases aren’t growing like before due to other options.
I won’t trust or buy any more Nest devices again or trust the brand. I buy newer Nest devices and cycle them out.
Gen 1 and Gen 2 folks were early adopters and they can find more elsewhere.
There are lots of other better options.
It’s easy to go early adopt the next thing. Home automation has come a long way and those who are trying to earn in the past risk being left in the past.
The device will work locally but api is being removed so the mobile app won’t work and neither will any home automation integrations.
The least they could do is just let people control it directly. We’ll see if it gets unlocked now.
EDIT: That comment was heavily expanded after I replied. It was originally only about the distinction of purchase date. I won't debate the rest of the comment because as I said at the start, "While I agree with the message...". I just don't think this specific case is a particularly good example of what is being argued and therefore arguing it is probably counterproductive.
I know this because I’ve bought a few, not sure about yourself.
Hope that helps.
https://www.reddit.com/r/hacking/comments/1k97rv0/hack_a_nes...
That’s no excuse for Google arbitrarily disabling functionality.
Lol
One device is a pain. When you have a smart fridge, dishwasher, sonos, doorbell, smart lock, etc: the mean time to corporate abandonment gets very short.
I have an Ecobee, and for sure I’m looking to get off of that ecosystem once I’m forced to.
It also feels like Ecobee is an abandoned project at this stage: I get a 500 error trying to get a dev token, and portions of the app have been broken the entire time I’ve had one (9 years, 2 devices).
Yeah, I don't have a smart home, but all my old stuff works great and that will continue until after I have left this place.
Maybe I do have a smart home.
Some earlier discussion: https://news.ycombinator.com/item?id=45033555
And when it was announced in April: https://news.ycombinator.com/item?id=43802574
121 more comments available on Hacker News