jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-08 18:06:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Google Calendar's scenario 2 instructions (#37549)

Browse Source
This commit is contained in:
Stuart McCroden 2025-04-14 15:10:24 -05:00 committed by GitHub
parent 942198773c
commit 593f3b423d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 25 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

50
source/_includes/integrations/google_client_secret.md
View File

@ -26,29 +26,29 @@ This section explains how to generate a client ID and client secret on
3. **Enable** the {{ api }}.
4. Navigate to **APIs & Services** (left sidebar) > [Credentials](https://console.cloud.google.com/apis/credentials).
5. In the left sidebar, select **OAuth consent screen**.
- Select **External** and **Create**.
- Set the **App name** (the name of the application asking for consent) to anything you want, e.g., *Home Assistant*.
6. You then need to select a **Support email**.
- From the dropdown menu, select your email address.
7. Under **Developer contact information**, enter your email address (the same as above is fine).
8. Scroll to the bottom and select **Save and continue**.
- You don't have to fill out anything else here. Adding other information to this page (like an app logo) may trigger an additional review process from Google and delay setup by days.
9. You will then be automatically taken to the **Scopes** page.
- You do not need to add any scopes here. Select **Save and continue** to move to the **Test users** page.
- You do not need to add anything to the **Test users** page. Select **Save and continue**, which will take you to the **Summary** page.
- Select **Back to dashboard**.
10. Select **OAuth consent screen** again and under **Publishing status**, select **Publish app**.
- Otherwise your credentials will expire every 7 days.
11. Make sure **Publishing status** is set to **In production**.
12. In the left sidebar, select **Credentials**, then select **Create credentials** (at the top of the screen), then select **OAuth client ID**.
13. Set the **Application type** to **Web application** and give this credential set a name (like "Home Assistant Credentials").
14. Add `https://my.home-assistant.io/redirect/oauth` to **Authorized redirect URIs** then select **Create**.
- This is not a placeholder. It is the URI that must be used.
15. 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 them shortly.
- Once you have noted these strings, select **OK**.
- If you need to find these credentials again at any point, then 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**, select 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.
16. Congratulations! You are now the keeper of a client secret. Guard it in your treasure box. In most cases your new credentials will be active within a few moments. However, Google states that activation may take up to five hours in some circumstances.
6. It will take you to the Overview page and ask for **Project Configuration**:
- Complete the App Information:
- Set the **App name** (the name of the application asking for consent) to anything you want, for example, *Home Assistant*.
- For a **Support email**, choose your email address from the dropdown menu.
- Click **Next**.
- For Audience, select **External** then click **Next**.
- Under Contact Information, enter your email address (the same as above is fine). Click **Next**.
- Read the policy and check the box if you agree. Click **Continue**.
- Click **Create**.
7. In the left sidebar, select **Audience**:
- Under **Publishing status > Testing**, select **Publish app**.
> Otherwise, your credentials will expire every 7 days.
8. In the left sidebar, select **Clients**:
- Click **+ Create Client**.
- For Application type, choose **Web Application** and give this client ID a name (like "Home Assistant Client").
- Add `https://my.home-assistant.io/redirect/oauth` to **Authorized redirect URIs** then select **Create**.
> **Note**: This is not a placeholder. It is the URI that must be used.
- Click **Create**.
9. Find the client you just created. Under the Actions column, choose **Download OAuth client** (download icon), which will show you the **Client ID** and **Client Secret**.
- Make a note of these (for example, copy and paste them into a text editor), as you will need them shortly.
- Once you have noted these strings, select **Close**.
- Congratulations! You are now the keeper of a client secret. Guard it in your treasure box. In most cases, your new credentials will be active within a few minutes. However, Google states that activation may take up to five hours in some circumstances.
> If you need to find these credentials again at any point, then 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 the **Client ID** and **Client Secret**, click the **Download OAuth client** (download icon) under the Actions column.
{% enddetails %}