I’ve followed this google calendar guide, but unable to validate the configuration after inputting these lines in the configuration.yaml file. There is no error. The check just keep spinning. I have tried to place in different parts of the file with same results.
google:
client_id: !secret google_calendar_id
client_secret: !secret google_calendar_secret
track_new_calendar: true
Somehow I’m having issues as an hour ago. I have Google Calendars working a few months now (and had to reauthenticate once).
I deleted the .google token file (which usually solves this re-authentication issue). After that I got the authentication prompt again, but Home Assistant does not create the google_calendars.yaml file. I then created a new API and did the process again. Got the authentication again, but still no yaml file. Restarted HA a bunch of times and also reverted to my previous client id and secret.
Something is definitely not right…
Thanks for the report. I don’t know if our issues are related, but I cannot get pass step 1. If I only enter google: in the config, validation just keeps spinning.
If I enter a bogus:, I get this error.
Component error: bogus - Integration 'bogus' not found.
Am I suppose to install something in the add-on store?
Did you check the logs what else might be there? Mine say this:
Logger: homeassistant.core
Source: components/google/__init__.py:349
First occurred: 9:14:16 (1 occurrences)
Last logged: 9:14:16
Error executing service: <ServiceCall google.scan_for_calendars (c:0d7d56b14fc945b5912f9c1c2678a9cf)>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/core.py", line 1276, in catch_exceptions
await coro_or_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1299, in _execute_service
await self._hass.async_add_executor_job(handler.func, service_call)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/google/__init__.py", line 257, in _scan_for_calendars
service = calendar_service.get()
File "/usr/src/homeassistant/homeassistant/components/google/__init__.py", line 349, in get
"calendar", "v3", http=http, cache_discovery=False
File "/usr/local/lib/python3.7/site-packages/oauth2client/_helpers.py", line 133, in positional_wrapper
return wrapped(*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/googleapiclient/discovery.py", line 237, in build
raise e
File "/usr/local/lib/python3.7/site-packages/googleapiclient/discovery.py", line 229, in build
requested_url, discovery_http, cache_discovery, cache)
File "/usr/local/lib/python3.7/site-packages/googleapiclient/discovery.py", line 279, in _retrieve_discovery_doc
raise HttpError(resp, content, uri=actual_url)
googleapiclient.errors.HttpError: <HttpError 429 when requesting https://www.googleapis.com/discovery/v1/apis/calendar/v3/rest returned "Too Many Requests">
This thread came up when I searched for my error, Too many requests.
I’ve had issues with errors from the Google Calendar before, but I think this is new.
My calendar (mostly) works usually.
Since tonight (00:30 european time. almost 12 hours ago now) I get this error at least every minute, or more often.
Calendar does not work any more.
In google dev console I do not see requests or errors.
@der-optimist and @lindsayward please report/confirm your issue on the Github tickey below as well (I created that issue on Github). That way the HA team can investigate more.
I don’t see any errors related to google.
I also woke up this morning to this error. I tried completely scrubbing the integration and redoing it but that didn’t work either. Hopefully, what even it is gets sorted I really enjoy this integration.
Please confirm your issue here: https://github.com/home-assistant/core/issues/37874#issuecomment-658645516
edit: for people how might see this thread: this issue (that I was describing) has been fixed (see githhub).
No. I’ve ditched the project.
I removed my HOA device from the devices that have access to my google account.
then enabled the Google CalDev and Google Calendar API and it worked