Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Calendar integration does not react to homeassistant.update_entity service #44145

Closed
matejdro opened this issue Dec 12, 2020 · 18 comments · Fixed by #98037
Closed

Google Calendar integration does not react to homeassistant.update_entity service #44145

matejdro opened this issue Dec 12, 2020 · 18 comments · Fixed by #98037
Assignees

Comments

@matejdro
Copy link
Contributor

The problem

When performing homeassistant.update_entity service on Google Calendar, integration will not update.

I understand that under normal circumstances, polling interval is set to 15 minutes to avoid overwhelming Google's servers. But IMO integration should still respond to requests for manual refresh.

Environment

  • Home Assistant Core release with the issue: 0.118.5
  • Last working Home Assistant Core release (if known): /
  • Operating environment (Home Assistant/Supervised/Docker/venv): Docker
  • Integration causing this issue: Google Calendar Event
  • Link to integration documentation on our website: https://www.home-assistant.io/integrations/calendar.google/
@github-actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Mar 12, 2021
@matejdro
Copy link
Contributor Author

matejdro commented Mar 12, 2021

Still happening in 2021.2.0

@github-actions github-actions bot removed the stale label Mar 12, 2021
@github-actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jun 10, 2021
@matejdro
Copy link
Contributor Author

anti stale

@github-actions github-actions bot removed the stale label Jun 10, 2021
@github-actions
Copy link

github-actions bot commented Sep 8, 2021

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Sep 8, 2021
@matejdro
Copy link
Contributor Author

matejdro commented Sep 9, 2021

there has been no changes. Still the same with Home Assistant 2021.9.2

@github-actions github-actions bot removed the stale label Sep 9, 2021
@travipross
Copy link

+1

@github-actions
Copy link

github-actions bot commented Jan 2, 2022

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jan 2, 2022
@matejdro
Copy link
Contributor Author

matejdro commented Jan 3, 2022

Still happening with HA 2021.12.7

@github-actions github-actions bot removed the stale label Jan 3, 2022
@jherby2k
Copy link

I don't really understand why new calendar events show up more or less immediately in the calendar UI / card, but the entity doesn't update, as per https://community.home-assistant.io/t/google-calendar-integration-strange-behaviour/323673/4.

the documentation suggests we can use these calendar entities for triggering automations, but it just doesn't work if the entity doesn't update.

@allenporter
Copy link
Contributor

I've been digging into the calendar integration and re-writing how it works to simplify things. Here is what is going on. There are two paths:

  • Interactive calendar UI path that sends requests live to google to query the calendar
  • Entity path: The entity updates every few seconds/minutes (e.g. so that it can detect the next event has become "active"), but the data refresh happens every 15 minutes and is limited with a throttler.

I have been thinking about how to unify these paths by doing a more efficienct synchronization down to device so both paths use the same data and serve it locally so it is more reliable (proposed design) and also so that its more efficient to implement triggers for automations.

There is not necessarily a simple way to separate out these two notions of entity update. The integration can't tell the difference between a normal refresh and a forced update as far as I know to know to allow a data fetch.

@swiergot
Copy link
Contributor

Related issue (sadly closed as stale): #57128

@allenporter
Copy link
Contributor

One quick update: Google calendar now syncs down data to local (when not using search) and so the UI view and state are in sync. However, there are still two separate update mechanisms because the state represented by the calendar and the "next event" are separate. I don't see a simple solution yet to make this work better.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@matejdro
Copy link
Contributor Author

matejdro commented Apr 8, 2023

This is still relevant issue.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@matejdro
Copy link
Contributor Author

matejdro commented Jul 7, 2023

This is still an issue in Home Assistant 2023.6.3

@allenporter
Copy link
Contributor

Assigning this to myself as I finally understand the solution to this problem.

@github-actions github-actions bot locked and limited conversation to collaborators Sep 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
5 participants