Invalid Alarm Action

[Ahbrown41]

Invalid Alarm Action

[aceisace]

@Ahbrown41
Hi Alex,
thank you for your interest in this software and for the compliments of the new version :)

I need to take a deeper look to find out where exactly the issue lies. I‘ll get back to this on Monday as I‘m not at home at the moment. On Monday, I‘ll let you know more about it.

For now, could you please tell me what action you‘re using as triggers for events? Thanks in advance

[Ahbrown41]

It appears NONE throws it off. I will look for some examples that are not private :-)

[aceisace]

@Ahbrown41
Thanks for your help. It seems there are quite a few issues with ics.py parsing iCalendar URLs. Although there are fixes available, it would maybe be better to switch to a updated or more advanced library, like the icalendar one (see here). What's your opinion?

[aceisace]

@Ahbrown41
I've more or less understood where the errors are coming from. I'll try finding a fix for this issue and add it in the E-Paper.py file. On the other hand, if you manage to find a way that prevents these errors, please share it here. Thanks in advance

[aceisace]

@Ahbrown41
OK, I've tested out a few things. For now, this is the solution that works:
Could you please try to see if the error from your icalendar persists when using the below snippet? Thanks.

from ics import Calendar, Event
from urllib.requests import urlopen

ical_urls = [
"iCalendar-url"
]

elist = [] #create empty event list
for icalendars in ical_urls:
    decode = str(urlopen(icalendars).read().decode()) #create a string first
    #fix errors related to invalid alarm action
    fix_e = decode.replace('BEGIN:VALARM\r\nACTION:NONE','BEGIN:VALARM\r\nACTION:DISPLAY\r\nDESCRIPTION:')
    ical = Calendar(fix_e)
    for events in ical.events:
        if(time.now().strftime('%Y-%-m') == (events.begin).format('YYYY-M')):
            elist.append(events.name+" on " +events.begin.format('D MMM YYYY'))
print(elist)

[aceisace]

I've tested out the snippet from above which 'bypasses' the invalid Alarm action. I've tested the new snippet for a few days and so far, no errors have shown up. Therefore, I've replaced the old snippet with the new one (from the above comment).

As this issue has been fixed, I'll be closing it now. Should you feel a need to re-open the issue, feel free to do so.