@HeikoGr - lol, adjusted my headers and saw that the timezone was concatenated to the header. Snapped a photo to post and saw your comment. That fixed it!!! Thank you and Sam both!!!

@sdetweil - I don’t use PM2, but I went ahead and replicated the steps you suggested to create that some file.txt log file and the appropriate searches. The only thing of note I saw was an error about MMM-CalendarExt3 not having permission to enter objects. Not sure if that would have any bearing on the MMM-GoogleCalendar module. Image attached.

By the way, I tried git pull to update MagicMirror, but being told I can’t fast-forward for some reason.

@sdetweil said:

@reilley what MagicMirror version are you on? There was a bug fixed when scanning for changes

Version 2.34.0

@sdetweil - Hi Sam! Surprisingly, the error may not show up for a while after you make changes and restart.

A couple of weeks ago, MagicMirror started displaying a message that the MMM-GoogleCalendar module is behind by two commits, but I’ve git-pulled and installed, merged as required, and ran the npm install but it’s still showing as being behind. I ran npm audit fix and two moderate issues appear, but not sure how to fix them. I’ve installed the latest GAXIOS version as suggested but no joy.

Any ideas?

So for a few weeks now, I continue to get the messsge that my MMM-GoogleCalendar module is two commits behind, even though I’ve git pulled and installed the latest version. Merged as needed and ran NPM audits but see two moderate issues. Screenshots attached!

@sdetweil - you’re gonna laugh, but I found the issue. I was using an inactive API key. My backup was too old and was before the v2.29.0 API 3.0 requirement. Sorry to drag you through this!

@reilley - oh, I think I know what’s wrong now.

@sdetweil - nope, same result

@sdetweil said in "Invalid Date" appears in Weather module. MM v2.29.0:

@reilley said in "Invalid Date" appears in Weather module. MM v2.29.0:

So my code worked for you and the only change was the API key?

correct

That’s nuts. Why would an API key work two days ago and not today? Seems like maybe there’s a configuration problem elsewhere but I not sure where it would be since I made no changes to weather.js or other .js files associated with the Weather module.

@sdetweil said in "Invalid Date" appears in Weather module. MM v2.29.0:

@reilley I copied your config and used my apikey
no other changes (well I wrapped your config in code block to keep the quotes correct for copy/paste)

So my code worked for you and the only change was the API key? This key worked two days ago, so not sure what’s happening here.