You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is 17:05 currently. Loadshedding ended at 16:30, but the two calendars that are published using this integration still show the start_time and end_time as 14:00 and 16:30 respectively as in the image below.
However, when you click on the Calendar in the HA side bar, the calendar is aware that the next next load shedding event is at 22:00.
Is it possible for the integration to update the two calendars once a current shed has completed so that the start_time and end_time is updated to the next load shedding event? Although the integration is set to update every hour, I think it would be great if this can be done based on the current end_time of the current calendars. The idea is not to poll the API when this happens (although this would be a configurable nice-to-have), the only action that should happen after the end_time is reached is to update the calendars to the next event.
This will allow the calendar to immediate reflect the next load shedding time so that the relevant automations, reporting, etc can be accurate and not having to wait an hour or 30min or whatever for this to happen.
The text was updated successfully, but these errors were encountered:
It is 17:05 currently. Loadshedding ended at 16:30, but the two calendars that are published using this integration still show the start_time and end_time as 14:00 and 16:30 respectively as in the image below.
However, when you click on the Calendar in the HA side bar, the calendar is aware that the next next load shedding event is at 22:00.
Is it possible for the integration to update the two calendars once a current shed has completed so that the start_time and end_time is updated to the next load shedding event? Although the integration is set to update every hour, I think it would be great if this can be done based on the current end_time of the current calendars. The idea is not to poll the API when this happens (although this would be a configurable nice-to-have), the only action that should happen after the end_time is reached is to update the calendars to the next event.
This will allow the calendar to immediate reflect the next load shedding time so that the relevant automations, reporting, etc can be accurate and not having to wait an hour or 30min or whatever for this to happen.
The text was updated successfully, but these errors were encountered: