Although my original issue wasn’t identified, I am happy with the new module information provided by mumblebaj. It appears to be stable and the updates are continuing to work. I think we can close this one. Thanks!

@mumblebaj
I installed the module and it looks good! I will continue to monitor for the next while to see if the updates continue to work. Thanks!

@mumblebaj
Wow! That looks like just what I would need… What module is that? I thought that sticking to the default modules would be advantageous but maybe that is a better solution.

I seem to be having an intermittent problem with getting weather updates. I am using the default weather module, and I am aware of the issues with using some of the different providers. But I have read that using the Pirate Weather API would work. I have configured my MM to display both the current weather conditions and a second display of the weekly forecast. Initially, everything works as expected. But eventually, either my current weather display OR my weekly forecast will stop providing updated information. Whenever I reboot/restart my MM, the problem is resolved and I get the correct information.

I understand that Pirate Weather allows 10,000 API calls per month. I set the first update interval to 600,000 (every 10 minutes) and the second one to 1,800,000 (every half hour). I assume this results in 8 calls per hour or just under 6,000 calls per month. So, I don’t believe that I am exceeding the call limitation. Also, the fact that a reboot will fix the problem would indicate that this is not a call limitation issue.

I have read that others have run into problems which they resolved by offsetting the times when the call requests are sent by adjusting the ‘initialLoadDelay’ value. I have set that value to ‘5000’ on my second display (value not set on the first display).

I set my MM to restart every week (via crontab) so I can get an idea if the problem re-occurs at a specific point. I attempt to monitor the uptime whenever I see the problem. It doesn’t seem to have a pattern. It can fail after two days, or three days, four days, etc. Sometimes, it will work for the entire week, and my MM will restart and reset the uptime clock.

The failure can appear on the current conditions (ie. the displayed temperature is ‘stuck’ at the same value for days), or it can appear on the weekly forecast (ie. the days of the week will not change). It seems to be random. I know that if I just wait a few days, it will get resolved on its own, but I would prefer to get an idea on how to fix this so that the display is correct all the time. Any ideas?

Thanks in advance.

	  {
module: "weather",
position: "top_right",
config: {
  type: "current",
  weatherProvider: "pirateweather",
  apiBase: "https://api.pirateweather.net",
  weatherEndpoint: "/forecast",
  apiKey: "my API key",
  lat: "my latitude",
  lon: "my longitude",
  tableClass: "medium",
  colored: "true",
  fadePoint: "0.50",
  maxNumberOfDays: "1",
  updateInterval: "600000",
  degreeLabel: "true"
},

},

	{
module: "weather",
position: "top_right",
config: {
  type: "forecast",
  Header: "true",
  appendLocationNameToHeader: "true",
  weatherProvider: "pirateweather",
  apiBase: "https://api.pirateweather.net",
  weatherEndpoint: "/forecast",
  apiKey: "my API key",
  lat: "my latitude",
  lon: "my longitude",
  tableClass: "small",
  colored: "true",
  fadePoint: "0.50",
  maxNumberOfDays: "7",
  updateInterval: "1800000",
  degreeLabel: "true",
  initialLoadDelay: "5000"
},

},

Ah, yes. That was it. Instead of manually making the changes, I just copied the entire code and pasted. Seems to work now. Thanks!

I don’t believe that I am using pm2. Here are the logs when MM starts:

magicmirror@2.27.0 start
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

