I’ve followed all the Google Nest integration setup steps multiple times and I get this error every time at the very last step (after it opens the Google page and you sign in and Link accounts): “Error while obtaining access token.”
I’m running this on a Raspberry Pi 4 B as a Docker container. I got it working before when running Home Assistant OS as a VM on a Windows host.
Here is a screenshot of the error:
Is your homeassistant using http or https ? Confirm the correct url.
Disable addblockers, script blockers, dns blockers
If you are subscribed to nabu casa, try the url for that.
It’s using plain http. I copy/pasted the URL in my browser so should be the right one.
I tried again in a private Firefox window and disabled my adblockers, but still no luck.
I noticed a failed request from the network debugger after clicking “Link account”. It says “oauth_failed”:
GET http://raspberrypi.local:8123/api/config/config_entries/flow/de9f3498972f989ef62c65c29e3d02d9
JSON Response:
{“type”:“abort”,“flow_id”:“de9f3498972f989ef62c65c29e3d02d9”,“handler”:“nest”,“reason”:“oauth_failed”,“description_placeholders”:null}
Did you ever get to the bottom of this? I’m having the same issue but against my xxx.duckdns.org version of the url. I’ve followed various setup instructions for Nest to the letter and none of them work.
It worked after upgrading the Home Assistant Docker image from 2024.1.6 to 2024.2.2. I was actually using the latest tag, which was pointing to 2024.1.6, so I had to explicitly set the tag.
I deleted my Nest credentials and then did the setup again exactly as before, reusing my Google Project ID and Device Access Project ID, and it just worked.
Im getting this error again. Deleted credentials. When adding the integration, the erorr shows up in the same exact spot as the screenshot in this thread
I’m going to leave a comment here because I had this problem and found the problem - when looking at the client id’s in my google console I didn’t notice that ALL the id’s start with the same 12 characters - so when I looked at my notes for my client id’s and secrets I grabbed the first client and thought “yeah, that one, the first 8 digits match” - not noticing that it’s 12 numbers followed by probably a guid. So when I entered my credentials I used the wrong account to go with the secret and got exactly the results mentioned in this post. So then I had to go to the integrations tab, where you add an integration, click on the three dots in the upper right corner and select “Application Credentials” and delete the bad credentials I made. Now I could put in a correct client and secret pair and it all worked.
So basically if your secret does not match your client id you fail at the very end of the authentication process.
