Sharing a setup that’s been working well for me, in case it’s useful to anyone else juggling a physical MM display on aging/fragile hardware.
Background: I had MagicMirror running natively on a Raspberry Pi 3B with a monitor attached. I wanted to move to Docker, but didn’t want to run Docker on the same Pi that’s driving the display, that Pi is old, and I didn’t want display/GPU quirks tangled up with container management.

What I ended up with instead:

• MagicMirror runs as a single Docker container on a separate, more capable Pi on the same home network , completely headless, no monitor attached.
• The Pi with the physical monitor doesn’t run MagicMirror at all anymore. It just runs a browser in kiosk mode, pointed at a small local reverse-proxy process running on that same Pi, which in turn proxies through to the Docker container’s web UI.
  Why the proxy, instead of just pointing the browser straight at containerhost:8080?
  Two reasons:

1. MagicMirror sends X-Frame-Options: SAMEORIGIN, which matters if you want to wrap the feed in your own page (see #2).
2. I wanted a couple of small custom status overlays on the display itself — e.g. a banner if the Docker host becomes unreachable, or if internet connectivity drops but the local container is still fine. To overlay anything on top of MM’s own page you need it loaded same-origin, so a tiny local Node reverse-proxy on the display Pi re-serves the container’s content from localhost, strips that header, and the wrapper page around it handles the status banners.
   Why this arrangement, generally:

One MagicMirror instance/config to maintain, no matter how many physical screens you eventually want — each display Pi is just “a browser + a small proxy,” nothing module- or backend-specific.
Any hardware-specific pain (GPU driver quirks, monitor power management, etc.) on the display Pi stays isolated from the actual MagicMirror process, a crash or leak in a module’s backend logic can’t take the display down, since they’re not sharing a process tree anymore.

Honest caveat: this doesn’t make the display Pi itself lighter, it’s still a real browser doing real DOM/JS rendering and image decoding locally, so don’t expect a resource-usage miracle on the display side. What you get is architectural: single source of truth for MM itself, and a much smaller, simpler thing running on whatever hardware is stuck driving a screen
I’m pairing this with a Radar motion sensor for wake-on-motion, poll a GPIO pin and call dpms_control on on a HIGH reading, dpms_control off after N minutes of no motion. One thing worth knowing if you’re doing the same: Trixie’s kernel exposes the GPIO chip at a different base offset than older Raspberry Pi OS versions, so older libraries like onoff that write raw BCM pin numbers straight to sysfs (/sys/class/gpio/export) fail with EINVAL. Shelling out to gpioget/gpiomon from libgpiod-tools instead sidesteps that entirely:

Hey everyone,

I got the MM-TomTomCalculateRouteTraffic module and it is making calls with a TomTom API - now i would like to have really high amount of calls in the morning (about once every 30s) and non after a certain time.

Is it possible to config a module to be deactivated after a certain time? e.g. run it from 7-8am and then not?

I (thought I’ve) updated everything for my Proxmox MM container: container to Trixie, node.js to stable, all modules to latest commits, AND MM itself. Here’s what the logs show:

[2026-08-21 16:27:57.244] [INFO] [systeminformation]

System Information

MM: version: v2.37.0; git: 53fc814f; branch: master

• SYSTEM: manufacturer: Gigabyte Technology Co., Ltd.; model: Z390 AORUS PRO; virtual: false
• OS: platform: linux; distro: Debian GNU/Linux; release: 13; arch: x64; kernel: 7.0.2-6-pve
• VERSIONS: electron: undefined; used node: 24.19.0; installed node: 24.19.0; npm: 11.17.0; pm2: 5.4.1

But I still get an alert that I am 11 commits behind :-(

What am I forgetting?

Re: iCloud photos
I am trying to use pyicloud library but do not have it working yet.

I’ve been working on MMM-MessageCenter, a module that gives notifications from different sources one consistent place on the mirror.

The idea came from a pretty simple problem: a notification appears, disappears, and nobody knows whether anyone actually saw it. Different modules and services also handle alerts differently, so important information can easily get lost.

MessageCenter adds a small notification history with clear unread, viewed, acknowledged, dismissed, and expired states.

What can send messages?

Everything:

• Other MagicMirror modules
• MagicMirror’s bundled Weather module
• MMM-Remote-Control
• Home Assistant
• REST webhooks
• MQTT
• Local Unix-socket scripts and system monitors

It intentionally doesn’t collect every internal MagicMirror event. Modules either use the MessageCenter API or an explicitly enabled adapter, which keeps refresh, navigation, and module-control traffic out of the inbox.

A few examples

A dishwasher notification can briefly appear as an alert and then remain in history until someone views it.

A doorbell message can include a camera snapshot captured when the event happened, so the image doesn’t change before somebody checks it.

The standard MagicMirror Weather module can add a “Rain approaching” message without requiring a separate weather service.

A local monitoring script can report low disk space, high temperature, network trouble, or another condition that should be visible on the mirror.

Different ways to display it

MessageCenter can be used as:

• A compact list in a normal MagicMirror region
• A full-page message inbox
• A touch-friendly display with message controls
• A non-touch display that simply shows the newest messages

It can show temporary alerts, retain message history, expire old messages, update existing messages by ID, and publish attention events for other integrations. It only says that something needs attention, leaving other modules and integrations free to decide what that means.

Configuration, payload examples, and documentation:

https://github.com/bwente/MMM-MessageCenter

If your MM is using the default Weather module with the EnvCanada provider or the 3rd-party MMM-EnvCanada module, there are some upcoming changes announced by Environment Canada that might impact your MM config in some very specific cases.

Change #1: A handful of siteCode values are changing and will require a minor config.js update. The changes are:

Change#2: A handful of siteCode locations are being relocated to new locations within 5km of the original. This is unlikely to require config.js updates but the changes have been highlighted as FYI. They are:

These Env Canada changes will come into effect as of Oct 6, 2026 are being done to align with other Canadian government databases. I suspect they will impact a very small number of module users (if any).

Query: What would cause a MagicMirror installed on a VM to fill up the 50 GiB VM virtual disk over 4 months?

I have an instance of MagicMirror installed in a Linux VM running under TrueNAS, which is mostly used to try out modules, configurations or layouts without disturbing the main MagicMirror. When I went to look at it yesterday I found the VM running, but not MM. PM2 status did not show it running, and it would [re]start. MagicMirror is the only thing installed on the VM, and running modules were newsfeed and default weather [5 instances],

Some searching tells me the virtual disk of 50 GiB is full! I have expanded the virtual disk size [resized the zvol], but am unable to extend the partition and filesystem as I get an error. I think it was along the lines of “you don’t have enough free space in /var/cache/apt/archives”.

At this point it appeared the best route would be to just build a new VM and install MM, but when I went to start making notes to record what I was doing - I found this same thing happened some months ago. The current VM is an upsized VM that similarly locked up.

Since starting over will not apparently solve the underlying root cause, I need some help. Thanks in advance.

Good evening!

After a lot of on-and-off wrestling with Spotify on my mirror, I finally sat down and built something new — and I’m genuinely happy with how it turned out: MMM-NowPlayingOnVolumio.

The backstory (some of you will feel this pain 🙂)

I’ve run Spotify through librespot for long time now, and it kept breaking in ever-new and creative ways. The latest one — the login5 change — finally finished it off for me: hard to fix, only community support and no chances that things will become better.
So I decided finally to jump ship to Tidal.

That meant my beloved (forked) MMM-NowPlayingOnSpotify was suddenly out of a job — Tidal doesn’t expose a “currently playing” API the way Spotify does. The existing Volumio modules would have been the obvious fallback… but they’re pretty old (8 and 9 years) and simply too old for a current Trixie / Node 22 setup (ancient socket.io and friends). So: a new module, written from scratch against current Volumio (4.x) and current Node.

The silver lining

Moving to Tidal pushed me onto Volumio’s Premium tier — and that turned unexpectedly even into a
real win. (I’m not THAT big fan of “payment-plans” at all - but: I get noticeably better sound quality (Spotify via Volumio is quality-limited by intent), and (that’s the surprise) the Premium plan unlocks Volumio’s Music Metadata, so the module can show a proper artist biography right on the mirror. More info and better sound — I’ll happily take that trade.

What it does

• Shows what Volumio is playing — cover, title, artist, progress bar and
  elapsed/total time.
• Optional artist biography from Volumio’s Music Metadata (Premium), Between Artists’s Name and progreess bar - shown page by page with a gentle cross-fade — no jittery scrolling.- Because Volumio is the source of truth, it works with any source: Tidal, Spotify, Qobuz, web radio, local files — no changes when you switch services.
• When nothing is playing it quietly fades to the Volumio logo.
• Clean split: the backend holds a persistent socket.io connection and does the work, the frontend just displays. It reconnects on its own and survives browser reloads.

Config

Basically just your Volumio host:
(some options more available - see documentaion on github)

{
  module: "MMM-NowPlayingOnVolumio",
  position: "bottom_left",
  // header: "Volumio",
  config: {
    volumioHost: "volumio.local",
    showArtistBio: true
  }
}

One dev note for the curious: current Volumio runs a socket.io 2.x server, so socket.io-client is pinned to exactly 2.4.0 — 2.5.0 and the 4.x line won’t connect. That one cost a moment to figure out. 🙂

GitHub (MIT): https://github.com/rkorell/MMM-NowPlayingOnVolumio

Feedback, issues and PRs are very welcome — especially from fellow Volumionists.

Happy mirroring!

Warmest regards,
Ralf

(module is included in 3rd-party-module-list)

Update socket issue 1 No data received yet .
It is already second time with this problem. Last time update helped. This time not. What has been changed? It still uses vendo profile besides I changed in config.js to “db”
Edit: by fahrplanguru also only flixbus is available

Hi, I have a magic mirror and I have added new albums to my google photos and they are not coming through to the magic mirror the old albums still show but not the new one. Any ideas on what i need to do? Also haven’t changed anything for a while, so have forgotten how to do anything. Thank is advance for any help.

I have things looking basically how I want it. My main goal was a digital wall calendar to replace our large paper wall calendar. My only complaint with MMM-MonthlyCalendar is that I would love to show 6 weeks to be able to see further out (and better make use of the space). I tried switching to MMM-CalendarExt3, but text wrapping is a non-negotiable for me, on top of frustrations getting it to sit in the right space on screen. Is it possible to change the number of weeks shown on MMM-MonthlyCalendar? Is there a better calendar mod for what I’m trying to accomplish?

Hi.
I am a great fan of the MMM-MyCommute module, but for some unknown reason it has stopped showing up.
I have narrowed it down to the

hideDays

parameter.
If I comment this parameter, the module shows up. Once I reactivate it, nothing shows up.
The logs do not show any errors, as the module is working - just not as intended.
As usual, I want to hide this module on the weekend

hideDays: [0,6],

Any idear/clue/tip what is going on here ?
Thanks

I’ve been working on a small ambient information appliance called Seymour.

The inspiration is the original 3Com Audrey internet appliance. Seymour is built around a Raspberry Pi, a 7-inch touchscreen, a rotary encoder, an illuminated WLED ring, an internal speaker, and a 3D-printed enclosure. I chose MagicMirror because its module ecosystem already provides most of the useful building blocks.

Instead of presenting everything as one dashboard, Seymour organizes modules into channels. Pressing the encoder opens the channel selector, rotating chooses a channel, and pressing again opens it. The touchscreen is also available.

The current prototype includes clock, weather, news, calendar, messages, a kitchen timer, and local music playback through Music Assistant. The LED ring provides status and attention feedback, while the speaker handles music and timer sounds.

It is still a working prototype, although it may already be close to the finished personal appliance I wanted. I’m continuing to polish the documentation and software before making the repositories public.

I caught hell today because I had our anniversary date wrong in MM. I use google calendar to feed the default calendar module and it seems that if I have an all day event scheduled it puts that date as one day prior to the actual event. I verified the date is correct on my calendar and don’t see any reason for it to be incorrect in MM. I checked another all day event coming up and MM displayed it’s date as one day prior also.

I’m running on an RPI 5 with 4GB of memory and a 256GB NVME. MM is running as a container on docker. MMversion is 2.34.0.

I also have MM , 2.34.0, running with docker on my laptop 32GB memory and 1TB SSD dual boot with Ubuntu 26.04 and win 11. The dates are correct on the laptop, running Linux.

Is there any thing I can do to correct this since it is running on a default module?

TIA, Ron

super basic question, both modules are from the same developer, but both are missing the most basic info of how to install.

in instances like this how do I find the first bit of info to put in terminal to start pulling down the info needed for a module?

Cheers.

After upgrading MM awhile ago my Zero 2W started having issues where MM would intermittently freeze or not start at all after a reboot. I tried a bunch of different things but nothing improved the situation.

I had an old Pi 3B+ lying around and decided to try that. It was solid for over a week in testing so I replaced the Pi in my mirror with the 3B+ and it’s been great.

I have two instances of weather in my config. The first for current and using my pws provider. The second for forecast using weathergov. Both display data but the forecast seems to ignore the fade: false option. Here are the module entries from my config.js.

  ```

{
module: “weather”,
position: “top_right”,
order: “1”,
header: “Our Weather Station”,
config: {
weatherProvider: “pws”,
stationId: “KTXFARME145”,
apiKey: “xxxxx”,
type: “current”
},
disabled: false,
label: “instance 1”,
hiddenOnStartup: false,
configDeepMerge: false,
animateIn: “none”,
animateOut: “none”,
index: 0
},
{
module: “weather”,
position: “top_right”,
order: “2”,
header: “Weather Forecast”,
config: {
weatherProvider: “weathergov”,
type: “forecast”,
lat: 33.173,
lon: -96.332
},
colored: true,
fade: false,
fadePoint: “1”,
maxEntries: “7”,
maxNumberOfDays: “7”,
disabled: false,
label: “instance 2”,
hiddenOnStartup: false,
configDeepMerge: false,
animateIn: “none”,
animateOut: “none”,
index: 1
},

I have updated the MMM-PWSWeather provider v2.0 for MM v2.35.0+. The provider pws now runs as a server-side provider API. If you are running an older version of MM you can download the initial release.

Hey!

Pretty new at everything about MM2. Built one a few years ago but forgot most about how everything work.

Anywho, I got my mirror set up and running a few simple modules, but have some issues with one specific module. Tried to comment in the thread about the module about a year ago

https://forum.magicmirror.builders/topic/5582/mmm-skolmaten-shows-school-lunch-menus-in-sweden-from-skolmaten-se?page=1

but didn´t get any answer. So I guess i´ll try my luck in this threat.

The module is called MMM-Skolmaten, a swedish module that show what food that is served in swedish schools. I´ve installed it and added it to my confiq.js. It shows up when i start MM. But the info keeps saying “loading” and nothing happends.

I´ve tried re-installing . Changed the rss from default to diffent rss without any luck.
In the module thread it says to " Do a “npm install rss-parser@2.12.0”. But it doesn´t work.

Guess its a long shot to solve this, but I thought i would give it a try :)

The module thread is in english if there is any info that could help.

Thanks!

Hey everyone,

I built a module to show upcoming train/bus/light rail departures from any Danish stop, using the Rejseplanen API 2.0. Wanted to share in case it’s useful to other Danish (or Scandinavian-adjacent) mirror builders.

Features:

Departure times with real-time delay updates
Transport-type icons (S-Tog, Bus, Letbane)
Filter by transport type
Time-window filtering (e.g. only show departures within the next hour)
Walking-time reachability — dims departures you can’t realistically catch based on how long it takes you to get to the stop
Optional platform/track display
Dynamic header showing your configured stop name

Screenshot:

Repo: https://github.com/SyS64760/MMM-DSBDepartures

Requires a free Rejseplanen Labs API key (non-commercial use gets 50,000 calls/month, no cost). Setup instructions and full config options are in the README.

Feedback and issues welcome — happy to improve it if others find bugs or want features added.