I’ve just done a clean install of MagicMirrorOS (based on @karsten13 ’s docker install) - 4 Jul 64 bit build.

The mm container just seems to be stuck in a restart loop.

Suggestions to troubleshoot?

scottwalsh@calendar:/opt/mm/run $ docker ps
CONTAINER ID   IMAGE                                      COMMAND                  CREATED         STATUS                          PORTS      NAMES
7feb4bcf2b57   karsten13/magicmirror:latest               "/usr/bin/tini -- ./…"   3 minutes ago   Restarting (1) 35 seconds ago              mm
c4ecd7a1a688   ghcr.io/nicholas-fedor/watchtower:latest   "/watchtower --inter…"   3 minutes ago   Up 3 minutes (healthy)          8080/tcp   watchtower
c0d1ee7dcd97   karsten13/labwc:latest                     "/entrypoint.sh"         3 minutes ago   Up 3 minutes (healthy)                     labwc
scottwalsh@calendar:/opt/mm/run $ 
scottwalsh@calendar:/opt/mm/run $ 
scottwalsh@calendar:/opt/mm/run $ 
scottwalsh@calendar:/opt/mm/run $ docker logs mm
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
/opt/magic_mirror/node_modules/electron/dist/electron: /opt/magic_mirror/node_modules/electron/dist/electron: cannot execute binary file
scottwalsh@calendar:/opt/mm/run $ 
scottwalsh@calendar:/opt/mm/run $ 
scottwalsh@calendar:/opt/mm/run $ docker down
docker: unknown command: docker down

Run 'docker --help' for more information
scottwalsh@calendar:/opt/mm/run $ docker compose down
[+] down 5/5
 ✔ Container watchtower   Removed                                                                                                                               0.9s
 ✔ Container mmpm         Removed                                                                                                                               0.1s
 ✔ Container mm           Removed                                                                                                                               0.1s
 ✔ Container labwc        Removed                                                                                                                               1.4s
 ✔ Network magicmirror_mm Removed                                                                                                                               0.2s
scottwalsh@calendar:/opt/mm/run $ docker compose up -d --force-recreate
[+] up 4/5
 ✔ Network magicmirror_mm Created                                                                                                                               0.1s
 ✔ Container watchtower   Started                                                                                                                               2.1s
 ✔ Container labwc        Healthy                                                                                                                               7.6s
 ⠋ Container mm           Starting                                                                                                                              7.1s
 ✔ Container mmpm         Created                                                                                                                               0.2s
magicmirror hook exited with status 137
scottwalsh@calendar:/opt/mm/run $

Hi all,

if you use MMM-NowPlayingOnSpotify (raywo’s lovely “now playing” module), there’s a
change coming from Spotify that will quietly break it — and I wanted to share both the
problem and a fix.

The problem

Spotify announced that, starting 20 July 2026, user refresh tokens will expire after 6
months (blog (https://developer.spotify.com/blog/2026-06-18-refresh-token-expiration)).
Until now those tokens were effectively permanent, so the module just stored one and
kept minting access tokens forever. Once a refresh token expires, Spotify returns an
invalid_grant error, and the app is expected to discard it and send the user through
the sign-in flow again.

The original module doesn’t handle that case: it logs the error and silently falls back
to the “nothing is playing” logo. So one day your mirror would just… stop showing
songs, with no hint why — while hammering the API once per second with a dead token.

First attempt: the polite way

I opened an issue on the original repo to flag it. Unfortunately the project has been
unmaintained for ~6 years, and there was no response. So rather than let everyone’s
module quietly die this summer, I forked it and did the work.

The fix: a fork with proper token handling

👉 https://github.com/rkorell/MMM-NowPlayingOnSpotify (v2.0.0)

What it does now:

• Detects invalid_grant, stops retrying, and shows a clear red re-authorization banner
  on the mirror instead of pretending nothing’s playing.
• Proactive warning ~2 weeks before the hard expiry (a smaller banner above the cover
  art) — the music keeps playing, so it’s never a surprise outage.
• Self-managed token store (tokens.json, git-ignored) instead of tokens in config.js,
  so rotated/renewed tokens are actually persisted. You only keep clientID, clientSecret
  and redirectURI in your config now.
• Integrated re-authorization: the module runs a tiny local auth server; you
  re-authorize from a browser and it recovers in-process, no restart.
• Under the hood: a full refactor to native fetch/http — the deprecated request/express
  dependencies are gone, so it’s now zero runtime dependencies — plus a proper backend
  poll loop and English/German translations.

One wrinkle worth knowing (loopback + SSH tunnel)

Spotify only accepts http redirect URIs for loopback addresses now — a LAN IP or
hostname over http is rejected at runtime as insecure, and localhost isn’t allowed
either. So the redirect URI is http://127.0.0.1:8888/callback. Since a mirror is
headless, the easiest way to re-authorize from your laptop is a one-line SSH tunnel:

ssh -L 8888:127.0.0.1:8888 pi@<mirror-ip>

…then open http://127.0.0.1:8888 in your laptop’s browser. Full details are in the
README.

Happy to help anyone getting it running, and a big thank-you to raywo for the original
module that many of us have enjoyed for years.

This may be a little late but that’s what I get when you only use the free AI subscription. This module will put the FIFA World Cup Bracket on your Magic Mirror. Looks nice so far.
https://github.com/msimon360/MMM-FIFAWorldCup

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.