Read the statement by Michael Teeuw here.
Calendar module events stop displaying before due time/date
-
I created a new event for tomorrow:
BEGIN:VEVENT
CREATED:20200806T005525Z
DTSTAMP:20200806T005659Z
LAST-MODIFIED:20200806T005659Z
SEQUENCE:3
UID:ffae8dff-cd39-4315-977c-762a0b47544c
DTSTART;TZID=Australia/Sydney:20200724T082500
DTEND;TZID=Australia/Sydney:20200724T092000
SUMMARY:NEW P1 - LESSON (ROOM No.)
RRULE:FREQ=WEEKLY;COUNT=5;INTERVAL=2;BYDAY=FR
LOCATION:XXXX
END:VEVENTLook at CREATED:20200806T005525Z. This is 12.55am, right? I created this at about 10.55am, so a 10hr time diff - AEST <> GMT.
Is this relevant?
-
@castletonroad shouldn’t matter, in my opinion
-
@castletonroad I recommend opening an issue on the MagicMirror GitHub issue page. there is work going on the resolve calendar problems now
-
Will do.
BTW, I created two new recurring events (new lessons 1 and 2) on my iPhone, then edited the recurrence specifics on the NextCloud calendar app web page (as the iPhone is limited in the ‘custom’ options for events it offers). This morning, neither of the new events showed on the Mirror, so same problem.
I then created a new NON-recurring event on my iPhone (start at 09.20), and restarted the MM - the event showed.
I then used my iPhone to make the event RECURRING, and restarted the MM - the event DOES NOT show.
I THEN set the start to be 10.30 (vs. 09.20) - and the recurring event showed on the MM again!
10.05 - the recurring event shows.
10.00 - the recurring event shows.
09.55 - the recurring event DOES NOT show.
I then removed the recurrence - the event shows again.
So definitely something to do with event recurrence AND timezones. A recurring event starting within my TZ difference from midnight does not show.
What do you think?
Thanks for your help with this :)
-
@castletonroad add that to the issue. make an ics for both with/without recurrence. add to the issue.
guys are looking for recreatable things to test against.
this is really my fault. I opened an issue last year, as we were have cal problems, but using old code. the team updated to the latest library code, which fixed some problems, but has caused more
-
-
@castletonroad awesome! thank you