[2024-05-03 16:04:55.886] [LOG] Starting MagicMirror: v2.27.0
[2024-05-03 16:04:55.935] [LOG] Loading config …
[2024-05-03 16:04:55.938] [LOG] config template file not exists, no envsubst
[2024-05-03 16:04:55.957] [LOG] Loading module helpers …
[2024-05-03 16:04:55.958] [LOG] No helper found for module: alert.
[2024-05-03 16:04:56.237] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.239] [LOG] Module helper loaded: updatenotification
[2024-05-03 16:04:56.240] [LOG] No helper found for module: clock.
[2024-05-03 16:04:56.402] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.403] [LOG] Module helper loaded: MMM-MyCalendar
[2024-05-03 16:04:56.403] [LOG] No helper found for module: calendar_monthly.
[2024-05-03 16:04:56.414] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.414] [LOG] Module helper loaded: MMM-Pir
[2024-05-03 16:04:56.462] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.462] [LOG] Module helper loaded: MMM-Weather
[2024-05-03 16:04:56.543] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.544] [LOG] Module helper loaded: MMM-Tools
[2024-05-03 16:04:56.673] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.674] [LOG] Module helper loaded: newsfeed
[2024-05-03 16:04:56.674] [LOG] All module helpers loaded.
[2024-05-03 16:04:56.685] [LOG] Starting server on port 8080 …
[2024-05-03 16:04:58.244] [LOG] Server started …
[2024-05-03 16:04:58.247] [LOG] Connecting socket for: updatenotification
[2024-05-03 16:04:58.248] [LOG] Starting module helper: updatenotification
[2024-05-03 16:04:58.250] [LOG] Connecting socket for: MMM-MyCalendar
[2024-05-03 16:04:58.261] [LOG] Starting node helper for: MMM-MyCalendar
[2024-05-03 16:04:58.262] [LOG] Connecting socket for: MMM-Pir
[2024-05-03 16:04:58.264] [LOG] Connecting socket for: MMM-Weather
[2024-05-03 16:04:58.272] [LOG] Connecting socket for: MMM-Tools
[2024-05-03 16:04:58.284] [LOG] [Tools] MMM-Tools Version: 2.1.7
[2024-05-03 16:04:58.286] [LOG] Connecting socket for: newsfeed
[2024-05-03 16:04:58.287] [LOG] Starting node helper for: newsfeed
[2024-05-03 16:04:58.288] [LOG] Sockets connected & modules started …
WARNING: v3dv is neither a complete nor a conformant Vulkan implementation. Testing use only.
[2024-05-03 16:04:58.891] [LOG] Launching application.
[2024-05-03 16:05:02.661] [LOG] Create new calendarfetcher for url: http://www.calendarlabs.com/ical-calendar/ics/39/Canada_Holidays.ics - Interval: 300000
[2024-05-03 16:05:02.668] [ERROR] Whoops! There was an uncaught exception…
[2024-05-03 16:05:02.677] [ERROR] ReferenceError: fetcher is not defined
at fetchCalendar (/home/pi/MagicMirror/modules/MMM-MyCalendar/calendarfetcher.js:65:3)
at CalendarFetcher.startFetch (/home/pi/MagicMirror/modules/MMM-MyCalendar/calendarfetcher.js:110:3)
at Class.createFetcher (/home/pi/MagicMirror/modules/MMM-MyCalendar/node_helper.js:73:11)
at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-MyCalendar/node_helper.js:21:9)
at Socket. (/home/pi/MagicMirror/js/node_helper.js:98:11)
at Socket.emit (node:events:514:28)
at Socket.emitUntyped (/home/pi/MagicMirror/node_modules/socket.io/dist/typed-events.js:69:22)
at /home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:704:39
at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
[2024-05-03 16:05:02.680] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
[2024-05-03 16:05:02.684] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MagicMirrorOrg/MagicMirror/issues
[2024-05-03 16:05:02.686] [LOG] Create new calendarfetcher for url: https://calendar.google.com/calendar/ical/5u47rliikveghncls65jrsotkc%40group.calendar.google.com/private-7c6a117f2ae0d357b447c735373245a2/basic.ics - Interval: 300000
[2024-05-03 16:05:02.688] [ERROR] Whoops! There was an uncaught exception…
[2024-05-03 16:05:02.689] [ERROR] ReferenceError: fetcher is not defined
at fetchCalendar (/home/pi/MagicMirror/modules/MMM-MyCalendar/calendarfetcher.js:65:3)
at CalendarFetcher.startFetch (/home/pi/MagicMirror/modules/MMM-MyCalendar/calendarfetcher.js:110:3)
at Class.createFetcher (/home/pi/MagicMirror/modules/MMM-MyCalendar/node_helper.js:73:11)
at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-MyCalendar/node_helper.js:21:9)
at Socket. (/home/pi/MagicMirror/js/node_helper.js:98:11)
at Socket.emit (node:events:514:28)
at Socket.emitUntyped (/home/pi/MagicMirror/node_modules/socket.io/dist/typed-events.js:69:22)
at /home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:704:39
at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
[2024-05-03 16:05:02.690] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
[2024-05-03 16:05:02.690] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MagicMirrorOrg/MagicMirror/issues
[2024-05-03 16:05:02.790] [LOG] Create new newsfetcher for url: https://rss.cbc.ca/lineup/canada.xml - Interval: 300000
[2024-05-03 16:05:03.039] [LOG] Create new newsfetcher for url: https://rss.cbc.ca/lineup/canada-toronto.xml - Interval: 300000
[2024-05-03 16:05:03.052] [LOG] Create new newsfetcher for url: https://rss.cbc.ca/lineup/sports-nhl.xml - Interval: 300000
[2024-05-03 16:05:03.071] [LOG] [WEATHER] MMM-WEATHER Version: 1.0.6
[2024-05-03 16:05:03.112] [LOG] [MMM-Pir] Version: 1.5.1 rev: 240402
[2024-05-03 16:05:03.114] [LOG] [MMM-Pir] [LIB] [PIR] Mode 0 Selected (onoff library)
[2024-05-03 16:05:03.168] [LOG] [MMM-Pir] [LIB] [PIR] Started!
[2024-05-03 16:05:03.172] [LOG] [MMM-Pir] [LIB] [SCREEN] Mode 4: HDMI CEC
[2024-05-03 16:05:03.228] [LOG] [MMM-Pir] Started!
[2024-05-03 16:05:03.231] [INFO] updatenotification: Updater Class Loaded!
[2024-05-03 16:05:03.233] [INFO] updatenotification: Checking PM2 using…
[2024-05-03 16:05:03.239] [INFO] Checking git for module: MMM-MyCalendar
[2024-05-03 16:05:03.375] [INFO] Checking git for module: calendar_monthly
[2024-05-03 16:05:03.478] [INFO] System information:

SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.4; raspberry: [object Object]; virtual: false

OS: platform: linux; distro: Raspbian GNU/Linux; release: 11; arch: arm; kernel: 5.10.103-v7l+

VERSIONS: electron: 29.1.6; used node: 20.9.0; installed node: 20.4.0; npm: 9.8.1; pm2: 5.3.1

OTHER: timeZone: America/Toronto; ELECTRON_ENABLE_GPU: undefined

[2024-05-03 16:05:03.529] [INFO] Checking git for module: MMM-Pir
[2024-05-03 16:05:03.687] [INFO] updatenotification: [PM2] You are not using pm2
[2024-05-03 16:05:04.116] [INFO] Checking git for module: MMM-Weather
[2024-05-03 16:05:04.566] [INFO] Checking git for module: MMM-Tools
[2024-05-03 16:05:04.708] [INFO] Newsfeed-Fetcher: Broadcasting 18 items.
[2024-05-03 16:05:04.809] [INFO] Checking git for module: MagicMirror
[2024-05-03 16:05:04.861] [INFO] Newsfeed-Fetcher: Broadcasting 20 items.
[2024-05-03 16:05:04.874] [INFO] Newsfeed-Fetcher: Broadcasting 19 items.
[2024-05-03 16:05:14.810] [LOG] Shutting down server…
[2024-05-03 16:05:14.812] [LOG] Stopping module helper: updatenotification
[2024-05-03 16:05:14.813] [LOG] Stopping module helper: MMM-MyCalendar
[2024-05-03 16:05:14.813] [LOG] Stopping module helper: MMM-Pir
[2024-05-03 16:05:14.814] [LOG] Stopping module helper: MMM-Weather
[2024-05-03 16:05:14.814] [LOG] Stopping module helper: MMM-Tools
[2024-05-03 16:05:14.815] [LOG] Stopping module helper: newsfeed
[2024-05-03 16:05:14.816] [LOG] Node_helpers stopped …
[2024-05-03 16:05:14.891] [LOG] [MMM-Pir] [LIB] [SCREEN] See you soon !
[2024-05-03 16:05:14.893] [LOG] [MMM-Pir] [LIB] [SCREEN] @bugsounet

Not sure what happened here… You indicate that this issue is solved…? I still don’t have a calendar yet. MM launches now, but I only have an indication that the calendar is “Loading…” but it never appears.

I am running MM version 2.27.0, node v20.4, npm v9.8.1

I read that post already, which allowed me to get the MM running again. I just commented out the lines indicated.

I’ve been using the default calendar module for awhile now, and living with the incorrect date for one of my recurring events. Specifically, my event occurs on the first Thursday of each month, and the calendar seems to show the correct date for the first occurrence, but all subsequent occurrences seem to happen on the first Wednesday of each month — one day early.

I understand that one solution may be to use the MMM-MyCalendar module instead. I attempted this and discovered that my MM wouldn’t launch, and attempted a workaround shown here:

https://github.com/jclarke0000/MMM-MyCalendar/issues/40

As others have reported, MM will now launch, but the calendar never appears (always indicates ‘loading’). I can put back the original calendar module, and just live with the problem, but does anyone have any other suggestions? Thanks.

@karsten13

Success! I ran the following command:

npm install node-fetch@2

… and now it’s back up and running again! Thanks for the quick response!