Fixed: Google Calendar not initializing "takes exactly one argument"

In the past HASSIO upgrade between 95 and 97 my google calendars have stopped working, but I can’t see mention of calendars changing in the release notes.

I’ve removed the /config/.google.token and reauthenticated but the following error persists.

Any ideas?

2019-08-16 12:48:57 ERROR (MainThread) [homeassistant.components.calendar] Error while setting up platform google
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/", line 149, in _async_setup_platform
    await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
  File "/usr/local/lib/python3.7/asyncio/", line 442, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/google/", line 34, in setup_platform
    for data in disc_info[CONF_ENTITIES] if data[CONF_TRACK]])
  File "/config/custom_components/google/", line 34, in <listcomp>
    for data in disc_info[CONF_ENTITIES] if data[CONF_TRACK]])
  File "/config/custom_components/google/", line 47, in __init__
    super().__init__(hass, data)
TypeError: object.__init__() takes exactly one argument (the instance to initialize)

google_calendars.yaml has entries like this…

- cal_id:
  - device_id: movie_releases
      ignore_availability: true
      name: Movie Releases
      track: true

I’m using 97.1 on HassOS 2.11 on a Pi.

There war a custom google component I used. I’m not sure of the purpose or source. It might have been to get more events per calendar. Hmm.

Can’t see a source to update / test with.