Read the statement by Michael Teeuw here.
ICS file events not displayed
-
@pappastech in the startup messages we put out a message w how many events we are sending out, by url
-
@pappastech you have a typo
-
pastEvents
-
@sdetweil Yes and it says that there’s 28 events being broadcast currently while there are 119 instances of “BEGIN:VEVENT” in the ICS file though many are recurring events. Does the broadcast count represent unique events or would there be a single increment for 10 unique events that are part of a single recurring event?
-
@sdetweil Doh! Well, that fixed the past events not showing up. I looked at that line 20 times and missed that typo; curious that it didn’t show an error in the logs. Still trying to find a solution for the recurring events not showing up.
Thanks.
-
@pappastech we dont put out messages for unexpected properties
if you add
,"DEBUG"to the logLevel property at the top of config.js
and run MagicMirror like this
npm start >somefile.txt
run til the cal appears
then quit and examine the somefile.txt
you can see the event processing -
@sdetweil I did that earlier and everything looks fine. The recurring events show up in the log and it shows them successfully processing just like the other events that show up on the display. I don’t see any difference between the ones that show up and ones that do not.
My wife likes to add images to event titles but they show up fine on the events that do display. Is there any limitation with respect to that? There’s no difference that I see otherwise.
-
@pappastech display where? the default cal doesnt
-
the issue at least in the sample tested is no RRULE on the event, thus it cannot have recurrences
