Anyone wanting developer access has to pay a one-time non-refundable $5. Wow, Google sucks ( Before creating your first project, you must register for Device Access. Registration consists of the acceptance of the Google API and Device Access Sandbox Terms of Service, along with a one-time, non-refundable fee (US$5) per account.
You will not be able to create a project until you have accepted both Terms of Service and paid the registration fee. This applies to all users, both individual users and those looking to create a commercial offering.)
Happy to help with development work for anybody that wants to collaborate. I’ve never developed for HA but otherwise I’m fairly competent having worked as a developer for several years.
I am in the dark ages and still running the original RedDragon integration with my Nest account. I have Nest Protects and a Nest Thermostat. Am I safe to migrate to mattsch’s integration and a Google account?
I’m in the “well I’ve waited this long, might as well let this play out” camp.
I’ve been very close to switching to Google Auth and the newer repo as well but after this news and seeing the API I’ve decided something will probably come out pretty quick since the API looks pretty straight forward even to me.
Yeah they seem to be the red head stepchild of the bunch. Shame because I thought they were pretty cool when they came out. I needed smoke detectors when they came out for my whole house when I added on to my house. (Code) so I’d be really irked through their life cycle. Glad I’m only 1 product in. They’ve got so many pieces to make a complete eco system but just fall on their face when it comes to… being an eco system.
I was able to get my Nest Protects showing up in HA using the mattsch/badnest integration and they work fine in HA. However I tried to export the sensors via the HomeKit bridge and it didn’t give any errors, but they don’t show up in HomeKit. Anyone know how to make them work in HomeKit, or is that not possible? Thanks!
After the thermostat stopped working again, I followed the instructions given by @Meelobee and copied these type of cookies:
cookie: __Secure-3PAPISID=…/…; __Secure-3PSID=…
It all went well. Please take care of the " " as well.
Wow. I’ve been trying to get Bad Nest to work for over 6 months and your suggestion finally got it up and running for me. I have a first generation Nest, so I didn’t have a “WWN Reset” option in my settings, but I just reset the Nest to factory settings, reconfigured the Nest through the on-screen setup process and then re-added the cookie to my configuration. Restarted HA and bam. It worked. Thanks!
Maybe a dumb question but do you need to do any extra configuration besides the snippet shown on github with the badnest/climate/camera/sensor to get the Nest to show up? Blew a few hours trying to get it working this morning including factory resetting my Nest twice and redoing the cookie/token thing multiple times, no error messages in debug logs either I just see the “adding thermostat”, “adding sensor” etc type messages and then nothing else. Makes me wonder if I missed a step or if my Nest is cursed somehow.
Well, I can still control it by bridging through Alexa so it’s not a HUGE deal, though that route is very limited. (Need to create a routine in advance with specific temperatures set up and then trigger it through a template contact sensor or something, also no way to push the current temperature back to HA for purposes of automation or whatever.) Hopefully with the API finally out in the open we’ll see the official integration updated soon…
Replying to my own message, I switched from HOOBS to Homebridge (both on docker) and my thermostat shows up fine with the same plugin in Homebridge, but not HOOBS.
Unsure what has happened but I think the GitHub repo has been moved or renamed as I am getting error 404 messages in the homebridge core logs. Is anyone else having the same issue? The plugin still works but I doubt it will get any more updates.
It appears the repo was deleted, the local copy I have still works and currently this is the only workable method I have to control the Nest thermostat from HA.
@USA-RedDragon, I guess you have no desire to maintain this further?
Yes I have 2FA set up with Nest but haven’t migrated to a Google account so the native plugin just doesn’t work for me. Luckily I got it just before it was deleted as I have only recently fully migrated from Homebridge to Home Assistant in the last week. At least for now it still works.
If we get native support for Nest 2FA then I will just use that. But if it ain’t broke…
I just added a nest hello doorbell to my system. The badnest integration is still working for my nest protects and two thermostats but isn’t picking up the new device. Not sure if there is any steps required to resync it.