Partner Connections Manager Error Reference
Stay organized with collections
Save and categorize content based on your preferences.
During or after account linking
,
PCM may return an error. The errors documented here are
listed in order of precedence.
In this document, PARTNER
refers to the name of the
Device Access project.
During account linking
These errors occur during the account linking process.
Something went wrong
Can't link to PARTNER
This error may surface different messages:
This version of the error occurs for a few different reasons:
- The Device Access project has been
deactivated.
- The OAuth 2.0 Client ID used in PCM does not
match the one configured for the Device Access
project.
To enable PARTNER
, make sure
you've migrated your Nest Account to Google.
This version of the error occurs when the user attempting
account linking does not have a Nest account, or has not migrated that
Nest account to a Google account. It may also occur if migration has
been completed, but the Google account has no structures.
A
"Migrate to Google" URL is provided with this version of the error.
This version of the error occurs if the user attempts to
link an account that does not meet the age requirements for managing
their own Google account. These types of accounts cannot be used for
Device Access.See Age
requirements on Google Accounts
for more information.
No access to partner
Can't find devices to link to PARTNER
Something went wrong, please try again in few minutes.
This error encompasses all other internal errors. Wait a few minutes before
attempting account linking again.
Logged in account
These errors occur when viewing PCM for a Google account
that is logged in and may have already been linked to a Device Access
project.
No partner connections found
No home found
Can't find devices in home
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License
, and code samples are licensed under the Apache 2.0 License
. For details, see the Google Developers Site Policies
. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-07-25 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-25 UTC."],[[["\u003cp\u003eThis document outlines potential errors during or after account linking for the Device Access project and offers troubleshooting steps.\u003c/p\u003e\n"],["\u003cp\u003eErrors are categorized by stage of the linking process: during account linking, or when the Google account is logged in.\u003c/p\u003e\n"],["\u003cp\u003eCommon errors include issues with Project ID, Device Access project status, user account requirements, and home or device setup in Google Home app.\u003c/p\u003e\n"],["\u003cp\u003eEach error message provides a description and potential solutions, such as verifying project details, migrating Nest accounts, or adjusting Google Home settings.\u003c/p\u003e\n"],["\u003cp\u003eFor persistent issues or internal errors, contacting the partner or retrying after a few minutes is recommended.\u003c/p\u003e\n"]]],[],null,["# Partner Connections Manager Error Reference\n\nDuring or after [account linking](/nest/device-access/authorize#link_your_account),\nPCM may return an error. The errors documented here are\nlisted in order of precedence.\n\nIn this document, \u003cvar translate=\"no\"\u003ePARTNER\u003c/var\u003e refers to the name of the\nDevice Access project.\n\nDuring account linking\n----------------------\n\nThese errors occur during the account linking process.\n\n### Something went wrong\n\n| Message | Description |\n|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|\n| ### Please contact the developer of this app if the issue persists. | This error occurs when the Project ID specified in the PCM URL is not found or invalid. Make sure to use the correct Project ID for your project. |\n\n### Can't link to *PARTNER*\n\nThis error may surface different messages:\n\n| Message | Description |\n|------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| ### Please contact \u003cvar translate=\"no\"\u003ePARTNER\u003c/var\u003e if the issue persists. | This version of the error occurs for a few different reasons: - The Device Access project has been deactivated. - The OAuth 2.0 Client ID used in PCM does not match the one configured for the Device Access project. |\n| ### To enable \u003cvar translate=\"no\"\u003ePARTNER\u003c/var\u003e, make sure you've migrated your Nest Account to Google. | This version of the error occurs when the user attempting account linking does not have a Nest account, or has not migrated that Nest account to a Google account. It may also occur if migration has been completed, but the Google account has no structures. A \"Migrate to Google\" URL is provided with this version of the error. |\n| ### It looks like you need to be a little bit older before you can link to \u003cvar translate=\"no\"\u003ePARTNER\u003c/var\u003e. Talk to a parent for more information. | This version of the error occurs if the user attempts to link an account that does not meet the age requirements for managing their own Google account. These types of accounts cannot be used for Device Access. See [Age requirements on Google Accounts](https://support.google.com/accounts/answer/1350409) for more information. |\n\n### No access to partner\n\n| Message | Description |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| ### Information could not be retrieved. Please contact \u003cvar translate=\"no\"\u003ePARTNER\u003c/var\u003e 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. | This version of the error applies to the Device Access Sandbox and occurs when the Google account used with PCM is not an authorized account on the structure being linked. Make sure the Google account is a member of the home listed in the Google Home app. See [Share a home and devices in the Google Home app](https://support.google.com/googlenest/answer/9155535) for instructions on how to manage home members. |\n\n### Can't find devices to link to *PARTNER*\n\n| Message | Description |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| ### If your home has multiple members, the person who first set up the home must migrate their Nest Account to a Google Account before you can link to \u003cvar translate=\"no\"\u003ePARTNER\u003c/var\u003e. | This error occurs when the user attempting account linking has a Google account, but the manager of the home has a Nest account. The manager of the home must migrate that Nest account to a Google account to allow account linking. |\n\n### Something went wrong, please try again in few minutes.\n\nThis error encompasses all other internal errors. Wait a few minutes before\nattempting account linking again.\n\nLogged in account\n-----------------\n\nThese errors occur when viewing PCM for a Google account\nthat is logged in and may have already been linked to a Device Access\nproject.\n\n### No partner connections found\n\n| Message | Description |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|\n| ### New partner connections will show up here. If you're trying to link other services, you can add them from the Home view in the Google Home app. | This error occurs when the user has not connected any partners for Device Access. |\n\n### No home found\n\n| Message | Description |\n|----------------------------------------------------------|----------------------------------------------------------------------------------------------------|\n| ### You need to have a home to view partner connections. | This error occurs when the user has removed all structures from their home in the Google Home app. |\n\n### Can't find devices in home\n\n| Message | Description |\n|---------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| ### Make sure that you have at least one device in your home. | This error occurs when the user has removed all devices supported with Device Access from their home in the Google Home app. |"]]
