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
BEGIN:VEVENTDTSTAMP:20211209T101739ZUID:[email protected]SUMMARY: Achtung: Restmülltonne, XXXXstr. YY
DTSTART;TZID=Europe/Berlin;VALUE=DATE:20220106
DTEND;TZID=Europe/Berlin;VALUE=DATE:20220106
LOCATION:XXXXstr. YY
DESCRIPTION:Im Zeitraum 18.12.2021 bis 11.01.2022 kann es wegen der Feiertage vorkommen, dass wir Ihre Tonnen vor oder nach dem gewohnten Termin leeren.
STATUS:CONFIRMEDBEGIN:VALARMTRIGGER:-PT15H
ACTION:DISPLAYDESCRIPTION:Restmülltonne, XXXXstr. YY
END:VALARMEND:VEVENT
Setting up a calendar that detects those events (by filtering for contains: Achtung for instance) correctly provides the next event in the sensor, but no state attribute contains the text in the DESCRIPTION field of the ics event. Instead, the attribute "description" seems to contain the summary.
I love this integration, it should be stock in Home Assistant! Thank you!
The text was updated successfully, but these errors were encountered:
true .. ICS isn't very strictly defined .. most provider have the text in summary and not in description for what ever reason.
But you're welcome to add the 2nd field and submit a pull-request :D
With an ics file containing events like this:
Setting up a calendar that detects those events (by filtering for
contains: Achtung
for instance) correctly provides the next event in the sensor, but no state attribute contains the text in the DESCRIPTION field of the ics event. Instead, the attribute "description" seems to contain the summary.I love this integration, it should be stock in Home Assistant! Thank you!
The text was updated successfully, but these errors were encountered: