From 0da413743c04983286f9b397c7f9544116443ebd Mon Sep 17 00:00:00 2001 From: Allen Porter Date: Sat, 24 Jul 2021 13:13:29 -0700 Subject: [PATCH] Improvements for nest documentation based on recent user issues (#18599) Co-authored-by: Franck Nijhof --- source/_integrations/nest.markdown | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown index e1412846b84..e70ae145fee 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -35,6 +35,10 @@ There is currently support for the following device types within Home Assistant: This integration supports two Nest APIs. The SDM API is the new primary API that accepts new users. The Legacy Works With Nest API is not accepting new users, but the documentation still exists at the bottom of the page so existing users can keep using it. +Google applies strict [Redirect URI validation +rules](https://developers.google.com/identity/protocols/oauth2/web-server#uri-validation) to keep your login +credentials secure. In practice, this means that you must access Home Assistant *over SSL* and a *public top-level domain*. See the documentation on [Securing](/docs/configuration/securing/) or [Troubleshooting](#troubleshooting), and note that you don't need actually need to enable remote access. + ## Overview: Supported Devices Home Assistant is integrated with the following devices through the SDM API: @@ -247,8 +251,8 @@ everything, however, you can leave out any feature you do not wish to use with H domain (such as .com or .org)* or *must use a valid domain that is a valid top private domain*. This means that you may need to change the URL you use to access Home Assistant in order to access your devices. - - A convienent solution is to use [Nabu Casa](https://www.nabucasa.com/) - - There are subtle rules for what types of URLs are allowed, namely that they must use a publicly known hostname, though your Home Assistant ports do not need to be exposed to the internet. + - See [Securing](https://www.home-assistant.io/docs/configuration/securing/) Home Assistant for convient solutions e.g. [Nabu Casa](https://www.nabucasa.com/) or Duck DNS. + - There are subtle [rules](https://developers.google.com/identity/protocols/oauth2/web-server#uri-validation) for what types of URLs are allowed, namely that they must use SSL and a publicly known hostname, though your Home Assistant ports do not need to be exposed to the internet. - You can use any publicly known hostname you own - As a hack, you can use hosts tricks to temporarily assign a public hostname to your Home Assistant IP address. @@ -275,13 +279,14 @@ logger: homeassistant.components.nest.climate_sdm: debug homeassistant.components.nest.camera_sdm: debug homeassistant.components.nest.sensor_sdm: debug + homeassistant.helpers.config_entry_flow: debug + homeassistant.helpers.config_entry_oauth2_flow: debug google_nest_sdm: debug google_nest_sdm.device: debug google_nest_sdm.device_manager: debug google_nest_sdm.google_nest_subscriber: debug google_nest_sdm.event: debug google.cloud.pubsub_v1: debug - google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager: debug ``` ## Camera