said in 2.32.0 Calendar module limitDays and excludedEvents stopped working:
Previous suggestions to fix the excludedEvents still not working though.
@sdetweil hold up - it’s all working now! I don’t think I changed anything else, just an extra refresh. So, all your fixes are good. Sorry that took a while to figure out, and if I’d read @karsten13’s docker instructions properly I think that docker module override feature was probably the cause of earlier confusion.
@karsten13 aha, good to know, although I already started and now finished setting up from scratch again 🙄 no docker this time … I kept it on a spare sd card though so may switch back.
@sdetweil new code for limitDays reapplied on a fresh install, still seems fine. Previous suggestions to fix the excludedEvents still not working though.
@sdetweil no problem, that new code seems to work fine for me.
However, I don’t seem to have a great setup for testing - after making the changes, I can load up MM in my remote/laptop browser and immediately see the changes working, but if I try and refresh the electron browser on the raspberry pi running my mirror (using MMM-Remote-Control), it seems to take ages, crash, and then reverts the code back to the docker image default 😮💨
I can see this in the docker container logs so I reckon it’s reverting any changes I make there?
[entrypoint 18:36:04.283] [INFO] copy default modules
[entrypoint 18:36:04.918] [INFO] copy css files
> magicmirror@2.32.0 start
> node --run start:x11
@sdetweil I’ve no idea then, but if you were able to reproduce the issue I had, and then fix it on your end, I probably just messed something up somewhere and without any access to logs on my docker setup that may remain a mystery … I’ve just had another go at trying to figure out what that may be, no luck.
No rush at all but I guess if you’re happy with the fix it’ll show up in a new MM version at some point and I’ll update to that.
@sdetweil should I see a console message from loader.js about calendarfetcherutils.js being loaded?
I see
Load script: modules/default/calendar/calendar.js
Load script: modules/default/calendar/calendarutils.js
but no mention in the console of calendarfetcherutils.js
@sdetweil fair enough, complexity no doubt warranted!
Perhaps is there any reason why shouldEventBeExcluded function might not be getting called at all for me? I’m stumped why after making all these changes including console.log messages, nothing is appearing any different -
@sdetweil yep that’s what I’ve got, copying below in case I’m missing something …
I’ve also added your debug messages back in and changed Log.debug to console.log (as I still can’t get any debug logs from docker but I do get console.log messages from other modules) but nothing comes out in the console log - seems odd that all these changes have had zero effect, am I missing something that might be needed to get these changes to kick in?
shouldEventBeExcluded (config, title) {
let result = { // CHANGED
excluded: false,
until: null
};
for (let f in config.excludedEvents) {
let filter = config.excludedEvents[f],
testTitle = title.toLowerCase(),
until = null,
useRegex = false,
regexFlags = "g";
if (filter instanceof Object) {
if (typeof filter.until !== "undefined") {
until = filter.until;
}
if (typeof filter.regex !== "undefined") {
useRegex = filter.regex;
}
// If additional advanced filtering is added in, this section
// must remain last as we overwrite the filter object with the
// filterBy string
if (filter.caseSensitive) {
filter = filter.filterBy;
testTitle = title;
} else if (useRegex) {
filter = filter.filterBy;
testTitle = title;
regexFlags += "i";
} else {
filter = filter.filterBy.toLowerCase();
}
} else {
filter = filter.toLowerCase();
}
console.log("should be excluded ", testTitle, filter, useRegex, regexFlags)
if (CalendarFetcherUtils.titleFilterApplies(testTitle, filter, useRegex, regexFlags)) {
if (until) {
result.until = until; // CHANGED
} else {
console.log("event should be excluded = true,", testTitle )
result.excluded = true; // CHANGED
}
console.log("filter applies result =", result)
break;
}
}
console.log("filter applies returning =", result)
return result; // CHANGED
},
p.s. just spotted comment on line 12 😅
TODO This seems like an overly complicated way to exclude events based on the title.
@sdetweil perhaps I’m missing something, but that’s not working for me - it’s made no difference, excluded events are still appearing … I’ve double checked and can’t spot anything amiss, I’ve made the 4 changes from ‘filter’ to ‘result’?
@sdetweil nice! Yes that’s fixed the limitDays issue for me …
Now, how about part 2 of my issue, the excludedEvents config? The first event showing for me is titled ‘Tutor time’ despite that string being excluded. I’ve tried other terms with/without spaces and nothing seems to work to exclude events any more?
@sdetweil yeah that’s what I was using limitDays for and it was working great for my needs until now - I have my kids school lessons synced to a google calendar, and setting limitDays to 1 used to show the full set of lessons for the day. When they get home from school (all events from the current day are in the past), it automatically showed all of the lessons for the following day. Best thing I’ve ever used MM for! Even highlights PE lessons so they know when to bring kit :)
For me now, limitDays: 1 just shows the single next event even when there are 6 more events on that day (and if that event is ‘Tutor time’, it displays when it should be hidden).
I can’t say exactly what version I was on prior to the update but it should have been whatever the previous version was - since I set this up with watchtower in docker I’ve not had to do any manual upgrades.
Here’s my anonamised calendar config - I have 5 different calendar modules running if that’s likely to be a factor, but this is one that has the config issues:
{
module: 'calendar',
header: 'School day',
position: 'bottom_right',
config: {
coloredSymbol: true,
coloredText: true,
showLocation: true,
displaySymbol: false,
hideTime: true,
tableClass: 'medium',
flipDateHeaderTitle: true,
fade: false,
timeFormat: 'absolute',
dateFormat: 'ddd',
fullDayEventDateFormat: 'ddd',
urgency: '0',
sliceMultiDayEvents: true,
nextDaysRelative: false,
limitDays: 1,
fetchInterval: '600000',
displayRepeatingCountTitle: true,
wrapEvents: false,
//maxTitleLength: 30,
customEvents: [{ keyword: 'Physical Education', symbol: 'volleyball', color: 'Gold' }],
excludedEvents: [
'Tutor time'
],
calendars: [
{
symbol: 'graduation-cap',
url: 'https://calendar.google.com/calendar/ical/REDACTED/basic.ics'
}
]
}
},
Thanks, I’ve merged that logging improvement to MMM-Scrapey.
I suppose my query is simply whether anybody else can see the same calendar functionality issues as me?
If it’s only affecting me, I’ll probably try rebuilding my setup from scratch.
@KristjanESPERANTO I’ve been able to update MMM-Remote-Control to 3.2.0 and you were right that stops the errors I was getting in the logs when running docker compose up.
Still doesn’t look like there are any clues there for my calendar issues though …
docker compose up > somenewfile.txt ─╯
[+] Running 6/6
✔ Network magicmirror_default Created0.2s
✔ Container xserver Created0.8s
✔ Container watchtower Created0.7s
✔ Container init Created0.8s
✔ Container mm Created0.2s
✔ Container mmpm Created0.2s
xserver |
xserver | X.Org X Server 1.21.1.14
xserver | X Protocol Version 11, Revision 0
xserver | Current Operating System: Linux 2133690aa282 6.12.34+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.34-1+rpt1~bookworm (2025-06-26) aarch64
xserver | Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=de21c80a-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=GB video=HDMI-A-1:1920x1080M@60,rotate=270
xserver |
xserver | Current version of pixman: 0.43.4
xserver | Before reporting problems, check http://wiki.x.org
xserver | to make sure that you have the latest version.
xserver | Markers: (--) probed, (**) from config file, (==) default setting,
xserver | (++) from command line, (!!) notice, (II) informational,
xserver | (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
xserver | (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 8 21:49:11 2025
xserver | (==) Using system config directory "/usr/share/X11/xorg.conf.d"
watchtower | time="2025-07-08T21:49:12Z" level=info msg="Watchtower 1.7.1"
watchtower | time="2025-07-08T21:49:12Z" level=info msg="Using no notifications"
watchtower | time="2025-07-08T21:49:12Z" level=info msg="Checking all containers (except explicitly disabled with label)"
watchtower | time="2025-07-08T21:49:12Z" level=info msg="Scheduling first run: 2025-07-15 21:49:12 +0000 UTC"
watchtower | time="2025-07-08T21:49:12Z" level=info msg="Note that the first check will be performed in 167 hours, 59 minutes, 59 seconds"
mm | [2025-07-08 22:50:02.823] [WARN] You're using a full whitelist configuration to allow for all IPs
mm | [2025-07-08 22:50:26.661] [ERROR] table not found in HTML.
mm | [2025-07-08 22:50:26.684] [ERROR] table not found in HTML.
mm | [2025-07-08 22:50:26.765] [ERROR] Tue Jul 08 2025 22:50:26 GMT+0100 (British Summer Time) - WatchDog: Heartbeat timeout. Frontend might have crashed. Exit now.
mm | [2025-07-08 22:50:26.873] [ERROR] table not found in HTML.
mm | [2025-07-08 22:50:26.888] [ERROR] table not found in HTML.
mm | npm notice
mm | npm notice New major version of npm available! 10.9.2 -> 11.4.2
mm | npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.4.2
mm | npm notice To update run: npm install -g npm@11.4.2
mm | npm notice
mm | [2025-07-08 22:50:56.210] [WARN] You're using a full whitelist configuration to allow for all IPs
mm | [2025-07-08 22:51:04.036] [ERROR] table not found in HTML.
mm | [2025-07-08 22:51:04.866] [ERROR] Tue Jul 08 2025 22:51:04 GMT+0100 (British Summer Time) - WatchDog: Heartbeat timeout. Frontend might have crashed. Exit now.
mm | [2025-07-08 22:51:24.381] [WARN] You're using a full whitelist configuration to allow for all IPs
mm | [2025-07-08 22:51:42.944] [ERROR] table not found in HTML.
mm | [2025-07-08 22:51:42.966] [ERROR] table not found in HTML.
mm | [2025-07-08 22:52:10.109] [ERROR] table not found in HTML.
mm | [2025-07-08 22:52:11.413] [ERROR] table not found in HTML.
I think the repeating ‘table not found in HTML’ error is just from my MMM-Scrapey module, as it’s looking for bus times and it’s late, the last bus has gone.
@mumblebaj for a bit more context I’m using MagicMirrorOS and it’s been great whilst it was working, but certainly seems to make dubugging harder so perhaps I’ll switch back to regular setup when I get a bit more time …
To clarify, I’m only seeing errors when trying to work around lack of access to logs in docker - if I just let the system run normally I’m not getting any errors, just an unexpected change in calendar behaviour.
docker compose up -d works if I enter /opt/mm/run directory first.
Not sure I need that compose up command though as the container is running ok already. docker exec -it mm bash works to get into the container, but then I can’t find any debug logs …
@KristjanESPERANTO I’m not sure but I think the errors referring to MMM-Remote-Control I posted were more to do with my failed attempts to get logs from the docker container, not the original issue of calendar display … but in case you’re onto something:
> node@magicmirroros:/opt/magic_mirror/modules/MMM-Remote-Control$ grep '"version":' package.json
"version": "3.1.4",
@sdetweil if I cd into /opt/mm/run I can get some output but still looks like it fails before giving anything useful:
docker compose up > somefile.txt
[+] Running 5/5
✔ Container watchtower Created0.0s
✔ Container xserver Created0.0s
✔ Container init Created0.0s
✔ Container mm Created0.0s
✔ Container mmpm Created0.0s
xserver |
xserver | X.Org X Server 1.21.1.14
xserver | X Protocol Version 11, Revision 0
xserver | Current Operating System: Linux ad48284f7eed 6.6.74+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025-01-27) aarch64
xserver | Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=de21c80a-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=GB video=HDMI-A-1:1920x1080M@60,rotate=270
xserver |
xserver | Current version of pixman: 0.43.4
xserver | Before reporting problems, check http://wiki.x.org
xserver | to make sure that you have the latest version.
xserver | Markers: (--) probed, (**) from config file, (==) default setting,
xserver | (++) from command line, (!!) notice, (II) informational,
xserver | (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
xserver | (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 7 13:42:05 2025
xserver | (==) Using system config directory "/usr/share/X11/xorg.conf.d"
watchtower | time="2025-07-07T13:42:06Z" level=info msg="Watchtower 1.7.1"
watchtower | time="2025-07-07T13:42:06Z" level=info msg="Using no notifications"
watchtower | time="2025-07-07T13:42:06Z" level=info msg="Checking all containers (except explicitly disabled with label)"
watchtower | time="2025-07-07T13:42:06Z" level=info msg="Scheduling first run: 2025-07-14 13:42:06 +0000 UTC"
watchtower | time="2025-07-07T13:42:06Z" level=info msg="Note that the first check will be performed in 167 hours, 59 minutes, 59 seconds"
mm | [2025-07-07 14:42:46.322] [WARN] You're using a full whitelist configuration to allow for all IPs
mm | [2025-07-07 14:43:11.194] [ERROR] Mon Jul 07 2025 14:43:11 GMT+0100 (British Summer Time) - WatchDog: Heartbeat timeout. Frontend might have crashed. Exit now.
mm | [2025-07-07 14:43:37.677] [WARN] You're using a full whitelist configuration to allow for all IPs
mm | [2025-07-07 14:43:48.386] [ERROR] Whoops! There was an uncaught exception...
mm | [2025-07-07 14:43:48.396] [ERROR] TypeError: Unexpected ? at 17, expected END: https://git.new/pathToRegexpError
mm | at Iter.consume (/opt/magic_mirror/node_modules/path-to-regexp/dist/index.js:123:15)
mm | at consume (/opt/magic_mirror/node_modules/path-to-regexp/dist/index.js:179:16)
mm | at parse (/opt/magic_mirror/node_modules/path-to-regexp/dist/index.js:183:20)
mm | at /opt/magic_mirror/node_modules/path-to-regexp/dist/index.js:294:74
mm | at Array.map (<anonymous>)
mm | at pathToRegexp (/opt/magic_mirror/node_modules/path-to-regexp/dist/index.js:294:25)
mm | at Object.match (/opt/magic_mirror/node_modules/path-to-regexp/dist/index.js:264:30)
mm | at matcher (/opt/magic_mirror/node_modules/router/lib/layer.js:86:23)
mm | at Array.map (<anonymous>)
mm | at new Layer (/opt/magic_mirror/node_modules/router/lib/layer.js:93:46)
mm | at router.route (/opt/magic_mirror/node_modules/router/index.js:428:17)
mm | at router.route (/opt/magic_mirror/node_modules/router/index.js:428:17)
mm | at Class.createApiRoutes (/opt/magic_mirror/modules/MMM-Remote-Control/API/api.js:172:24)
mm | at Class.onModulesLoaded (/opt/magic_mirror/modules/MMM-Remote-Control/node_helper.js:83:10)
mm | at Class.loadModuleDefaultConfig (/opt/magic_mirror/modules/MMM-Remote-Control/node_helper.js:354:25)
mm | at /opt/magic_mirror/modules/MMM-Remote-Control/node_helper.js:225:14
mm | at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read/context:68:3)
mm | [2025-07-07 14:43:48.397] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
mm | [2025-07-07 14:43:48.398] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MagicMirrorOrg/MagicMirror/issues
mm | [2025-07-07 14:43:48.405] [ERROR] Mon Jul 07 2025 14:43:48 GMT+0100 (British Summer Time) - WatchDog: Heartbeat timeout. Frontend might have crashed. Exit now.
… then it just gets stuck in a loop trying to restart
@sdetweil ah - I did have ‘limitDays: 1’ previously but added the quotes to try and fix - I’ve removed them again but either way seems to make no difference.
I’m not sure how to get the debug log out though, as I’m using a docker setup, not pm2, and can’t figure out how to stop the running instance first (so it looks like it fails to start fully) - here’s what I get:
docker exec -it mm bash
node@magicmirroros:/opt/magic_mirror$ npm start
> magicmirror@2.32.0 start
> node --run start:x11
[2025-07-07 12:55:11.034] [LOG] Starting MagicMirror: v2.32.0
[2025-07-07 12:55:11.114] [LOG] Loading config ...
[2025-07-07 12:55:11.125] [LOG] config template file not exists, no envsubst
[2025-07-07 12:55:13.444] [INFO] Checking config file /opt/magic_mirror/config/config.js ...
[2025-07-07 12:55:13.892] [INFO] Your configuration file doesn't contain syntax errors :)
[2025-07-07 12:55:13.898] [INFO] Checking modules structure configuration ...
[2025-07-07 12:55:14.362] [INFO] Your modules structure configuration doesn't contain errors :)
[2025-07-07 12:55:14.890] [LOG] Loading module helpers ...
[2025-07-07 12:55:15.014] [LOG] Initializing new module helper ...
[2025-07-07 12:55:15.022] [LOG] Module helper loaded: MMM-mmpm
[2025-07-07 12:55:15.892] [LOG] Initializing new module helper ...
[2025-07-07 12:55:15.894] [LOG] Module helper loaded: MMM-Remote-Control
[2025-07-07 12:55:16.549] [LOG] Initializing new module helper ...
[2025-07-07 12:55:16.551] [LOG] Module helper loaded: MMM-AuroraWatchUK
[2025-07-07 12:55:18.106] [LOG] MMM-Scrapey node helper is starting...
[2025-07-07 12:55:18.108] [LOG] Initializing new module helper ...
[2025-07-07 12:55:18.109] [LOG] Module helper loaded: MMM-Scrapey
[2025-07-07 12:55:18.180] [LOG] Initializing new module helper ...
[2025-07-07 12:55:18.182] [LOG] Module helper loaded: MMM-MoonPhase
[2025-07-07 12:55:18.193] [LOG] Initializing new module helper ...
[2025-07-07 12:55:18.196] [LOG] Module helper loaded: MMM-WatchDog
[2025-07-07 12:55:18.201] [LOG] No helper found for module: alert.
[2025-07-07 12:55:18.395] [LOG] Initializing new module helper ...
[2025-07-07 12:55:18.396] [LOG] Module helper loaded: MMM-ModuleScheduler
[2025-07-07 12:55:18.402] [LOG] No helper found for module: clock.
[2025-07-07 12:55:19.042] [LOG] Initializing new module helper ...
[2025-07-07 12:55:19.043] [LOG] Module helper loaded: calendar
[2025-07-07 12:55:19.050] [LOG] No helper found for module: weather.
[2025-07-07 12:55:19.141] [LOG] Initializing new module helper ...
[2025-07-07 12:55:19.142] [LOG] Module helper loaded: MMM-MyGarbage
[2025-07-07 12:55:19.145] [LOG] All module helpers loaded.
[2025-07-07 12:55:19.177] [LOG] Starting server on port 8080 ...
[2025-07-07 12:55:19.185] [WARN] You're using a full whitelist configuration to allow for all IPs
[2025-07-07 12:55:19.278] [ERROR] Whoops! There was an uncaught exception...
[2025-07-07 12:55:19.281] [ERROR] Error: listen EADDRINUSE: address already in use 0.0.0.0:8080
at Server.setupListenHandle [as _listen2] (node:net:1940:16)
at listenInCluster (node:net:1997:12)
at node:net:2206:7
at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
code: 'EADDRINUSE',
errno: -98,
syscall: 'listen',
address: '0.0.0.0',
port: 8080
}
[2025-07-07 12:55:19.284] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
[2025-07-07 12:55:19.286] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MagicMirrorOrg/MagicMirror/issues
[2025-07-07 12:55:20.074] [INFO] System information:
### SYSTEM: manufacturer: ; model: Docker Container; virtual: false
### OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.6.74+rpt-rpi-v8
### VERSIONS: electron: undefined; used node: 22.17.0; installed node: 22.17.0; npm: 10.9.2; pm2:
### OTHER: timeZone: Europe/London; ELECTRON_ENABLE_GPU: undefined
For a long time I’ve used limitDays: ‘1’, and excludedEvents: [ ‘Tutor Time’ ], to limit my calendar display to show my kids upcoming lessons for the day, synced from their school calendar.
Since the last update, limitDays seems to limit the number of events that show, rather than the number of days. Setting it to ‘1’ shows the first lesson of the day, ‘2’ shows the first two lessons etc.
excludedEvents also seems to have no effect any more … the first event of every day is ‘Tutor Time’ so I exclude that, but it has started appearing since the latest update.
I can’t see anything in the release notes that’d explain that ?
@fredric.nil yes as @sdetweil says it needed to be .MMM-Scrapey td {} to have any effect.
Try this in your custom CSS, I think it’s the line height you want to adjust, not the padding:
.MMM-Scrapey td {
line-height: 1;
}
MagicMirror default line height on the body element is 1.5 so I think everything inherits that unless overidden.
@sdetweil yes, I have apiVersion: ‘2.5’ in my config - I didn’t change that recently though, I think I changed that perhaps a year ago when it stopped working previously … whatever the latest update did, I now need the /weather endpoint specified as well. All good though, it’s working fine now.
@chris_d glad you’ve found it useful, and that’s a good idea for the module option - I actually had the same issue with the data I was scraping and was using some custom CSS to clean up the formatting, but a plain text option in the module is a better approach.
So, I’ve added a new ‘plainText’ option to the config. The default is still to use HTML in case anyone was making use of that (I doubt it but you never know), you’ll need to add ‘plainText: true’ to the module config to strip the HTML formatting.
The same happened to me, my fix was a bit simpler but maybe only temporary …
It seems the default endpoint has changed - the documentation still says that the default for weatherEndpoint should be ‘/weather’, but I think in the latest update that changed to ‘/onecall’. For those of us with old api keys I think it’s still ok to use the /weather endpoint, you just need to specify that in the config now that it’s no longer the default.
weatherEndpoint: '/weather',