Read the statement by Michael Teeuw here.
2.32.0 Calendar module limitDays and excludedEvents stopped working
-
@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 -dworks 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 bashworks 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", -
@AndyHazz said in 2.32.0 Calendar module limitDays and excludedEvents stopped working:
but in case you’re onto something
Not sure, but you have a rather old version of MMM-Remote-Control which is only compatible to a limited extent with MM 2.32.0. If you update MMM-Remote-Control, the start of MM may not abort like above.
-
@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.
-
@AndyHazz Unfortunately, I don’t know if I can help any further here. The error message (
[ERROR] table not found in HTML.) is indeed from MMM-Scrapey - I have created a pull request for the module to improve logging, at least in the future. -
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?
- limitDays has changed to limit the number of calendar items, not the number of days worth of calendar items
- excludedEvents appears to do nothing any more, events matching excluded words have started showing when prior to 2.32.0 they were hidden
If it’s only affecting me, I’ll probably try rebuilding my setup from scratch.
-
@AndyHazz what release were you on prior to the upgrade?
I don’t see any code change from 2.31
| correction, there is a test of date after change here. -
@AndyHazz can you show your calendar config, xxx out the URLs.
-
@AndyHazz I should note that this property is NOT a sequential limit of days from today
it is UNIQUE days INCLUDING today
limitDays:2
so if there no events til next Thursday, that is the 1st day
and no events til the following Tuesday, that is the second daywhich is different than event tomorrow and saturday, but only show tomorrow… (2 consecutive days gets today and tomorrow), or two days from NOW gets today/thurs/friday, but still not saturday.
-
@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' } ] } }, -
@AndyHazz Do you mind sharing your ICS, anonymized off course.
-
@AndyHazz found it…
comparing date AND TIME oops…
edit modules/default/calendar/calendar.js
approx line 708
change the lines marked below with //if (this.config.limitDays > 0) { let newEvents = []; let lastDate = today.clone().subtract(1, "days").startOf('day'); // add .startOf('day'), note dot let days = 0; for (const ev of events) { let eventDate = this.timestampToMoment(ev.startDate).startOf('day'); // add .startOf('day'), note dot -
@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?
-
@AndyHazz working on it
-
@AndyHazz ok, got it too… this one looks like a javascript difference in scopes…
I added the Log.debug lines, they are not important
modules/default/calendar/calendarfetcherutils.js , starting line 18 (4 changes total)
see // change this lineshouldEventBeExcluded (config, title) { let result = { // change this line excluded: false, until: null }; for (let f in config.excludedEvents) { let filter = config.excludedEvents[f], // this line uses the same variable name, filter, now we have two, 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(); } Log.debug("should be excluded ", testTitle, filter, useRegex, regexFlags) if (CalendarFetcherUtils.titleFilterApplies(testTitle, filter, useRegex, regexFlags)) { if (until) { result.until = until; // change this line } else { Log.debug("event should be excluded = true,", testTitle ) result.excluded = true; // change this line } Log.debug("filter applies result =", result) break; } } Log.debug("filter applies returning =", result) return result; // change this line }, -
@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’?
-
@AndyHazz hm…
my config parm for excluded EventsI added one event for saturday… without excluded it shows, with excluded it doesn’t
excludedEvents: [ 'Birthday' ],I checked the changed lines and only see those 4
- is old line
+ is new line* until: the date until the event should be excluded. */ shouldEventBeExcluded (config, title) { - let filter = { + let result = { excluded: false, until: null }; @@ -52,17 +52,20 @@ const CalendarFetcherUtils = { } else { filter = filter.toLowerCase(); } if (CalendarFetcherUtils.titleFilterApplies(testTitle, filter, useRegex, regexFlags)) { if (until) { - filter.until = until; + result.until = until; } else { - filter.excluded = true; + result.excluded = true; } break; } } - return filter; + return result; }, -
@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. -
@AndyHazz note that the excluded events is an ARRAY (so for loop to look thru them )
test ALL til find one that is true (CalendarFetcherUtils.titleFilterApplies returns true) , or notAND the item in the array can be an object with more specific controls, or a string
MM doc entries on separate lines
[ 'Birthday', // text 'Hide This Event', // text {filterBy: 'Payment', until: '6 days', caseSensitive: true}, // complex, but text {filterBy: '^[0-9]{1,}.*', regex: true} // complex, uses regex ]AND the list/array can be a MIX of those things,
and the string test is the test string is SOMEWHERE in the title, doesn’t have to BE the entire title
-
@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 -
-
@AndyHazz can’t think of any, MM is case sensitive, some times people get the case wrong and we don’t report unexpected parms or missing parms…
but you’ve been using that so, it doesn’t shouldn’t be an issue for you
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login