From 89cec25d45c81d3fc4aa0cc248c6291417e8b676 Mon Sep 17 00:00:00 2001 From: Daniel <49846893+danielbrunt57@users.noreply.github.com> Date: Thu, 11 Feb 2021 14:49:08 -0800 Subject: [PATCH] Notation: OAuth Consent Screen Publishing Status needs to be In Production, not Testing (#16476) Co-authored-by: Franck Nijhof --- source/_integrations/nest.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown index c47c822d087..0bfc9478c2f 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -78,7 +78,8 @@ Project**. Note: This is a different type of project from the Device Access proj 1. Give your API Project a name then click **Create**. Note: You can ignore the *Project ID* here as Home Assistant does not need it. -1. Click *OAuth consent screen* and make sure you have that configured, otherwise, you can do that now. +1. Click *OAuth consent screen* and make sure you have that configured, otherwise you can do that now... + - Ensure that the ***Publishing status*** is **In Production** and not **Testing**! ![Screenshot of OAuth consent screen creation](/images/integrations/nest/oauth_consent_create.png) 1. Select **External** (the only choice if you are not a G-Suite user) then click **Create**. 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. They make regular improvements to this flow and appear to value feedback.