Olen
Olen
Have you looked at the actual ical-file you are parsing? Sometimes cancelled events will still show up in the ical files, even if they are removed from other (3. party)...
Why do you add the `extract_offset` lines? There should not be a time-offset in the description or location fields?
> > Why do you add the `extract_offset` lines? There should not be a time-offset in the description or location fields > > True, I just copied the row above...
The "offset" thing was not invented by me or tybritten or the ical-integration. It was a "hack" in the original google-calendar integration to make a way to trigger automations before...
There is also a similar line here: https://github.com/tybritten/ical-sensor-homeassistant/blob/f5c17bea1fdcad1831317b6b0de63c48a8643736/custom_components/ical/__init__.py#L112 Which should also get description and location I guess
> > There is also a similar line here: > > https://github.com/tybritten/ical-sensor-homeassistant/blob/f5c17bea1fdcad1831317b6b0de63c48a8643736/custom_components/ical/__init__.py#L112 > > > > Which should also get description and location I guess > > Without the four...
Can't you use the "calendar.ical_xxxx" for that?
Yes. The calendar entity state is always related to the next (or current) event. It works the same as e.g. https://www.home-assistant.io/integrations/google/#using-calendar-in-automations
You need to update to the latest version of this integration.
I have never seen a calendar entry that goes to (or from) 24:00:00. All full day events in my calendar starts at 00:00:00 on the day of the event and...