Release Notes

Thanks to: @angeldeejay, @egeekial, @khassel, @KristjanESPERANTO, @MikeBishop, @rejas

⚠️ This release needs nodejs version >=22.21.1 <23 || >=24 (no change to previous release)

Compare to previous Release v2.36.0

[core]

• Prepare Release 2.37.0 (#4193)
• fix(electron): map IPv6 :: wildcard to localhost (#4188)
• refactor(main): modernize DOM update flow with async/await (#4186)
• refactor(main): simplify _updateDom with async/await (#4185)
• fix(security): prevent unauthorized secret expansion in socket payloads (#4184)
• refactor(main): simplify updateDomWithContent async flow (#4182)
• fix: modules losing data after HTTP 304 responses (#4180)
• chore: add missing core defaults (#4181)
• fix(server): enforce ipWhitelist for Socket.IO too (#4169)
• feat(systeminfo): include Git hash and branch in system information log (#4167)
• feat(electron): support object-based electronSwitches (#4161)
• systeminformation thread not ending: move error handling from utils to app (#4160)
• fix systeminformation thread not ending (#4155)
• refactor: use ES module imports in browser core (#4158)
• refactor(core): remove old Object.assign polyfill (#4157)
• refactor: rewrite Module as an ES6 class (#4151)
• refactor: rewrite NodeHelper as an ES6 class (#4147)
• update eletron to v42 (#4144)
• refactor(utils): drop ajv dependency (#4142)
• fix(systeminformation): output right ‘used node’ version (from parent process) (#4141)
• fix: skip postinstall git clean when not in a git repository (#4139)
• Remove unnecessary conditionals and fix falsy property check in imperial conversion (#4135)
• update version in package.json

[dependencies]

• update dependencies (#4191)
• Bump actions/checkout from 6 to 7 (#4190)
• chore: update dependencies and adjust import path for SunCalc (#4189)
• update dependencies incl. electron and revert yauzl-electron-install-fix (#4183)
• update dependencies, add electron fix in package.json (#4175)
• chore: update dependencies (#4162)
• Bump actions/dependency-review-action from 4 to 5 (#4152)
• Unify linting: replace Stylelint and markdownlint with ESLint (#4148)
• update dependencies and workflows to node v26 (#4140)

[modules/alert]

• CodeQL cleanup for alerts #18, #19, #20 (#4153)
• fix: resolve CodeQL alerts #24 and #26 (#4145)
• fix(electron): resolve CodeQL alerts #22 and #25 in electron.js (#4136)

[modules/calendar]

• perf(calendar): pre-filter ICS data before parsing (#4168)
• perf(calendar): use async ICS parsing to avoid blocking event loop (#4143)

[modules/newsfeed]

• [newsfeed] add allowBasicHtmlTags option for basic emphasis (#4176)

[modules/updatenotification]

• fix(updatenotification): don’t spawn a child process when running under PM2 (#4166)
• fix(updatenotification): use process.argv[0] as restart binary (#4163)
• fix(updatenotification): preserve start mode on restart (#4156)
• fix(updatenotification): fix ref diff parsing for fetch --dry-run (#4138)
• refactor(updatenotification): replace pm2 usage with node logic (#4134)

[modules/weather]

• feat(weather): add Buienradar provider (#4164)

[testing]

• remove warning in unit tests (for nodejs >= v25) (#4149)
• polish HTTP 304 docs/test/handling (#4129)

Hello everyone,
Since upgrading to MM version 2.36.x, I’ve been having a problem with the display of my images, which are controlled via the calendar.
I use an ICS file to display the collection times for my various bins on MM.
Up to version 2.34.x, this worked quite smoothly with a little trick.
This is what the display looked like in version 2.34.x (grey, blue, green images):

Here is the custom.css file for the calendar:

The names and locations of the pictures:

The excerpt from the config.js file for the calendar module:

And finally, here’s a short extract from my ics file:

I used Sam’s Backup&Restore script to back up my modules. I then installed the new version 2.36.x on a new SD card and restored the modules using Sam’s script.
Basically, everything is working again – apart from the display of the coloured bins.
A test via a browser on my PC within my network showed me that I can’t display the images in the CSS folder.
Attempts using the “default” or “vendor” directories also failed to produce the desired result.
Does anyone have any idea how I can get the icons to display again?
Many thanks

Hello,
I’m trying to get MMM-Anylist to show white text on an dark opaque background. How is this accomplished.
Thanks!

Is there already a MagicMirror module that can be modified to display iCloud shared albums?

Thanks in advance.

Hi. I have my MagicMirror pretty much set up the way I want except for one little thing…

I would like the timed events to have the same block coloring as the full day events. Right now, it’s just the text that’s colored. Is there a way to do this?

I eventually will also change the color based on the keyword in the title which I already know how to do for the text. I’m assuming it’ll be the same for the full entry coloring?

Description:

Displays currently free and upcoming free games from the Epic Games Store.

Screenshots:

Download:

// Remove the spaces and add your Github module repository
GitHub: https://github.com/ACE-012/MMM-EpicFreeGames

v1.0.0

• Initial release

Hi there,

I’m trying to move an embedded website up a little, to the page header is hidden and I can show more effective data.
I’ve tried it using the beneath option in custom.css, but that does not seem to do the trick. Any other suggestions?

Also, is there an option to do this with different values for each embedded url, since it might differ per page?

.MMM-EmbedURL .embed .embeded {
top: -100px;
}

Updated PlaceInfo for a changed API spec for openweathermap (a long time ago!)

https://github.com/njwilliams/MMM-PlaceInfo

Provides very simple weather and currency exchange information for different cities

It’s been a while, but a new release - v2.0.0 - is now published. Fixes a bunch of cosmetic bugs, updated for latest NodeJS, and adds a new feature of animated stroke order for Kanji.

https://github.com/njwilliams/MMM-Kanji-Random

I’m using this daily since my Japanese learning is still very basic, so it’s a tool to help me memorize new words.

Re: Global module positioning

zIndex config option is not applied — containers always render at z-index: 9999

Description

The README documents a zIndex field per module entry (and references it in the Troubleshooting section: “Adjust zIndex in your module config”), but setting it has no effect. Positioned containers are always rendered with z-index: 9999 regardless of the configured value.

Steps to reproduce

1. Configure a module with an explicit zIndex:

   {
     module: "MMM-GlobalPositioner",
     config: {
       debug: false,
       delay: 1000,
       maxAttempts: 5,
       modules: [
         { name: "MMM-GoogleSheets", position: { top: 160, left: 20 }, zIndex: 1 }
       ]
     }
   }
   

2. Restart MagicMirror.
3. Inspect the generated container in DevTools.

Expected behavior

The container’s inline style should reflect z-index: 1.

Actual behavior

The container is still rendered with z-index: 9999, e.g.:

<div id="mm-global-container-MMM-GoogleSheets"
     style="position: fixed; z-index: 9999; pointer-events: none; left: 20px; top: 160px;">

Impact

This makes it impossible to layer GlobalPositioner-managed modules underneath other overlay-based modules — for example, screen-dimming modules like MMM-AutoDimmer/MMM-Dimmer, which apply opacity via a fullscreen_above overlay. Because GlobalPositioner’s containers are hardcoded to z-index: 9999, modules repositioned by it always render above such overlays and never get dimmed, even though dimming works correctly for all normally-positioned modules.

Workaround

Forcing the z-index via a custom stylesheet (config/custom.css) with !important, since the module sets it as an inline style:

div[id^="mm-global-container-"] {
  z-index: 1 !important;
}

This resolves the visual conflict, but it would be better if the documented zIndex config option actually worked, so this kind of override isn’t necessary.

Environment

• MagicMirror²: v2.36.0 (commit fb41d24ef522e91e802e2a623ff6afbddeb3c9d8)
• Node.js: v22.21.1
• OS: Raspberry Pi OS

Otherwise, GREAT module!
Karl

Hi everyone,

I’d like to share a new module I built for those of you based in Greece.

MMM-eshopspecials displays the daily special offer from e-shop.gr, one of the largest online retailers in Greece, directly on your Magic Mirror. Every day at 12:00 the module automatically refreshes to show the new deal — no need to set updateInterval. It shows the product image, title, price and a short description.

You can find it here:
👉 https://github.com/mariosgouros/MMM-eshopspecials

Feedback and suggestions are welcome!

Hello all,

As the PI prices go up and it’s getting insanely pricy, i was wondering if a used laptop with touch screen can be used as MM2 display with a touch screen feature?
If so, what laptop is recommended and what OS should i run on it?

I’m looking to build a dedicated screen for chores, alarms and reminders for kids.

I would propose the following as a transitional addition to the configuration system.

1. Add a simple GUI based configuration utility or web frontend to the system (there are some modules that attempt to do this already so it would be minimal work to adapt it to the following second detail.

2. For the simple GUI enforce a configuration contract with modules that follows a defined schema using [tags] to define types of information blocks. For a module to be able to show up in the GUI developers will need to briefly update their github repository to add a contract.yaml etc file that defines the default settings for the module.

This merges into the main program a feature that other modules have attempted to create while transitioning the system to a true contract based configuration system that allows for much easier user settings changes. The onus is on the module developers to present the correct base configuration file from which the dynamic configuration file for magicmirror can then be crafted from.

Just an FYI on anyone wanting to load the Letterboxd module you will need to manually update Node fetch to Version 2 at least, and install the cheerio as these are not included on the initial npm install of the modules dependencies.

cd /MagicMirror/modules/MMM-Letterboxd

npm install node-fetch@2

once installed, head back to

cd MagicMirror/modules/MMM-Letterboxd

npm install cheerio

restart magic mirror and it should work :)

I’d like to introduce a new module: MMM-CanvasCalendar

https://github.com/dbeltjr/MMM-CanvasCalendar

I previously maintained MMM-Canvas, a fork of another module that used the Canvas API to display upcoming assignments. After the recent Canvas data breach, my institution stopped issuing API access tokens — so that approach was no longer viable.

As an alternative, I worked with AI to take MagicMirror’s default calendar module and customize it specifically for the Canvas iCal feed. It has similar functionality to MMM-Canvas with a few additions, all documented in the README.

One limitation worth noting upfront: because the Canvas iCal feed does not include submission status, the module cannot automatically remove assignments you’ve already completed.
They will drop off once their due date has passed.

I’m not a developer by trade, but I’ve found AI a useful tool for modifying and creating modules like this. Feedback and suggestions are welcome!