Read the statement by Michael Teeuw here.
MMM-CalendarEXT: Not Showing Latest Private Google Calendar Feed
-
So, I can’t use the Secret address from google? Sorry if I wasn’t clear, that is the address I was using to get the ical file to confirm the difference between events.
Would rather not make this particular calendar public.
Thanks again
-
Correctly identified,
if someone puts out a code with which you can sign up as a google user, that would be great. -
@cccp402
For MMM-CalendarExt(not MMM-CalendarExt2), checkredrawInterval
of system parts andinterval
of calendar parts in configuration. -
@sean Great, I’ve adjusted those values, and will see if that addresses what I’m experiencing.
Is there a cache of the previously accessed ics file somewhere in the system? I am still seeing the old version of the calendar, prior to the event modifications.
-
@cccp402
There is no cache.
Can you share the .ics URL to examine details? My email iseouia0819@gmail.com
. -
@Sean Hi, something is definitely wrong with the default calendar module. It worked for me when I installed a few weeks ago but recently I did a fresh install and noticed the calendar displays "No upcoming events’ no matter ics file or url I use. Public URLS and my own ICS work using other methods and definitely have data populated but the mirror/module shows "No upcoming events’ no matter what. Actually tomorrow is presidents day and still nothing. Could you please check into this for us? Thanks.
-
@anthony6608 the default holiday Cal only had 2017 & 2018 holiday events.
There is a new one for 2019. Just posted earlier today in one topic
See https://forum.magicmirror.builders/post/52595Also, open the dev console
npm start dev
And look for errors in the console tab
-
@anthony6608
Are you talking about my module (MMM-CalendarExt) or default calendar module? I’m slightly confused. -
@Sean Sorry, referring to the default calendar. Now I notice my MM is complaining about addr/port already In use. Do you know anything about troubleshooting that error?
-
u have to stop the MM instance before starting the debug instance… can’t run two at the same time