@sdetweil Hi Sam,
thanks very much for your great scripts. They really work like charm!

Basic installation of the MagicMirror really worked without any issue using your scripts.
I am just fighting with some modules, which are obviously not up to date, but that’s a different story.
At least I found the root cause of an issue with MMM_systemtemperature and I hope that I could help some other beginners who struggled with that module and did not get support in corresponding forum up to now…or just misunderstood the instructions in the forum.

I want to thank you so much for the great work you are doing for the MM community!

@sdetweil Thanks for the hint!
I tried to use the same backup on a different SD card, showed the same issue.
Maybe I need to set it up from scratch on a different card…

Hi guys,
after 1.5 years I thought that it would be time to update my Magic Mirror to version 2.18.0, including node.js and electron.
But now when I want to start it, I face the following issue:

pi@raspberrypi:~/MagicMirror $ npm start
magicmirror@2.18.0 start
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js
sh: 1: ./node_modules/.bin/electron: Permission denied

I also used Sam’s scripts to update: [https://github.com/sdetweil/MagicMirror_scripts]…but it did not work either.

Even changing the owner and reinstalling electron did not work:
pi@raspberrypi:~ $ sudo chown -R pi MagicMirror
pi@raspberrypi:~ $ npm install electron --unsafe-perm=true

Has anybody further ideas how to make it work again? Thanks so much!

@ I have a Raspberry Pi 3 Model B

@sdetweil This morning we switched from DST to STD time. No issue at all with the calendar, everything works fine!
Again, thanks very much for your support!

@sdetweil
Wow, thank you so much for your great support!

@sdetweil
Thanks for the example. Looks like a next project for me… :thumbs_up:

@sdetweil
Thanks very much for your help! I highly appreciate it!

@sdetweil
Sorry for asking:
If I would import a calendar file from a text file, it would be easy to do the correction (change DTEND or remove BYDAY) in any text editor.
But how to proceed if I directly import data from *.ics link? Is there any ‘hack’ I could apply?
Thanks very much for your patience… All other data are really great now! And somehow I rely on a 3-weekly whole day, as we use to have 3-week iterations in our SCRUM process…

@sdetweil
As I wondered if the format of an 3-weekly event in ical has an issue, I set up a 3-weekly event in Google calendar and compared the files:

BEGIN:VEVENT
DTSTART;VALUE=DATE:20201005
DTEND;VALUE=DATE:20201006
RRULE:FREQ=WEEKLY;INTERVAL=3;BYDAY=MO
DTSTAMP:20201005T195008Z
UID:835F136F-35A4-44C6-AA16-481F02E5A2D1
CREATED:20201005T120626Z
DESCRIPTION:
LAST-MODIFIED:20201005T120626Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:3-weekly whole day test
TRANSP:OPAQUE
END:VEVENT

Event has been set to 5th of October and DTEND is also one day later than DTSTART for a whole-day-event and it also shows a BYDAY, that means it’s absolutely identical to the ical file…

@sdetweil
All whole day events start at the right day and end one day later. There is no difference in the calendar file, whether it is a weekly, 2-weekly or 3-weekly event.
That’s why I do not understand, why weeklies and 2-weeklies are shown correctly and the 3-weekly is shown one day too late…

@sdetweil
Wow, that looks great! Thanks very much for your endurance!

There is only that persistent ‘3-weekly whole day’ problem. It’s still one day too late. Most probably that’s so difficult, as it is a user defined interval, something strange seems to bring the parser to a wrong date…
For testing, I have added a 3-daily event. This shows correct start/end…

But the rest is great! Thanks very much!!!

@sdetweil
3-weekly whole day now shows Okt 23, but it should be Okt 22

As I have seen in the calendar file, switching from DST to STD time is correctly defined for last Sunday in October, that is 25th of October. So this should not influence an event on 22nd of October…

Regarding events after switching from DST to STD time, I don’t have a clue, as I am not a dev, just a little experienced in testing…
I tried to understand the calendar file. As far as I have seen, you have only the date for whole day events (without any time):

BEGIN:VEVENT
CREATED:20201001T205859Z
DTEND;VALUE=DATE:20201023
DTSTAMP:20201001T205900Z
DTSTART;VALUE=DATE:20201022
LAST-MODIFIED:20201001T205859Z
RRULE:FREQ=WEEKLY;INTERVAL=3;BYDAY=TH
SEQUENCE:1
SUMMARY:3-weekly whole day
UID:D718FE41-FF1B-43F6-9442-E9E43A41CCF0
URL;VALUE=URI:
END:VEVENT

In this case DTSTART is 20201022 and DTEND is 20201023.

For whole day events, can’t you simply set:
‘Begin’ to value of DTSTART 00:00 and
‘End’ to value of DTEND - 1day 23:59? (just as ical most probably uses 24:00 and that’s one day later)

Maybe it’s not as simple as I assume, otherwise you would have tried that already…

As we currently have TZOFFSET+0200 and switch to TZOFFSET+0100, I would rather expect that we see current events (planned after 25th Oct) on the monitor 1 hour too late.
So that’s why I currently would rather expect:
Oct 27th 01:00 - Oct 28th 00:59 for weekly whole day after switching to STD time instead of
Oct 26th 23:00 - Oct 27th 22:59

But as I mentioned before, maybe everything is much more complicated than I ever can imagine…

@sdetweil
I am currently not sure how this will look like after changing from DST(UTC+2) to STD time(UTC+1).
For sure this will happen on sunday, 25th of October. That’s why whole day events starting on 26th look differently.
But how should it look like today? Oct 26th 01:00 - Oct 27th 00:59???

@sdetweil

now I have corrected my calender entry, but I still cannot see same date for ‘3-weekly whole day’ and ‘3-weekly 13-14’.
Do you see same date for these events?
Any idea what I do wrong? Thx very much!

Ok, then it’s my error again. In the meantime I have corrected my calendar entry. Would you need a new calenendar export, or would you like to send me your fix to test it here?

@sdetweil
It’s getting better and better, great!

The only event, which is not correct yet, ist the 3-weekly 13-14. This should be in 21 days (Oct 22nd), exactly like the 3-weekly whole day. The following ones could be better controlled in an absolute time format…

@sdetweil
I would not mind to see 23:59 as end of a whole day event, but it would also be fine for me to see the day where it starts again…

@sdetweil
maybe you expected already that now the endTime of each whole day event is shown one day too late. Without that fix, it has been correct.

Regarding the ‘3-weekly whole day’ you gave me a perfect hint: As it is a user configured interval, you have to take care that begin of the event and day of the week you select as interval correspond. So if you configure it wrong, corresponding event will obviously not be shown, as you explained perfectly from your code analysis…

Hello Sam,
thanks very much for your great support.
Good news is that the endTime issue is solved now!

Nevertheless with recurring whole day events, the following entries are not correct yet:

3-weekly 13-14 is completely missing (should be 1.Okt)

Starting with the 3-weekly whole day 22.Okt (should be 21.Okt), every following ‘whole day meeting’ is shown one day too late.
You can easily see that even on your picture, as e.g. the 3-weekly whole day and the 3-weekly 13-14 should always take place at the same date.

Even on your picture this is not the case… monthly whole day is shown in 3 days, monthly 17-18 is shown in 4 days.

Once more, thanks for your great support so far!

You are right, now in summer, we are GMT+1, in winter it’s GMT+2…