MMM-CalendarExt2

[cskenney]

@Sean I understand that they are not synced. I can run a test where I set both values to 1 minute (each). I can then make a change in my calendar then come back to the MM 10 minutes later and nothing has changed.

Last night I added an item to my calendar and waited for a couple of hours and it never appeared. Today it is added to the MM calendar. It is like it finally refreshed at midnight when it had to adjust the days.

I am now left wondering if the scanInterval in the default section is actually only used at startup and at midnight.

Edit: I added the scanInterval into the section for a specific calendar and it solved the problem. It looks like when the scanInterval is in the default section that it must not be applied to each calendar. The result is that each calendar is only scanned once per day (or so it seems).

[A Former User]

@cskenney
Not at all.

I tested this; I gave 20seconds for updateInterval and scanInterval

At start there was no event to show;

In a minute, I added a test event on my google calendar;

log says There happend 1 event added at that time. (See Scanned and Selected)

And the screen was changed.(See the time of the clock.)

[cskenney]

@Sean where is this log file located? I will take a look at it and see what I can find.

[A Former User]

@cskenney
If you want to see the log on real time;
first stop your pm2 (if you are using), then npm start dev on your MagicMirror directory.

[BKeyport]

@Sean said in MMM-CalendarExt2:

3. That is because just parsing of other calendars is not finished before the first drawing of current loaded events. Just wait, in the next turn remains will be displayed.
   Or set enough time of firstDrawingDelay to wait for all the parsing be completed.
   https://github.com/eouia/MMM-CalendarExt2/wiki/2e.-Configuration:Others

is there a way to set priority of loading? If the trumba calendar referenced (Seahawks) is causing issues, I’d rather my main calendar loads first (Hold display until loaded), then the “trash” calendar, then the Trumba calendar. If not, feature request.

Thanks again, Love being able to make this exactly the way I want.

[A Former User]

@BKeyport
It would be over spec I think. Because;

• This symptom would be improved by delayFirstDrawing to some degree. I think a few seconds would be enough to complete all parsing. If some calendar would take over 10 seconds, it would be the connection issue not parsing issue.
• This symptom would be issued on short time only when MM starts. Usually, after the first cycle of refreshing, this issue would be gone away.
• None the less assigning priority, there would be no guarantee for the specific calendar completing to parse first. The main reason for this delay lays in the network connection quality between your RPI and the calendar server.

Anyway thanks for the suggestion. I’ll research more.

[cskenney]

@Sean I think I have it figured out now. If looks like putting the calendar scanInterval in the default section (look at the code I posted above) doesn’t apply it to all the calendars. Instead it looks like they are using a default value of 30 minutes. Does that make sense?

[A Former User]

@cskenney
Hmmm. without real ical data, I can’t say anything about your case. Configuration itself seems nothing wrong.
When I changed your updateInterval to 1000*30, it refreshes per 30 seconds.
If you don’t mind, send me your configuration with real ical URL. my email is eouia0819@gmail.com

[A Former User]

@cskenney
Wait a sec. I think found something.

[A Former User]

@cskenney
You have a mistyping in defaultSet. Not calendars, Fix it to calendar