It is in the first paragraph.
From Nest - Home Assistant – I realize it’s frustrating to waste $5 but i think it’s pretty clearly labeled.
Thanks for pointing this out! I am not sure how I missed it. Perhaps I only read the step-by-step instructions part. Another thing that would be nice to do is not to have this integration not jumping out for unsurrported devices. Anyways, thanks for all the efforts!
1 Like
Yeah, i think the problem is the auto detection is using a mac address shared by both supported and unsupported devices. I think the option would be to disable detection entirely…
Ok, I’ve tried every suggestion the last 2 days and it’s not working. I’ve a Nest Hub (not Max), I’ve factory resetted it, I’ve deleted my home from the Google Home app and started over, added my account in every step required (a personal one, not GSuite). I’ve double checked the accounts being the right ones, I don’t know what else to do, I’m stuck with the “No access to partner” no matter what I do. I think the Nest Hub it isn’t compatible in some way.
Nest hub is not on the list of supported devices as far as I know.
Just bumping to second this. First time using HA and after setup was prompted to configure the add-on for my Nest Hub, only to now find out that it isn’t supported.
If it’s a shared mac address issue then maybe have the integration display that it is only the Max is supported, & unhide the supported devices section in the set-up doc if it’s prompting people with unsupported devices? At least that -$5 will teach me not to skim in future!
I have a couple questions:
- is it an older version of home assistant or the latest?
- Do you know your devices mac address prefix?
Here is the current list:
I’ve already removed some from the list:
[skip two paragraphs if you just want the answer] I bought the new Nest Wired Doorbell and I spent hours and hours trying to get this working. Brand new Gmail account, set up everything clean in the Google Home app, followed all the steps to the letter, but I just got the “No access to partner” error every time.
Worth noting is that this error is not Home Assistant specific: following the instructions at Authorize an Account | Device Access | Google Developers to generate an authorization code only depends on the project-id and oauth2-client-id, and it fails in the same way.
So my problem turned out to be that I didn’t have any supported devices in my account. The troubleshooting page is super confusing with the suggestion to add the developer as a home member, because I only have one home member, and it’s me. Fortunately some previous messages in this thread mentioned not having supported devices, and after realizing that “Nest Doorbell (wired)” listed on the Supported Devices page is not the product currently being sold as “Nest Doorbell (wired)” (
), so I guess technically this isn’t on the list, it all started to fall into place.
I removed a thermostat from another account and added it to this one, and although it took 15 minutes to show up, once it did, the authorization flow worked. And only the thermostat shows up. I’m hoping this is a very temporary situation, because it’s kind of ridiculous to introduce a new product with the same name as a supported old product (and it’s just a wired version of the supported battery doorbell) and not support it. I assume somebody just needs to add an entry to a file somewhere.
Anyway, I wanted to add this comment for others running into this problem. It was mentioned above but not obvious: the cause count be that nothing on your account is supported by this API. I don’t know why they don’t just authorize and return an empty device list.
1 Like
I also ran into this problem and what masto said tipped me off. They said it already, but to be crystal clear, the 2nd gen wired doorbell (the one that came out a ~week ago) isn’t supported by SDM yet. See this nest community post.
Hopefully they add it to SDM soon, I probably would have gone with another product if I would have realized it’s not compatible.
Same here, it pist me off when I read your post ! Bought a 2nd gen doorbell wired and get stuck with the fucking no partner access message.
Same error message “No Access to partner”.
Everything is set correctly, I have one personal Google Account.
URI set up correctly. Nest devices registered to the same account.
paid the §@# 5$…
If I look at supported devices the Nest Smoke Detectors are not supported. That really sucks.
“No access to partner” always means there is a misconfiguration somewhere, or the account type is not allowed for some reason, one account setup in device access console vs different account used in cloud console, or there oauth id between device access console and google cloud console doesn’t match, or some kind of permissions issue with the Google Home app, etc.
You can see the SDM troubleshooting instructions for more detail from Google: Partner Connections Manager Error Reference | Device Access | Google Developers
Whilst going through the Google Nest setup routine, I received the same error as the OP’s Partner Connection Manager issue and I found this page.
I have fallen foul of the (un-)supported devices, having 2x Nest Mini’s and 1x Nest Audio. What led me down this garden path was the fact that HA “Discovered” Google Nest.
As @chiahsing says, if there are no supported devices, then what has HA “Discovered”? A waste of £4.15.
If the Nest speakers are not supported by SDM, is it not possible to get them to drive Home Assistant?
Google Assistant: Google Assistant - Home Assistant as opposed to Google Nest.
I’ve raised a PR, slightly rewording the introduction so others won’t lose $5.00.
1 Like
Ok the problem is all the devices use the same Mac address range. Can you let me know the Mac address ranges of your devices and we can exclude from discovery though unfortunately it disables discovery for other nest devices too.
Google enjoy nicking your Money! done it with me! Going to ring back and ask the though only $5 to refund me everything as a warranty!
Vidoe Im following and still having the same issues! Gone thorigh ti 6 times now changed things removed things and still same error message.(No access to partner
Information could not be retrieved. Please contact Home Assistant to verify that your account has been properly set up. You may need to add the developer email address as a home member in the Google Home app settings.) Has anyone really figure how to get this to work or is it all a scam? Even the Yellow does not work! From China!
If you see this, you have missed a setup in the setup. (e.g. maybe you didn’t set “production” as the status"). Not sure what video you watched, but Google Nest - Home Assistant has a video linked with instructions. I wouldn’t follow any others.
(You can see Integrations | Home Assistant Analytics for an idea of how many folks have completed setup successfully.)
1 Like
@BartK2
After spending hours, creating new projects, new users, new certs, I found a comment post on the bottom of website, of the video creator for the youtube video which is embedded in the Home Assistant Google Nest page.
I had not migrated my old Nest account to a Google account. Doing this migration via the Nest app fixed everything and allowed me to link my account without the “No access to partner” error message.
I have raised a PR to update the official documentation.
Copy of my edit.
“- No access to partner information “Information could not be retrieved” error message during the setup wizard means that the Google Account used is not able to access the Home. Please ensure that you have successfully migrated your Nest Account to a Google Account using the Google Nest App. Additionally, if your home has multiple members, please note that the individual who initially set up the home must complete the migration of their Nest Account to a Google Account before you can establish a connection with Home Assistant.”
I believe this fixed the issue, can I ask if you could please mark this post as the solution, to help others find it in the future? 