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.