Google Calendar Component setup fails

Configuration
1

So finally my frustration got the better of me and I’m posting my problem :wink:

I had my calendar working in a previous install of HA… But after a fresh install I decided to add google assitant first. I got this working and no issues there.

I even got the calendar component access (with the code in the notification) and thought that was it… But my calendar card would not stop loading. Eventhough I could see my upcoming event in the state of my calendar (developer tools - states).

I figured something went wrong with my authentication so I removed the google token from the config folder and did a reauth on a brand new project (so with new credentials) and got the verification code again… so far so good.

Because the google_calendars.yaml remained empty I restarted the server again.

only to discover that a new notification told me:

The following components and platforms could not be set up:

google 

Please check your config.

I can’t figure out what I am doing wrong, So I was wondering if it is the multiple auth methods… But seeing that it is advised to use multiple authentictions for different components I’m really at a loss here.

All help would be appreciated!

2

Did you delete the .google.token hidden file?

1 Like
3

Yes I did, this was needed to get a new auth code. BUt after that I still had the same issue.

4

I missed the part where you installed Google Assistant something I don’t have, but do see that if you migrated from HA 80 or below the documentation contains a few steps to get it all back in sync. https://www.home-assistant.io/components/google_assistant/

I don’t have the google token in my configuration but do have a google client id. Did you by chance mix them up?

5

Well I do have my calendar showing up as entity where the state is off and events are showing for tomorrow.

So it does not seem to be related to the google assistant. I’ll try removing some other elements to see if that works

6

It’s getting late but i think it has something to do with the domain. On the internal non https ip adress version the calendar works… on the https duckdns it doesn’t

dont know why but hey atleast it working onn the network