MMM-CalendarExt

[A Former User]

@helmi
Well, I tested and found nothing problem.
So, I suspect there might be some errors in front-electron views. Front-view error(from any module) could cause interfering other modules working. You can test by npm start dev.

[helmi]

@Sean I have been using the ‘npm start dev’ and it shows no errors. From the console log I can see that the timer triggers as expected. From the Calendar.js log (terminal view) I can see that the calendars fetching happens only when I start MMM from the beginning.

[helmi]

@Sean FYI: I have removed all other modules, only MMM-CalendarExt existing. I have also removed local calendar file, only Google Calendar URL existing. I have done shutdown and restart (both Rpi and MMM) several times. Problem still exists. For me looks like problem is where the calendars fetching should trigger. They happen only once when I start MMM from the beginning.

[A Former User]

@helmi
Hmmmm… weird.

Anyway, Calendar fetching interval([calendar].interval) is different with front-view redrawing(system.redrawInterval). There is some possibility of you’ve been confusing.

[helmi]

@Sean Ok - So does that mean that the redrawInterval parameter (my setting 60000) has nothing to do with Calendar fetching interval? If so, could you please give me some testing procedure in order to test those parts of the code where the fetching interval is working (or for me: not working)? I have some coding experience, but js is not my best knowledge.

[A Former User]

@helmi

system.redrawInterval is used for refreshing calendar view. It is set to 30 minutes by default. It doesn’t affect calendar fetching. With already fetched data, module redraws views per this interval value.

system: {
  show: ['upcoming', 'daily'],
  redrawInterval: 30*60*1000, //minimum 60000
},

[calendar].interval is used for reading iCal file and fetching. If you set this value to one hour, the calendar will be re-parsed per one hour. But, if there is no changed event or new event, the module doesn’t load newly-parsed-but-same data and use previous data already loaded.

The process is like this;

1. node_helper.js reads calendars per interval time.
2. it fetches calendars and compares them with previously fetched data.
3. If nothing changed, nothing happens.
4. If something changed, newly fetched data will be sent to the module.
5. Module loads fetched events data on the memory.
6. Every redrawInterval time, module redraw views with loaded events data.

[helmi]

@Sean Thank you for the clarifying information. Apparently I was expecting the calendars fetching to happen by system.redrawInterval, which was set at one minute (60000 ms). Now I waited for 30 minutes and fetching happened and events were updated as I expected. No problem so far!
Seems to me that the [calendar].interval (fetching) is set to 30 minutes by default.
Now only one question remains: How can I change the [calendar].interval to for example 5 minutes? This is the interval in “default” calendar, and I have some events needing to be updated more often than 30 minutes.

[helmi]

@Sean Solved! No need to answer my last question. Sorry I didn’t read the documentation carefully enough. It is a very clever solution to have refresh interval setting for each calendar individually!
Thank you very much for nice conversation and happy Christmas greetings from snowy Finland!

[cruunnerr]

Hi,

I realized, that every time the Calendars will be fetched, pm2 creates a log entry in it’s log file.
Well, sometime the log file will be very big, so my question is if it is necessary or advisable to delete the log file and if there is a way to do that automatically.

:)

[yawns]

@cruunnerr
I would try https://github.com/keymetrics/pm2-logrotate/blob/master/README.md for this. Looks like you can set a limit, and pm2 creates a new log file after the limit is reached. You can also activate compression for older log files and define how many old log files you would like to keep.
But I did not try