How to play: Some comments in this thread were written by AI. Read through and click flag as AI on any comment you think is fake. When you're done, hit reveal at the bottom to see your score.got it
If someone says Google can't be trusted for purchases of long-term, capital-style goods like a thermostat (or smoke detectors), I'd have to agree.
The Nest I bought way back when may still be installed in the home I sold 10+ years ago.
But I didn't buy it from Google, I bought it from Nest (pre-Google) - a company that designed and sold high-tech gear that was designed to be permanently installed and (presumably) last a good long time. The acquisition was not a good match, but it is what it is - lesson learned and reputations lost.
(and the design, honestly, was more down Apple's lane than Google's - I thought the former would be more likely to buy them out, not that it guaranteed any different results).
I think that's an overly optimistic take, because we've been through this over and over, and it's only getting worse. We collectively are clearly not getting the message, and we don't own anything as a result.
I'd push back on the Nest-was-different part. It was a venture-funded startup selling a cloud-dependent device, so it was always going to be acquired or shut down. Google at least kept the early models working for over a decade. A small company with the same business model would've probably died sooner.
What a coincidence, I am working on deploying the https://nolongerevil.com/ on my 2nd Gen Nest Thermostat, my wife has bugging me for weeks to either fix it or buy a new one.
I am actually going to self-host and vibe code my own cloud service on Cloudflare.
Why bother? Block WAN access at the router, put the entire thing behind a VPN (Tailscale or Wireguard, dealers choice), and move on. If you really care, put everything you vibe code or consider security-abandonware on its own VLAN.
Keep it off the WAN and you'll be streets ahead of commercial vendors, and your weird, one-off, vibe-coded app means those same commercial vendors are the easier, more widely-deployed targets anyways.
Login auth is the easy part, though. What authenticates the thermostat itself to your Worker? If it's just a device ID in a URL, anyone who guesses it can set your heat. And what happens in January when the Worker breaks and the house is cold?
Could do something like oauth to gmail + OTP (or passkeys) on cloudflare workers with long lived sessions or I could vibe code an iOS app even and side load it. That would be very secure as well. I haven't decided yet.
I have a personal password manager secured like that I vibe coded to replace 1password and so far it is working great.
On one hand, I obviously can’t legitimately expect the manufacturers of these things to support their older hardware offerings ad vitam aeternam.
On the other, it’s a freaking thermostat controller. An appliance. I don’t want to have to replace appliances before they break, and software breaking it is unacceptable.
I’ve been largely holding off on domotics because so much of it reeks of premature obsolescence... Maybe someone over here has good experience with Home Assistant et al?
I've recently set up Home Assistant again after a 5 year hiatus. All my old devices still work fine.
I primarily use zigbee, which is fully local and very reliable. Home Assistant supports a lot, including older hardware. I have a 2010 Philips LivingColors lamp (predecessor of the Hue) that talks early zigbee and still connects to a 2026 zigbee dongle + Home Assistant install.
I avoid any cloud dependency for the reason you give. Anything local, especially with open protocols and an active community, will probably work for a very long time. Likely the lifetime of the appliance.
I was looking at wireless cameras on eBay and had to stop because I realized I can't just check specs and price. I have to make sure they don't require a cloud connection and or a service plan.
I just bought a couple of Reolink RLC-810A cameras, and realized too late (after receiving them) that they require an app just to enable communications and configure the baseline RTSP functionality. Claude found https://github.com/TinKurbatoff/reolink-init# and took care of the issue nicely.
I will probably buy a couple more of the RLC-810As, since I can only assume that newer models will be harder for the owner to actually own.
What worked for me: search for ONVIF and PoE instead of "wireless." PoE cameras from Amcrest, or the Dahua/Hikvision OEM lines, have a plain web UI and RTSP on by default, with no app or account. Point Frigate at them, block their internet access at the router, done.
I've been using NodeRED + zigbee2mqtt/zwavejs for my locally controlled home automation to great effect. I expose all my devices to Google Home as a convenient frontend, but all the actual devices are mine and locally controlled so I can replace Google at any point. I tried home assistant years ago, but aside from the wealth of plugins I didn't find its approach particularly convincing. I have on occasion used it simply as a bridge between node red and HA plugins before though which is nice for niche devices or integrations
plenty of things should have a mandatory sort of twenty year supportability warranty. not necessarily free repairs but an enforceable promise that a thing / "ecosystem" can be used for a reasonably expected lifetime
Nest is a disaster. Same with their fire alarms. I spent a small fortune buying those, just to rip them out and dump into garbage. Google hardware - never again.
It truly is, and it's a shame since the hardware build quality was solid.
My gen 3 had a bug where when selecting heat mode from off mode after previously being in cooling mode, it'd pulse the AC briefly before ultimately engaging heat, which is absolutely not what you want to do when it's below safe operating temp for the AC compressor.
It was a really basic thing that would have been quickly patched if owned by a thermostat company, but clearly asking too much when owned by an advertising company.
100% agree. i had a thermostat and 4 cameras. abysmal software, and the hardware started dying . The thermostat died after 3 years, due to faulty "smart" HVAC circuitry . The doorbell camera (with built in lithium battery, ) died after 5 years.
i marvel at simple mechanical-electric solutions . e.g. toasters, simple coffee pots, thermostats. 100+ year duty cycles. amazing elegance and resilience
As far as I know, the independent evidence on smart thermostat savings is thinner than the marketing suggests. Nest claimed around 10-12% on heating, but field studies I've seen came in lower, sometimes near zero. So the mercury one isn't necessarily losing on efficiency, just on convenience.
not the parent, but when my nest protects died i switched to dumb ones. all co2 detectors expire after ten years, nest decided the appropriate action is to just brick it when they were ten years old. the only feature i really used was using the app to silence it when cooking got smoky. but theres very few options for smart ones, lack of interconnect compatibility got frustrating if i wanted to mix smart and dumb, and it would have easily cost twice as much(i have 6 detectors).
ive considered connecting the interconnect wire to my esp32 (that replaced the security system) and get it pushed into home assistant, but without the ability to silence, a push notification that it is going off just didnt seem worth it
Have since replaced it with a Z wave Honeywell thermostat, and I'm much happier.
Not only did I kill the wifi & Internet dependency, but the UX is much closer to a traditional thermostat. So other folks don't seem to have an issue with it as much.
And it actually supports my hardware thermometer for dual fuel cutover.
If it depends on some services that are being sunset then the cost of getting them working again approximates the cost of getting them working in the first place.
in theory AI can produce the ongoing software support. and the compute bill is trivial compared to even a single AI assistant customer (1/500). something doesn't add up
I will NEVER buy google hardware again. They kill stuff that we depend on and then just expect you to buy their latest version. Up yours, not going to happen. Got rid of my last nest products this year and did NOT replace with the google version. Goodbye!
Another case of a smart home device that unnecessarily needs someone else's servers. They could've made it controllable over the local network and that would've solved, like, 80% of this issue.
I have a z-wave hub I bought about 8 years ago. Admittedly, it's shit, but it does one thing right — you only need the manufacturer's cloud services if you want to control it from outside of your LAN, or if you want integrations with other services.
The law should require that if a company sells hardware that depends on an internet service, and later discontinues that service, it must open-source the communication protocol and provide a way to connect the hardware to alternative services. This requirement should cover every feature that was functional when the device was sold.
Fortunately Nest owners got lucky this time and there was an escape hatch that allowed projects like No Longer Evil. But there's a long list of devices that have been bricked when their manufacturers shut down a proprietary backend.
Someone has to write 'The law', and we need to prioritize politicians that do (instead of those that are trying to get views on social media by getting quips/gotcha moments).
One of many reasons I prefer home automation hardware that uses ZigBee, Z-Wave, or Thread over using WiFi. If it uses WiFi it almost always wants to connect to or worse requires a cloud, where the dedicated home automation network tech is basically the polar opposite and requires that it work entire directly locally or with a local hub.
Other major reason being that "IoT" devices usually have the shittiest WiFi radios that usually don't even support 5 GHz and almost never support WiFi 6/7 modes where they aren't wasting a ton of airtime on their low-bandwidth communication.
The Matter standard[0] (+HomeAssistant) starts to fix this, but almost all "smart" appliances have this flaw. From Lutron, GE, Apple, Amazon (ring), Philips(Hue), Samsung, LG, Control4, Ecobee, ADT, Schneier, Chamberlain, Tapo.
As if dumb thermostats last really that long.
Ours from Brötli died after around four years.
The replacement has a manufacturing date from 2008 -- what a joke.
The firmware in those things has bugs (like switching some, but not all programs at midnight) that will never get fixed; it works, but not flawless.
Considering this I wouldn't mind a smart solution that lasts /only/ ten years, but gets bug fixes during its lifetime.
Honestly, given the surveillance capitalism of it all, I take this as a win. The termostst should have been dumb the whole time, not an avenue for harvesting our data.
This thing was released in 2011, and can be replaced in 5 minutes for like $100. This is probably longer than any "smart" device from any manufacturer has ever worked. Not everything needs to be an anti-Google crusade.
Swapped my 2nd gen Nest for a Z-Wave Honeywell T6 Pro a couple years ago and paired it with Home Assistant. Gotcha: the Nest may have been power-stealing without a C wire, so check your wiring first. Schedules run locally now, no cloud, and it's boring in the best way.
But I didn't buy it from Google, I bought it from Nest (pre-Google) - a company that designed and sold high-tech gear that was designed to be permanently installed and (presumably) last a good long time. The acquisition was not a good match, but it is what it is - lesson learned and reputations lost.
(and the design, honestly, was more down Apple's lane than Google's - I thought the former would be more likely to buy them out, not that it guaranteed any different results).