@sdetweil
Run those commands in the folder for the MMM-CalendarWeek folder, or in the modules folder itself?

I ran it in both folders and restarted MM but nothing changed. Still just a blank screen.

@sdetweil
The output of the MagicMirror-error.log is as follows :

/home/serveradmin/.pm2/logs/MagicMirror-error.log last 50 lines:
0|MagicMir | at require (node:internal/modules/helpers:130:18)
0|MagicMir | at loadConfig (/home/serveradmin/MagicMirror/js/app.js:117:14)
0|MagicMir | at App.start (/home/serveradmin/MagicMirror/js/app.js:250:18)
0|MagicMir | at Object. (/home/serveradmin/MagicMirror/js/electron.js:193:7)
0|MagicMir | at Module._compile (node:internal/modules/cjs/loader:1256:14)
0|MagicMir | at Module._extensions…js (node:internal/modules/cjs/loader:1311:10)
0|MagicMir | at Module.load (node:internal/modules/cjs/loader:1098:32)
0|MagicMir | at Module._load (node:internal/modules/cjs/loader:945:12)
0|MagicMir | MESA-INTEL: warning: Bay Trail Vulkan support is incomplete
0|MagicMir | libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
0|MagicMir | /home/serveradmin/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
0|MagicMir | [2024-04-29 22:15:24.769] [ERROR] (node:65585) UnhandledPromiseRejectionWarning: Error: Cannot find module ‘valid-url’
0|MagicMir | Require stack:
0|MagicMir | - /home/serveradmin/MagicMirror/modules/MMM-CalendarWeek/node_helper.js
0|MagicMir | - /home/serveradmin/MagicMirror/js/app.js
0|MagicMir | - /home/serveradmin/MagicMirror/js/electron.js
0|MagicMir | at Module._resolveFilename (node:internal/modules/cjs/loader:1055:15)
0|MagicMir | at s._resolveFilename (node:electron/js2c/browser_init:2:115476)
0|MagicMir | at Module._resolveFilename (/home/serveradmin/MagicMirror/node_modules/module-alias/index.js:49:29)
0|MagicMir | at Module._load (node:internal/modules/cjs/loader:908:27)
0|MagicMir | at c._load (node:electron/js2c/node_init:2:13672)
0|MagicMir | at Module.require (node:internal/modules/cjs/loader:1122:19)
0|MagicMir | at require (node:internal/modules/helpers:130:18)
0|MagicMir | at Object. (/home/serveradmin/MagicMirror/modules/MMM-CalendarWeek/node_helper.js:9:16)
0|MagicMir | at Module._compile (node:internal/modules/cjs/loader:1256:14)
0|MagicMir | at Module._extensions…js (node:internal/modules/cjs/loader:1311:10)
0|MagicMir | at Module.load (node:internal/modules/cjs/loader:1098:32)
0|MagicMir | at Module._load (node:internal/modules/cjs/loader:945:12)
0|MagicMir | at c._load (node:electron/js2c/node_init:2:13672)
0|MagicMir | at Module.require (node:internal/modules/cjs/loader:1122:19)
0|MagicMir | at require (node:internal/modules/helpers:130:18)
0|MagicMir | at loadModule (/home/serveradmin/MagicMirror/js/app.js:183:19)
0|MagicMir | (Use electron --trace-warnings ... to show where the warning was created)
0|MagicMir | [2024-04-29 22:15:24.769] [ERROR] (node:65585) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
0|MagicMir | MESA-INTEL: warning: Bay Trail Vulkan support is incomplete
0|MagicMir | libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
0|MagicMir | /home/serveradmin/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
0|MagicMir | MESA-INTEL: warning: Bay Trail Vulkan support is incomplete
0|MagicMir | libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
0|MagicMir | /home/serveradmin/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
0|MagicMir | MESA-INTEL: warning: Bay Trail Vulkan support is incomplete
0|MagicMir | libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
0|MagicMir | [66191:0429/230235.459040:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMir | [66191:0429/230235.561159:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMir | [66191:0429/230235.572084:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMir | [66191:0429/230235.577044:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMir | [66191:0429/234504.968361:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMir | [66191:0429/234505.073793:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMir | [66191:0429/234505.089665:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMir | [66191:0429/234505.092215:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed

I have installed the module as per instructions and added the required basic information to the config.js file but when MM restarts, it is not displayed and I am just left with a blank screen.
It doesn’t matter if I use my calendar’s private or public URL, or if I make the calendar public, I get the same result.

When I add the calendar to MM’s default Calendar module, the events are displayed as expected.

My config for the module is as follows : (I have listed both the private and public url: links and commented out one)
{
module: “MMM-CalendarWeek”,
position: “bottom_bar”,
config: {
allowDuplicate: false, // true, false
animationSpeed: 2000, // 0 - 5000
calendarTitle: “Network Maintenance Schedule”,
colored: true, // true, false
coloredSymbolOnly: true, // true, false
dateFormat: “ddd Do MMM”, // Wed 21st Aug
displaySymbol: true, // true, false
fetchInterval: 300000, // 1000 - 86400000
hideEmptyDays: true, // true, false
hideOngoing: false, // true, false
hidePrivate: false, // true, false
maximumEntries: 20, // 0 - 100
maximumNumberOfDays: 7, // 4
maxTitleLength: 25, // 10 - 50
showEndDate: true, // true, false
timeFormat: “dateheaders”, // absolute, relative, dateheaders
wrapEvents: false, // true, false
calendars: [
{
// private .ics link
//url: “URL to my private Google calendar”,
// public .ics link
url: “URL to my public Google calendar”,
symbol: ‘network-wired’,
color: “#FFFFFF”, // white
}
],
}
},

Is anyone able to assist?
I’ve also posted to the MagicMirror page on FB but havent been able to resolve the issue from the suggestions given there.

Thanks

@sdetweil Thank you. That’s sense, I guess.

I have the MMM-Wallpaper module installed and have it set to change the image every hour.
This works as expected.

What is unexpected is that find over the course of a week, the time at which the image slowly drifts out to 5 minutes or so until restart the host, which I usually do 1 min before the hour.
Resetting at this time results in the host coming back up on the hour, give or take a few seconds, and display the first image.

Any ideas on what I can do to rectify this time drift or is there something built into the module itself that causes this drift?

Thanks