You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/_integrations/google_assistant_sdk.markdown
+14-15Lines changed: 14 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -44,21 +44,20 @@ This section explains how to generate a Client ID and Client Secret on
44
44
1. First go to the Google Developers Console to enable [Google Assistant API](https://console.developers.google.com/apis/api/embeddedassistant.googleapis.com/overview)
45
45
2. Select an existing project or create a new one from the dropdown menu in the upper left corner.
46
46
3. Click to enable this API.
47
-
4. From the left sidebar click on [Credentials](https://console.cloud.google.com/apis/credentials)
48
-
5. Click on the field on the left of the screen, **OAuth Consent Screen**.
49
-
6. Select **External** and **Create**.
50
-
7. Set the *App Name* (the name of the application asking for consent) to anything you want e.g. *Home Assistant*.
51
-
8. You then need to select a *Support email*. To do this, simply click the drop down box and select your email address.
52
-
9. You finally need to complete the section: *Developer contact information*. To do this, simply enter your email address (same as above is fine).
53
-
10. Scroll to the bottom and click **Save and Continue**. Don't have to fill out anything else or it may enable additional review.
54
-
11. You will then be automatically taken to the Scopes page. You do not need to add any scopes here so click Save and Continue to move to the Optional info page. You do not need to add anything to the Optional info page so click Save and Continue which will take you to the Summary page. Click Back to Dashboard.
55
-
12. Click **OAuth consent screen** again and set *Publish Status* to **Production** otherwise your credentials will expire every 7 days.
56
-
13. Make sure **Publishing status** is set to production.
57
-
14. Click **Credentials** in the menu on the left hand side of the screen, then click **Create credentials** (at the top of the screen), then select *OAuth client ID*.
58
-
15. Set the Application type to *Web application* and give this credential set a name (like "Home Assistant Credentials").
59
-
16. Add https://my.home-assistant.io/redirect/oauth to *Authorized redirect URIs* then click **Create**.
60
-
17. You will then be presented with a pop-up saying *OAuth client created* showing *Your Client ID* and *Your Client Secret*. Make a note of these (for example, copy and paste them into a text editor) as you will need these shortly. Once you have noted these strings, click **OK**. If you need to find these credentials again at any point then simply navigate to *APIs & Services > Credentials* and you will see *Home Assistant Credentials* (or whatever you named them in the previous step) under *OAuth 2.0 Client IDs*. To view both the *Client ID* and *Client secret*, click on the pencil icon, this will take you to the settings page for these credentials and the information will be on the right hand side of the page.
61
-
18. Double check that the *Google Assistant API* has been automatically enabled. To do this, select **Library** from the menu, then search for *Google Assistant API*. If it is enabled you will see *API Enabled* with a green tick next to it. If it is not enabled, then enable it.
47
+
4. Click on the field on the left of the screen, **OAuth Consent Screen**.
48
+
5. Select **External** and **Create**.
49
+
6. Set the *App Name* (the name of the application asking for consent) to anything you want e.g. *Home Assistant*.
50
+
7. You then need to select a *Support email*. To do this, simply click the drop down box and select your email address.
51
+
8. You finally need to complete the section: *Developer contact information*. To do this, simply enter your email address (same as above is fine).
52
+
9. Scroll to the bottom and click **Save and Continue**. Don't have to fill out anything else or it may enable additional review.
53
+
10. You will then be automatically taken to the Scopes page. You do not need to add any scopes here so click Save and Continue to move to the Optional info page. You do not need to add anything to the Optional info page so click Save and Continue which will take you to the Summary page. Click Back to Dashboard.
54
+
11. Click **OAuth consent screen** again and set *Publish Status* to **Production** otherwise your credentials will expire every 7 days.
55
+
12. Make sure **Publishing status** is set to production.
56
+
13. Click **Credentials** in the menu on the left hand side of the screen, then click **Create credentials** (at the top of the screen), then select *OAuth client ID*.
57
+
14. Set the Application type to *Web application* and give this credential set a name (like "Home Assistant Credentials").
58
+
15. Add https://my.home-assistant.io/redirect/oauth to *Authorized redirect URIs* then click **Create**.
59
+
16. You will then be presented with a pop-up saying *OAuth client created* showing *Your Client ID* and *Your Client Secret*. Make a note of these (for example, copy and paste them into a text editor) as you will need these shortly. Once you have noted these strings, click **OK**. If you need to find these credentials again at any point then simply navigate to *APIs & Services > Credentials* and you will see *Home Assistant Credentials* (or whatever you named them in the previous step) under *OAuth 2.0 Client IDs*. To view both the *Client ID* and *Client secret*, click on the pencil icon, this will take you to the settings page for these credentials and the information will be on the right hand side of the page.
60
+
17. Double check that the *Google Assistant API* has been automatically enabled. To do this, select **Library** from the menu, then search for *Google Assistant API*. If it is enabled you will see *API Enabled* with a green tick next to it. If it is not enabled, then enable it.
0 commit comments