Note that OAuth for Apps has been deprecated by Google and will break by October 2022. See Troubleshooting below for steps to resolve the common misconfigurations that result in errors such as Can’t link… or Error 400 from Google. In this section you will authorize Home Assistant to access your account by generating an Authentication Token. Make sure the status is not Testing, or you will get logged out every 7 days. This does not expose your Google Account or Nest data. The warning says your app will be available to any user with a Google Account which refers to the fields you entered on the App Information screen if someone finds the URL.

Navigate back to the OAuth consent screen and click Publish App to set the Publishing status is In Production. Click Save on your test account then Save and Continue to finish the consent flow. On the Test Users step, you need to add your Google Account (e.g., your address) to the list. On the Scopes step click Save and Continue. logo) to avoid additional review by Google. These are only shown while you later go through the OAuth flow to authorize Home Assistant to access your account.

The App Information screen needs you to enter an App name and User support email, then enter your email again under Developer contact email. They make regular improvements to this flow and appear to value feedback. While you are here, you may click the Let us know what you think to give Google’s OAuth team any feedback about your experience configuring credentials for self-hosted software. Select External (the only choice if you are not a G-Suite user) then click Create. By the end of this section you will have configured the OAuth Consent Screen, needed for giving Home Assistant access toĬlick OAuth consent screen and configure it.

Camera gif