here is an UPDATED test version of the fixes for all kinds of calendar date problems.

NOTE: the changed branch name
NOTE: this used the node-cal@0.19.0 library UNCHANGED

best to make a new folder and git clone there

git clone https://github.com/sdetweil/MagicMirror
cd MagicMirror
git checkout fixcaldates2 // <------ note this is a changed branch name
npm run install-mm
copy your config.js and custom.css from the prior folder
and the non-default modules you have installed…

this ONLY changes the default calendar
but DOES ship an updated node-ical library too

if you need to fall back, just rename the folders around again so that
your original is called MagicMirror

all the testcases for node-ical and MagicMirror execute successfully.

the ‘BIG’ change here is to get the local NON-TZ dates for the
rrule.between()

all the checking and conversion code is commented out or not used
the node-ical fixes are for excluded dates (exdate) values being adjusted for DST/STD time… waiting to submit that PR

one fix in calendar.js for checking if a past date was too far back,
but it never checked to see IF the event date was in the past… (before today) so it chopped off too many

and one change in calendarfetcher.js to put out a better diagnostic message of the parsed data… (exdate was excluded cause JSON stringify couldn’t convert the complex structure)

I added the tests you all have documented

please re-pull and checkout the new branch (I deleted the old branch)
and npm run install-mm again

is this on the edited calendar.js or the develop branch?

im on a trip til tuesday

I noticed that multi fullday events will be shown one day in the past:

This is from today (20. Sep)

I don’t have the config to show past days enables.

remember to do (to get release level dependencies)

npm run install-mm

assuming the config in this MM is set correctly for sliceMultiDayEvents

hopefully we will get it into next release Oct 1.

and a testcase

Thx for your help.

change calendar.js 3 places
give it a try

change (line 633)

const maxCount = Math.ceil((event.endDate - 1 - moment(event.startDate, "x").endOf("day").format("x")) / ONE_DAY) + 1;

to

const maxCount = Math.round((event.endDate - 1 - moment(event.startDate, "x").endOf("day").format("x")) / ONE_DAY) + 1;

ceil takes 1.04 to 2, round to 1

					let midnight
						= moment(event.startDate, "x")
							.clone()
							.startOf("day")
							.add(1, "day")
							.endOf('day')  // add this (else its start of day, not end) line 641
							.format("x");

and recalc of midmnight (line split like above for clarity) line 654

	midnight = moment(midnight, "x")
                                   .add(1, "day")
                                   .endOf('day')  // add this 
                                   .format("x"); // next day

works in Europe/Berlin and America/Chicago 
2 bugs
1 count incorrect
2 loop control

btw: I have this problem for a long time and more or less always ignored it.

sliceMultiDayEvents

thanks for the config

looking at the results without sliceMultiDayEvents
I see

so the parsing was correct, the visual, we only show the start date, even if multi-day
so both are ‘correct’ tho not informative

with split day

I don’t see any difference in the calendar parsing. (add “DEBUG” to the loglevel list in config.js)
and redirect the npm start output to a file

Calendar-Fetcher: Broadcasting 4 events from http://localhost:8090/modules/default/calendar/splitdays_test.ics. 

only 4 events… so not calendar parsing,
the only place the split parm is used is in the front end… calendar.js
but my output is different than yours.

I am using the develop branch, coming Oct 1. however I don’t see a documented change here
this split code was added in 2019…
also tested on master (2.28.0) with same 4 lines of results

you can get the develop branch and try it…
https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code

I just copy/pasted your ics info in a file, unchanged

I tested with America/Chicago timezone.