-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
Comments
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. |
Still happening in 2021.2.0 |
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. |
anti stale |
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. |
there has been no changes. Still the same with Home Assistant 2021.9.2 |
+1 |
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. |
Still happening with HA 2021.12.7 |
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. |
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:
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. |
Related issue (sadly closed as stale): #57128 |
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. |
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. |
This is still relevant issue. |
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. |
This is still an issue in Home Assistant 2023.6.3 |
Assigning this to myself as I finally understand the solution to this problem. |
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
The text was updated successfully, but these errors were encountered: