From e0f8df3eadbed1f45310e58b3a3e6e1437dd3db1 Mon Sep 17 00:00:00 2001 From: Cagri Yucel Date: Tue, 5 Dec 2023 18:05:39 +0000 Subject: [PATCH] Add a new troubleshooting step for Something Went Wrong error (#30163) Co-authored-by: Fletcher Co-authored-by: Cagri Yucel Co-authored-by: Franck Nijhof --- source/_integrations/nest.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown index f50b7417eec..511ae508cf4 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -533,6 +533,8 @@ authentication process. - *Something went wrong: Please contact the developer of this app if the issue persists*: This typically means you are using the wrong type of credential (e.g. *Desktop Auth*). Make sure the credential in the [Google Cloud Console](https://console.developers.google.com/apis/credentials) is a *Web Application* credential following the instructions above. +- *Something went wrong, please try again in a few minutes*: According to Google's [Partner Connections Manager Error Reference](https://developers.google.com/nest/device-access/reference/errors/pcm), this error covers all other undocumented internal errors within Partner Connections. One of the issues that cause this error is synchronization problems between the Nest and Google Home apps. Confirm that your Nest device is visible within both apps under the same Home. If it is missing within Google Home, create a new dummy home on the Nest app, which triggers the synchronization process. (This is the workaround recommended by the Google support team). The dummy entry can be deleted once the Nest device is visible within the Google Home app. + - *Can’t link to [Project Name]: Please contact [Project Name] if the issue persists*: This typically means that the *OAuth Client ID* used is mismatched {% details "Resolving mismatched OAuth Client ID" %}