Google Calendar

This section explains how to generate a client ID and client secret on Google Developers Console.

1. First, go to the Google Developers Console to enable Google Calendar API .
2. Select Create project, enter a project name and select Create.
3. Enable the Google Calendar API.
4. Navigate to APIs & Services (left sidebar) > 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.

If the above My button doesn’t work, you can also perform the following steps manually:

• Browse to your Home Assistant instance.

• Go to Settings > Devices & Services.

• In the bottom right corner, select the Add Integration button.

• From the list, select Google Calendar.

• Follow the instructions on screen to complete the setup.

1. Continue through the steps of selecting the account you want to authorize.

2. NOTE: You may get a message telling you that the app has not been verified and you will need to acknowledge that in order to proceed.

3. You can now see the details of what you are authorizing Home Assistant to access with two options at the bottom. Select Continue.

4. The page will now display Link account to Home Assistant?, note Your instance URL. If this is not correct, refer to My Home Assistant. If everything looks good, select Link Account.

5. You may close the window, and return back to Home Assistant where you should see a Success! message from Home Assistant.

• all_day: true/false if this is an all day event. Will be false if there is no event found.
• message: The event summary.
• description: The event description.
• location: The event location.
• start_time: Start time of event.
• end_time: End time of event.

A calendar target is selected with a Target Selector and the data payload supports the following fields:

This is a full example of an action in YAML:

action: google.create_event
target:
  entity_id: calendar.device_automation_schedules
data:
  summary: "Example"
  start_date: "2022-10-1"
  end_date: "2022-10-2"

The integration supports additional configuration from a file google_calendars.yaml which is available for existing users before version 2022.06. This file is no longer automatically populated.