In light of Google’s recent announcement that they’ll be turning off the Works With Nest program and the fact that you can no longer sign up for new Nest dev accounts, I’ve been looking for another way to make my Nest Thermonstat usable with Home Assistant.
Since there was a rooting exploit against the Nest Thermostat way back in 2014, I figured it would make sense to use that as a starting point, and see if we can modify or replace the Nest’s built-in software to make it speak MQTT or something else. This would get around them shutting down the APIs, and probably allow us to make it a local-only device. (also it would be cool to be able to put our own interface on that great-looking little screen)
I’m going to start working on rooting my Nest in the next few days (probably after putting our original thermostat back on the wall so we don’t lose heating/cooling control) and see if there’s something that can be done to its software.
Does this seem like a good approach? Is MQTT support the right thing to aim for?
@Weok thanks for the suggestions! Unfortunately, those both still use the Works With Nest API. (they require signing up for a Nest developer account, which is no longer possible)
@whitelynx I was wondering if you had any luck in this area?
I found your thread and had a similar idea. I love my nest hardware, but would love to swap out the software for local control. I’m also debating just selling them off for a different thermostat, but can’t get over how the nest feels when you use it.
I haven’t yet, sorry. We ended up moving, and I haven’t had a chance to work on the Nest yet - the new place has an Ecobee that the landlord installed, so I’ve just been using that. Haven’t had enough time to actually dive into any of the hacks and see if I can actually root this thing. At least now if I brick it, I won’t lose the thermostat from Home Assitant.
While I’ve moved to a 3rd gen at my current residence, my old house will go up for sale soon and I’ll not include the 2nd gen Nest in the sale. I’ll happily donate it to science someone with demonstrable means and intent to get it working with HA. The caveat being that it might be several weeks until it’s free unless I replace it with a dumb one sooner.
It’s not the most elegant solution, but I imagine we could get something working using a MITM proxy to redirect API requests to home assistant. Folks used a similar approach to keep Juicebox EV chargers working when that company threw in the towel.
maybe easier to hack make home assistant tell the nest to turn off and on heating only, use a different sensor already present in home assistant to read the temp, I know have a few devices on mine that give temp readings.
While it’s technically possible to replace the control system with remote temperature sensors and relays, doing so largely defeats the purpose of using a smart thermostat. This approach essentially reduces the device to a basic temperature readout, stripping it of its intelligent functionality.
My primary needs for the Nest thermostat are straightforward: the ability to manually set heating and cooling, schedule temperature changes on a weekly basis, and make remote adjustments when necessary. I also rely on the Eco mode when I’m away for extended periods.
That said, I’m curious—does anyone know what operating system the Nest thermostat runs on? Additionally, is there a way to make the device operate locally, capture the data it transmits, and interpret or manipulate it to create a similarly functional, privacy-focused thermostat?
Hi, I’m reposting my original comment from April 26th (long story short, moderation snafu happened as a new user that caused it to be deleted but talked to the moderators about it afterward).
Does the Nest thermostat really need to be rooted? I'm wondering if a better approach to saving older Nest thermostats and reducing ewaste might be:
- Using the older 'unofficial API' (from around 2014) assuming it still works, and integrate it with Home Assistant (see https://github.com/gboudreau/nest-api & https://github.com/wiredprairie/unofficial_nodejs_nest#readme )
- Encouraging folks to put older and unsupported Nest devices on a separate wireless network that doesn't have internet access but access to a Home Assistant server for remote monitoring & control.
- Facilitate a way for Home Assistant based HVAC control setups to work with energy company savings programs where appropriate (in areas of the US this is fairly common, but they may only be supporting major brand vendors so far)
Having a separate 'rooted' firmware and such feels like a more substantial support effort.
Again, after writing this as others mentioned the ‘unofficial API’ repos I mentioned still depended on home.nest.com so the alternative firmware approach may make more sense if there’s enough support behind it.
I am fully in favor of initiatives aimed at preventing these Nest thermostats from becoming electronic waste. Although I do not have the technical expertise to advise on the optimal course of action, I am more than willing to contribute by participating in any testing or support activities that may assist this effort.
If there are any credible devs who need some sacrificial hardware, I’d be willing to mail off my thermostat to the cause In a USPS flat rate box. I’m not sure how much of a need there would be for extra thermostats, but obviously I’m not using it anymore.
All that you are saying doesn’t make any sense, as you seems to have thrown here from an AI prompt which had no clue about the topic. If you talk nonsense like that and put dash everywhere, don’t be suprised if you are flagged for AI use.
So let’s make it clear. These thermostats have no local network control, they do have local control as you walk to the thermostat and change it manually, but generally configuring them on the display and rotary knob is a pain.
So they have cloud control mainly through the Nest app, which controls are going to be shut down. So, that unofficial API is a pointless suggestion. Everybody knows about that, but moved to the Google one already and paid the money for the device access.
To make it locally controllable you need local access, hence you need a rooted/hacked version of the device.
Anyone know if there have been any developments on this? I haven’t been able to find anything besides people linking to that DFU attack that’s already been mentioned in this thread. I’d love to experiment with it myself, but I kind of need to keep my Nest on the wall to keep the AC going. Those who mentioned having a spare thermostat to loan out, are those offers still on the table? @colindean@forte