Calendar not updating

[sdetweil]

@matt216 well the type error is the problem.
the calendar.module doesn’t recover after the error.

can you open an issue on the mm GitHub page, with that info

are there any errors above that?

[matt216]

@sdetweil None that I can see.

pi@magicmirror:~/.pm2/logs $ tail --lines=1000 MagicMirror-error.log | grep calendar
[02.01.2024 10:29.43.758] [ERROR] Calendar Error. Could not fetch calendar:  https://my.cal.url TypeError: fetch failed
[02.01.2024 10:31.53.769] [ERROR] Calendar Error. Could not fetch calendar:  https://my.cal.url TypeError: fetch failed

Will open an issue. Thanks for assisting. I might have a play with a couple of the other calendar modules there are out there…

[sdetweil]

@matt216 generally there is a more specific error earlier in the log.

if you clear it
pm2 flush
the restart
pm2 restart all

you will have the smallest output to look at

[matt216]

@sdetweil Can’t see any calendar errors in error.log now! :grinning_squinting_face:
But still my new events are not showing up when they should…

[matt216]

https://github.com/MagicMirrorOrg/MagicMirror/issues/3329

[sdetweil]

@matt216 thank you… i posted a an additional grep thru the log to the issue

[sdetweil]

@matt216 cant see any errors… well not with the grep search you do

can u do this

pm2 stop all
cd ~/MagicMirror
npm start >somefile.txt 2>&1

wait, til UI up with no issues, or no updates

ctrl-q on MM screen to end

edit the somefile.txt

loo at messages after “Starting server on port”

[matt216]

@sdetweil

pi@magicmirror:~/MagicMirror $ cat somefile.txt | grep calendar
[02.01.2024 14:56.40.510] [LOG]   Module helper loaded: calendar
[02.01.2024 14:56.42.557] [LOG]   Connecting socket for: calendar
[02.01.2024 14:56.42.558] [LOG]   Starting node helper for: calendar
[02.01.2024 14:56.46.986] [LOG]   Create new calendarfetcher for url: https://my.cal.url - Interval: 120000
[02.01.2024 14:57.13.099] [INFO]  Calendar-Fetcher: Broadcasting 379 events from https://my.cal.url.
[02.01.2024 14:59.23.139] [ERROR] Calendar Error. Could not fetch calendar:  https://my.cal.url TypeError: fetch failed

[matt216]

@sdetweil

[02.01.2024 14:59.23.139] [ERROR] Calendar Error. Could not fetch calendar:  https://my.cal.url TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11576:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  cause: ConnectTimeoutError: Connect Timeout Error
      at onConnectTimeout (node:internal/deps/undici/undici:8522:28)
      at node:internal/deps/undici/undici:8480:50
      at Immediate._onImmediate (node:internal/deps/undici/undici:8511:13)
      at process.processImmediate (node:internal/timers:476:21) {
    code: 'UND_ERR_CONNECT_TIMEOUT'
  }
}

Timeout…
Let me know if the full somefile.txt by email is still wanted.

[sdetweil]

@matt216 no… not needed…

[matt216]

@sdetweil If I enter my calendar URL in to a web browser I can download the ics file fine, FYI

[sdetweil]

@matt216 yes, it was a momentary delay, which caused the timeout… trying to see why the catch() block didn’t

[sdetweil]

@matt216 can u try updating modules/default/calendar/calendarfetcher.js like this
replace lines 58-84 with this . also added this to the issue

		try {  /// new code here     // this will be the new line 58 

		fetch(url, { headers: headers, agent: httpsAgent })
			.then(NodeHelper.checkFetchStatus)
			.then((response) => response.text())
			.then((responseData) => {
				let data = [];

				try {
					data = ical.parseICS(responseData);
					Log.debug(`parsed data=${JSON.stringify(data)}`);
					events = CalendarFetcherUtils.filterEvents(data, {
						excludedEvents,
						includePastEvents,
						maximumEntries,
						maximumNumberOfDays
					});
				} catch (error) {
					fetchFailedCallback(this, error);
					scheduleTimer();
					return;
				}
				this.broadcastEvents();
				scheduleTimer();
			})
			.catch((error) => {
				fetchFailedCallback(this, error);
				scheduleTimer();
			});
		}    // new code here =========
		catch(error){
                     console.error( "fetch for calendar url" +url + "failed error="+error.code);
                    fetchFailedCallback(this, error);
                    scheduleTimer();
		}   // end new code ===== 

[matt216]

@sdetweil Doesn’t like that - mirror won’t load. Got to pick up my little boy now, so reverted back (mirror loads ok again). Will try again and look at logs.

[sdetweil]

@matt216 u are replacing the whole block, right…

replace lines 58-84 in original with that

lmk

[matt216]

@sdetweil can you tell I’m not a developer…?!

Ok, I’ve replaced the whole block, then pm2 stop all, cd ~/MagicMirror, npm start…

Mirror starts but still no new calendar events are showing where I would expect to be. Interestingly I can see that edits to existing events that I’ve made are showing up on the mirror, so there is some communication. Just no new events are being picked up.

Thanks again,
Matt

[matt216]

By existing and new events I mean with reference to the point I added the calendar server to the calendar module. That first initial sync (if that’s the right word) of the .ics file.

[sdetweil]

@matt216 and what do you see in the place where you npm start?

should NOT see the timeout error

[matt216]

@sdetweil I do not see a timeout, no. The most unusual log entry related to the calendar is
[04.01.2024 16:39.21.257] [LOG] Use existing calendarfetcher for url: https://my.cal.url

That “existing” might imply something…?

[sdetweil]

@matt216 not an error… says ’ we created a fecther() at the start’… and we found it and are reusing it… just informational

now… lets turn on more debug

in the config.js

change

    logLevel: [
      "INFO",
      "LOG",
      "WARN",
      "ERROR",
   //   "DEBUG"
    ],

loglevel like that (just hit enter after the commas and before the ]

then add the // debug line
then remove the leading //

just makes it easier later to turn off debug by adding the // (comment it out)

then in MagicMirror folder again do

npm start >somefile.txt 2>&1

wait til you think it should have updated...

then ctrl-q

and then look at the somefile.txt or send it to me
same user id at gmail 

(I added most of the debug output to work on calendar problems) 

then u can comment out "DEBUG" again

we did change the calendar parser version this release, to fix a couple bugs I added code for, and a big change on the repeating rule handler...