From d682ce328c298a9232f5e450e62ef7cdfeec1ca9 Mon Sep 17 00:00:00 2001 From: Tom Kay Date: Tue, 15 Dec 2020 10:21:04 +0000 Subject: [PATCH] Add troubleshoot block for "no application name" (#15899) 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 ba76bbaae44..4e577cb2290 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -192,6 +192,8 @@ Once your developer account is set up and you have a valid `nest` entry in `conf - 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. +- *Error: invalid_client no application name* means the [OAuth Consent Screen](https://console.developers.google.com/apis/credentials/consent) has not been fully configured for the project. Enter the required fields (App Name, Support Email, Developer Email) and leave everything else as default. + - *No devices or entities are created* if the SDM API is not returning any devices for the authorized account. Double-check that GCP is configured correctly to [Enable the API](https://developers.google.com/nest/device-access/get-started#set_up_google_cloud_platform) and authorize at least one device in the OAuth setup flow. If you have trouble here, then you may want to walk through the Google instructions and issue commands directly against the API until you successfully get back the devices. - *Not receiving updates* typically means a problem with the subscriber configuration. Changes for things like sensors or thermostat temperature set points should be instantly published to a topic and received by the Home Assistant susbcriber when everything is configured correctly.