Recurring events Calender

bhepler

@mr_moore - Just to be sure, you did set the location of your Pi using the raspi-config tool or going through the UI system configuration? That’s a likely culprit.

By default, the Raspbian OS thinks it is British. I have to set the time zone, language and keyboard first thing after every OS flash. If I don’t, the keyboard special characters are all off, I can’t get my passwords to work, and it thinks football is played without helmets.

Mr_Moore

@bhepler - I have the right time zone. The clock is correct. And if i have a one time appointment in the Google Calender it wil show the correct time at the MM. It is only when i have recurring events that it will show two hours wrong.

bhepler

@mr_moore - Hmm. Can you check the recurring events through Google’s interface and make sure the time zones on those events is correct?

Mr_Moore

@bhepler everything looks ok in Google Calender. See snapshots from Google and Mirror. Two reccuring events and one with only this day.

MajorC

@Mr_Moore said in Recurring events Calender:

@bhepler everything looks ok in Google Calender. See snapshots from Google and Mirror. Two reccuring events and one with only this day.

Did you solve this problem? I have the same one at the moment.

sdetweil

@MajorC did u install the temp calendar fixes from the troubleshooting section?

MajorC

Sorry, what? Can you provide me a link?

sdetweil

@MajorC temp calendar fixes from the troubleshooting section?

the troubleshooting section of the forum, the topics are pinned to the top

================================================================

note

these temp fixes were for 2.12

all the fixes are now in 2.13 (or the latest develop branch, see below)

dawookie1979

@sdetweil did you manage to fix this? I have similar issues, mine being 1 hour early ;)

sdetweil

@dawookie1979 if you load the develop branch, it has all the fixes

if manual install

cd ~/MagicMirror
git checkout develop

if my install script

cd ~/MagicMiror
git fetch origin develop:develop
git checkout develop

restart MM normally

if u see that package-lock.json has changed, preventing the checkout, do
git checkout package-lock.json

then restart the above