Read the statement by Michael Teeuw here.
MMM-GoogleCalendar Not Loading
-
@nuggetron22 I do not know about that module.
but Ext3 gets its events from the default calendar. it does not read from the source. -
Something seems to be wrong with v2.26.0 on how it reads in calendars. I’m not much of a coder for stuff like this, but I stumbled my way through reverting to v2.23.0 and the basic calendar module can now read my Google Private iCal file where it couldn’t on v2.26.0. I’ll try it with Ext3 and the GoogleCalendar module tomorrow and see if they work too.
-
-
ETIMEDOUT
generally happens when the server is busy, or the connection is extraordinarily slow. To prevent it,keep alive
header is recommended. (Not sure that is the reason, anyway.) -
CX3* can also be fed from MMM-GoogleCalendar. But by compatibility issues due to unmatched format, broadcasts from MMM-GoogleCalendar should be converted before consumption.
-
You can alternatively try
MMM-CalDAV
+default calendar module
instead ofMMM-GoogleCalendar
if you still have issues.
-
-
@nuggetron22 yes 2.26 has a problem w calendar parser
do thia
cd ~/MagicMirror npm install node-ical@0.16.1
restart MagicMirror
-
@sdetweil
I’ve reverted back to MM v2.23.0 and got this to work. I’m also trying to integrate it with MMM-CalenderExt3 and having some difficulties there. Still learning what needs to be updated to make them talk to each other.I’ll try going back to v2.26.0 and install the node-ical@0.16.1 and see if that fixes the calendar parser issue. Thanks for the quick replies all!
-
@nuggetron22 calendar Ext3 gets its info from the default calendar.
so the url goes there. get it working first
then comment out it’s position propertythen add Ext3 and customize
-
Alright, I went back to v2.26.0 and tried the
cd ~/MagicMirror npm install node-ical@0.16.1
but it didn’t resolve my calendar issues. I was getting all of my Google Calendars, whether in the default or the MMM-GoogleCalendar module, on v2.23.0. I couldn’t get my calendars on v2.26.0, v2.25.0, or v2.24.0. They all gave me ETIMEDOUT errors during the Fetch.
Back to v2.23.0 and I can get all of my Google Calendar either in the default calendar module or the MMM-GoogleCalendar module.
-
@nuggetron22 yes, this is probably a fetch problem in electron.
seems it gets confused when there is an ipv6 and an ipv4 address on the network interface and demands connection a certain way…others have had success disabling the ipv6 address on their pi… as its only inside the house, you’ll likely never exceed the number of devices…
-
@nuggetron22
I have the same problem with my Google Calendar, how do I get version 2.23.0?
Do I have to set up the SD card from scratch or can I go from version 2.26.0 to 2.23.0 in a simple way?What’s the best way to go about downgrading the magic mirror software but keeping all modules intact?
-
@sil3ntstorm do
cd ~/MagicMirror git fetch --all --tags rm package-lock.json git checkout tags/v2.23.0 -b temp_branch rm -rf node_modules rm _rf ../fonts/node_modules rm -rf ../vendor/node_modules npm run install-mm