I made a crappy Nest Thermostat integration that will work as a stopgap until alternatives come out

[Townsmcp (James T)]

@chilman4081 HA needs to be on 0.118.0 or higher to get the thermostat and cameras

[chilman4081 (Chilman408)]

Thank you, you are right.

[wideboys182 (James)]

Hi everyone a newbie here to Home Assistant. I have followed the guidance to link my Nest Thermostat to HA but have hit a brick wall. I seem to be getting the below, has anyone else seen this?

I have registered for Device Access, the device is active on my Google account, I have setup the Google Cloud Platform and create a project so have all my IDs etc. I seem to get the above when I go to link my account. Have I missed something?

[Tomiam (Tom)]

I think I had the same when setting up. If you click advanced it then brings up a continue box or similar and you can carry on.

[wideboys182 (James)]

Thanks @Tomiam.

Now on the access token. Not sure where I am suppose to paste this command as this doesn’t seem to work in Command Prompt in Windows

[Tomiam (Tom)]

Are you following the steps here?

Google-Nest Offical Device Access Console Finally Released!

I dont know if this will help anyone, however I have documented the setup in a much easier way than the Google docs show: Prerequisites - obtain external address and add the subdomain location /auth/external/callback, eg with Nabu Casa (NOTE - do not add a port to the address): https://[xxx].ui.nabu.casa/auth/external/callback For non Nabu Casa users (probably need to add your port number): https://[your_external_url]/auth/external/callback Browse to https://console.nest.google.com/device-…

[wideboys182 (James)]

I have done all the above except point 14 was google.co.uk. I am on Get an access token from the below which doesn’t appear to be covered in your post:

https://developers.google.com/nest/device-access/authorize

[Tomiam (Tom)]

Sorry I followed the steps in the post i linked to and for point 14 used my Nabu Casa address and it worked first time

[wideboys182 (James)]

I don’t have a Nabu Casa address so used google.com as per the instructions in my URL. I am able to progress but as soon as I attempt the Nest Integration from HA I am shown a message:

Authorization Error
Error 400: invalid_request
device_id and device_name are required for private IP…:

Is Nabu Casa worth signing up to?

UPDATE
I have been able to get the Nest Thermostat working and with Nabu Casa it was much easier. I think that $5 subscription could be worth it. @Tomiam have you done any work on customising the thermostat view? I have come across a few posts making the Lovelace card look like the Nest UI which looks very interesting.

[Tomiam (Tom)]

Glad you got it sorted. Nabu Casa for me is well worth it. Very simple to access HA remotely meaning I didn’t have to learn various other methods and has been stable.

I have not modified my thermostat card, it’s just the standard, I have seen the various mods on here and may delve into it at some point.

[batwater (Ben)]

@wideboys182 Presuming that you are using the Neste Integration from HA for my question…

I’m missing something simple, tried twice to put in the correct Nabu Casa URL for my HA instance, each time I did I got the above private IP error with the local IP of my HASS instance vs the Nabu Casa link that I put into the google console form.

Obviously I’m putting the wrong link in but I do not know where to find the correct link to use, can you provide some guidance as to where to find the correct Nabu link?

Edit: 12/23/2020 Found the answer! You must add the integration by accessing your HASS instance from the remote URL.

[JasonLee (Jason)]

Is it still possible to use the badnest Integration? My thermostat is still unavailable after updating my cookie.

I know there is now an official integration but I don’t want to pay for Nabu and I don’t want to expose my HA to outside my network. I’m assuming one of these two is a requirement?

[bschatzow (Bill Schatzow)]

Mine still works.

[JasonLee (Jason)]

Are you on the latest version of HA? I’m wondering if something in the recent December update might of broken it.

[bschatzow (Bill Schatzow)]

I am, 2020.12.1. Sometimes of my 4 nest devices won’t load, but it comes back. I am going to convert to the new one soon. Want to update to an SSD first which I did today. Have a recorder issue. Once resolved I will start my change over. I have been reluctant to change as I have not had any issues with “badnest” and the new way will take some time to get working correctly.

[SunnyM]

On latest HA here too, and BadNest stopped working several days ago

[bschatzow (Bill Schatzow)]

I just updated to the official release and all is working. Docs are pretty good, but you need to follow them carefully. Also you will need to remove bad nest first.

[SunnyM]

So pay a $5 fee to register a developer account to see our own stats from something we paid hundreds of dollars for

[bschatzow (Bill Schatzow)]

It did not seem to bad. I used my google $ earned from answering stupid questions.

[autotech]

I’m seeing several people are not getting badnest to work anymore.

Any idea if support for this has ended?

I’m hoping to find a free option to connect my nest thermostat to HA.