Google’s decision to cut cloud support for the first- and second‑generation Nest Learning Thermostats left thousands of owners with devices that still control local heating and cooling but lost remote apps, notifications and integrations. Within weeks, a community‑built project led by developer Cody Kociemba has produced an experimental firmware and backend — dubbed “No Longer Evil” — that aims to restore the remote features those thermostats lost.
What changed: Google’s end of support
On October 25, 2025, Google ended cloud support for Nest Learning Thermostats sold in the first and second generations. The hardware continues to function for on‑device control and automatic scheduling, but remote capabilities tied to Google’s servers were disabled: mobile control through the Nest or Google Home apps, status checks, push notifications, Home/Away Assist, multi‑device Eco mode, Nest Protect linkage and some emergency features are no longer available.
Google offered owners of affected units a discount toward newer models, but many customers and digital‑rights advocates called the move a reminder of the fragility of “smart” appliances that depend on remote services.
How the community fix works
The No Longer Evil project replaces parts of a thermostat’s firmware and reroutes its network activity to a third‑party backend that mimics the original Nest cloud. In practical terms, the developer reverse‑engineered the thermostat’s communication layer, built a custom bootloader and kernel components that make the device “think” it is still talking to Nest’s servers, and deployed a replacement API and web interface to replicate core remote features.
According to the project’s documentation, the current alpha restores:
- Remote temperature and mode control via a web dashboard or progressive web app (PWA)
- Status reporting for the thermostat
- The ability to pair thermostats to the replacement backend
- The firmware is alpha software meant for experimentation. Test only on units you can afford to be offline or replace.
- Flashing unofficial firmware can brick a device and will likely void any remaining warranty.
- Using a third‑party server for home devices raises privacy and security tradeoffs until the code is publicly audited and self‑hosting is straightforward.
- If your Nest Learning Thermostat is mission‑critical (e.g., it controls heat in winter and you cannot tolerate downtime), do not rely on alpha firmware. Replace the unit or use the discount Google offered toward newer models.
- If you’re technically comfortable and have a spare thermostat or backup, the No Longer Evil project provides a way to restore remote features. Expect to spend time following detailed flashing instructions and be prepared for troubleshooting.
- Consider security: wait for the project’s source code to be published and audited, or self‑host the backend if you want to minimize third‑party exposure.
- Check local utility programs—many energy providers and municipalities offer rebates for smart thermostat upgrades that could offset replacement costs.
The developer says source releases and the option to self‑host the backend will follow, so users and security researchers can inspect or run the service privately.
What you’ll need and how risky it is
This is not a plug‑and‑play update. The process currently requires technical steps such as putting the thermostat into a device‑firmware‑update (DFU) state, connecting it by USB to a computer and flashing the custom software. The project’s authors and early testing reports emphasize several warnings:
The project’s page cautions: “Only proceed if you have a backup thermostat or can afford to have your device non‑functional during testing.”
Perspectives: convenience, repair rights and security
Owners facing a sudden loss of remote functionality have reacted in two predictable ways: some upgraded to newer Nest or competing smart thermostats; others sought a way to keep perfectly good hardware in service. Advocates of repair and digital longevity view community projects like No Longer Evil as an important safety valve when manufacturers stop supporting older, otherwise functional devices.
At the same time, security researchers and cautious homeowners note the risks of redirecting a device’s communications to an unofficial backend. Until the firmware and server code are widely reviewed, users must weigh convenience against potential vulnerabilities and privacy exposure.
What this means for the smart‑home ecosystem
The quick emergence of a community solution highlights a broader tension in the smart‑home market: manufacturers increasingly tie core features to cloud services, and end‑of‑life decisions can strip a device of its defining capabilities. When the vendor’s support ends, the burden often falls on owners to upgrade hardware, pay for replacement devices or rely on hobbyists and open‑source maintainers.
If the No Longer Evil project follows through on releasing audited, self‑hostable code and tools, it could become a template for preserving other orphaned smart devices. But widespread adoption depends on clear, safe tooling and a path for less technical users to participate.
Practical guidance for owners
Bottom line
No Longer Evil is an early but meaningful example of how the open‑source community can push back on the planned obsolescence that cloud‑dependent devices sometimes face. It’s not a turnkey solution for most users today, but for technically proficient owners unwilling to discard otherwise working hardware, it offers a credible path to restoring much of the functionality that Google’s cloud sunset removed. As the project matures, its approach and the debates it sparks will be a bellwether for how consumers and makers handle the lifecycle of connected home products.