Description:

A newly refreshed fork of MMM-KitchenTimer, a responsive, touch-friendly countdown timer for MagicMirror².

It provides a large countdown display, configurable quick-duration presets, and accessible controls for touch, mouse, and keyboard. Tap the time display to pause or resume the countdown, and use the Reset or Dismiss control to cancel the timer or silence its alarm.

The module supports compact and full-screen layouts, optional alarm and button sounds, and reliable wall-clock timing. Active timers continue running and can finish while the module is hidden by page-management modules such as MMM-pages.

MMM-KitchenTimer also provides incoming and outgoing MagicMirror notifications. Other modules can start, add time to, pause, resume, reset, or dismiss the timer. Semantic state notifications make it possible to integrate voice assistants, smart lights, MQTT bridges, physical controls, notification centers, and other automations without embedding hardware-specific behavior in the timer.

This is a maintained fork of the module originally created by Tom Short, published with his permission. The original MIT attribution and existing configuration compatibility have been preserved.

Screenshots:

Download:

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

Installation:

cd ~/MagicMirror/modules
git clone https://github.com/bwente/MMM-KitchenTimer.git

Version 1.0.1

• Keep active timers and completion events running while hidden
• Improve compatibility with page-management modules such as MMM-pages

Version 1.0.0

• Modernized the original module as a maintained MagicMirror² module
• Added large, touch-friendly controls
• Added configurable quick-duration presets
• Added tap-to-pause and resume behavior
• Added compact and full-screen layouts
• Added incoming timer-control notifications
• Added outgoing semantic state and progress notifications
• Preserved the original configuration options and MIT attribution

I built MMM-OllamaHostMonitor to keep an eye on the Mac Studio that runs my local LLMs, right on the MagicMirror. It shows live GPU/CPU usage & power, unified memory, the Ollama models currently resident (with VRAM), and Hermes status.

Why a companion agent + MQTT? macOS doesn’t expose GPU/memory over HTTP, and hermes-agent has no metrics endpoint. So a tiny collector runs on the Mac (using the sudoless macmon, the Ollama REST API, and process inspection) and publishes retained JSON to your MQTT broker. The module just subscribes — it’s push-based, needs no inbound ports on the Mac, and populates instantly on boot. If the Mac/agent stops, an MQTT Last-Will greys the card out.

Features

• GPU & CPU utilization (bars) + power draw, unified memory, swap, GPU/CPU temps
• Ollama: up/down, version, each resident model + VRAM, installed-model count
• Hermes: up/down, configured model, CPU%/RSS
• Native MM look: standard module header, theme color variables, relative sizing so it scales with your font size and drops into any region
• i18n-ready (getTranslations), requiresVersion set, smooth non-flashing updates
• Bonus: built-in Home Assistant MQTT discovery — flip one config flag and every metric auto-registers as an HA entity under one device (loaded models exposed as attributes)

Requirements

• An MQTT broker reachable by both the Mac and the mirror (e.g. the Mosquitto add-on many of us already run for Home Assistant)
• macOS host with brew install macmon; Ollama on :11434

Install (module side)

cd ~/MagicMirror/modules
git clone https://github.com/coreycaverly/MMM-OllamaHostMonitor
cd MMM-OllamaHostMonitor && npm install
{
  module: "MMM-OllamaHostMonitor",
  position: "top_right",
  config: {
    mqttServer: "homeassistant.local",
    topicPrefix: "ollama-host/metrics",
    title: "Mac Studio"
  }
}
The Mac-side collector (setup, launchd service, config) is in the repo's agent/ folder with its own README.

Repo: https://github.com/coreycaverly/MMM-OllamaHostMonitor

Feedback welcome — happy to generalize beyond Macs if there's interest.

Hi everyone,

I wrote a small module that displays near-real-time Meteosat Third Generation (MTG) satellite imagery on MagicMirror².

The images are retrieved directly from the official EUMETView WMS service and automatically processed into a transparent full-disk image, so they can be placed nicely on any MagicMirror layout.

Screenshot

Features

• Near-real-time MTG satellite imagery
• Multiple official EUMETView products
• Automatic updates
• Transparent Earth disk for seamless integration
• Configurable image size and source-image resolution
• Optional source, product and timestamp caption

The module is available on GitHub:

https://github.com/FHFH2025/MMM-Meteosat

Installation, configuration and available products are described in the README.

This is my first MagicMirror² module, so there is certainly room for improvement. If you run into any issues or have suggestions, please let me know. Feedback, bug reports and pull requests are always appreciated.

Hello,

I want to announce a new module: MMM-Gamma601

This module adresses to all having a small bitcoin solo miner at home and want to display the actual values on magic mirror.

MMM-Gamma601 on Github

installed update using Sams update script.
MMM-Pinfo Not showing any information.
Did get pull and npm install
That did nothing.
IDEAS???

Hello Everyone,

Github: MMM-EnergyFlow

I built a module that shows your energy flow (Solar/Battery/Grid/House) as animated, glowing particles flowing between nodes in real time – cyberpunk/neon style. Works with any smart home system (Home Assistant, ioBroker, or anything that can send an HTTP request/MQTT message), not tied to one integration.

Setup guide, config options, and Home Assistant/ioBroker examples in the README. Feedback welcome!

Hi. This is very nice. Can you share please your module for Renault? The one you use for your Espace. I drive also a Renault and that will be usefull for me.

New module MMM-BracketEngine displays a mirrored knockout tournament bracket for any sport.

I took the MMM-FIFAWorldCup module and generalized it for any Bracket style Tournament. Providers fetch data from external APIs and normalize it into a common format; the engine renders it with a CSS Grid layout. You can also use a static bracket that you edit so you can display a tournament that has no online data (chess club, little league, etc.) . Providers for FIFA World Cup and Wimbledon are included.

Back when I built my bathroom mirror I bought it through a guy here, and now I’m about to build another one, and just wanted to find out, if there are still options available through users on the site?

Hi everyone,

I’ve tried a longer time ago without success - recently I gave it a second try and surprisingly it’s “working” right now: David Werth’s MMM-Bring.
It is a lovely little module and I want to be clear up front that all the original credit goes to him. The trouble is that it has not seen any maintenance in roughly six years (the original dates back to 2019), and my recent npm install started throwing security warnings at me.
Rather than let it bit-rot, I reworked it fairly thoroughly and published the result as a fork: https://github.com/rkorell/MMM-Bring.

I thought it might be useful to others here, so here is what changed and, more importantly, why.

1. The original has been unmaintained for ~6 years

The original module goes back to 2019 and has effectively been dormant since. That is not a criticism — it simply did its job and life moved on. But six years is a long time in Node land: it was written against an older dependency and rendering style, and nobody was around to react when its dependencies started aging out. If you install it today on a current MagicMirror / Node setup, you feel that age immediately (see the next point). My goal with the fork was not to reinvent it, but to bring it back to a state where it installs cleanly, runs on current Node, and can be maintained going forward.

2. The npm security issues — now zero runtime dependencies

This is what actually pushed me to act. Installing the original pulls in axios ^0.21.2 (released back in 2021) and data-store. On that axios line, npm audit reports two high-severity advisories — credential leakage across an HTTP-to-HTTPS redirect, and a prototype-pollution issue — plus a transitive follow-redirects advisory. For a module that authenticates with your Bring! account, shipping a known-vulnerable HTTP client is not great.

Instead of merely bumping versions, I removed both dependencies entirely. The fork now has zero runtime dependencies. All HTTP goes through Node’s built-in fetch (Node 18+), and the auth-token cache is a tiny fs-based JSON file that replaces data-store. The upshot: npm audit is clean, there is nothing to compile, and there is no npm install step at all anymore — you just clone it. Fewer moving parts, no native build, and nothing that can rot silently in the background.

3. The headline feature: app-identical category sorting

This is the part I am most happy with. The original shows the list in whatever raw order the API returns. The Bring! app, however, groups items into categories (Fruits & Vegetables, Milk & Cheese, Meat & Fish, …) and sorts those categories in an order you can customise per list. I worked out how the app reconstructs that and reproduced it faithfully.

There is a new option, useSections, with three modes:

• "off" — the classic flat list in raw API order (the old behaviour).
• "on" (the default) — items sorted into your list’s category order as one continuous list, without visible headers. Same layout footprint as before, just in the right order.
• "show" — the same sorting, plus a text header per category, exactly like the app.

The grouping is genuinely app-identical rather than a guess: it follows your list’s own saved section order (listSectionOrder), honours the sections you have hidden, and shows the localized category names and item names for your list’s language. Items you typed that are not in Bring!'s catalog land in an “own items” section — and even that fallback label is localized (13 language files covering all 20 Bring! locales). Under the hood the canonical item id is kept separate from the translated display name, so marking things bought and adding items keeps working regardless of language. There are screenshots of all three modes in the README if you want to see the difference.

Other improvements worth mentioning

• Backend-driven polling with a cached last-good state. The node helper owns the refresh cycle, so a browser reload shows data instantly and a transient network blip never blanks the list.
• Modern auth. The access token is refreshed via its refresh token, with a full password re-login only as a fallback.
• showCount. An optional count in the title line when the list is longer than maxItems, so you can see there is more than what is shown.
• Font licensing tidied up. The bundled paid “Museo Sans 300” weight was removed; the free 500 weight stays with proper exljbris attribution, and the spec label falls back to the MagicMirror default font.
• Touch support retained. You can still mark items bought and add items via MMM-Keyboard.

Install

cd ~/MagicMirror/modules
git clone https://github.com/rkorell/MMM-Bring.git

That is it — no npm install. Then add the module block to your config.js (there is a full options table in the README). If you already run the original module, you can simply replace the folder; your config.js entry stays the same. Step-by-step migration notes are in the README.

Credits and the usual caveat

All credit for the original module goes to David Werth (https://github.com/werthdavid/MMM-Bring). The API-interaction design was inspired by miaucl/bring-api (https://github.com/miaucl/bring-api), the well-maintained Python client, as a reference for a current, state-of-the-art Bring! implementation.

Standard caveat: Bring! offers no official public API, so this — like every Bring! integration — talks to the same private endpoints the app uses. They could change at any time. It has been stable for years, but be aware of that.

Repo, README and changelog: https://github.com/rkorell/MMM-Bring. Feedback, issues and pull requests are very welcome.

Hope you will find it useful.
Warmest regards,
Ralf

Hi everyone! After many evenings of tinkering I’d like to share our family’s MagicMirror² build. It hangs in the hallway and has become the central info hub for a family of five – calendars, school timetables, shopping lists, news, music, and a few experiments with AI. Everything is touch-operated.

Hardware

• Raspberry Pi 5 in a passive Flirc case, booting from USB
• Samsung DB22D – 22" Smart Signage LED display, mounted horizontally
• Connected via HDMI (video) and USB (touch)
• IKEA SYMFONISK bookshelf speaker (Sonos) mounted below the screen, sitting on the SYMFONISK shelf with built-in wireless phone charging – so the mirror doubles as a charging station
• S3KM1110 mmWave radar sensor for presence detection (much more reliable than PIR – it detects you even when you stand still)

Software overview

• MagicMirror² on Raspberry Pi OS Bookworm
• 19 pages, navigated by swipe gestures (MMM-Touch + MMM-pages + MMM-page-indicator with custom FontAwesome icons per page)
• MMM-ModuleScheduler switches between day and night layout automatically
• MMM-Remote-Control for administration and as an API for my presence script

The pages

Family calendar

MMM-CalendarExt3 in week view, merging iCloud family calendars, school holidays, both kids’ football clubs’ match schedules (auto-imported from the association’s ICS feeds), Juventus fixtures and the F1 calendar – color-coded per source.

School timetables (3 pages)

One page per child, rendered with MMM-CalendarExt3Journal as a proper weekly timetable grid. The data comes straight from the schools’ ICS exports, so it updates itself – no manual maintenance. The kids check their own page in the morning.

Shopping list with recipe integration

MMM-Bring shows our Bring! lists with full touch support – tap to add items (on-screen keyboard), tap to check them off. We use multiple lists; one of them is fed by Tandoor Recipes (self-hosted on a Synology NAS): when I add a recipe’s ingredients to the shopping list in Tandoor, they appear on the mirror. Meal plan and recipe of the day come from a small self-written MMM-Tandoor module.

News ticker with AI comic generation

This is my favorite gimmick. A self-written module (MMM-NewsComicFeed) shows rotating headlines from Swiss news sources at the top, plus Juventus/F1 feeds at the bottom. Tapping a headline sends it through the Claude API, which writes a comic scenario in one of 15 styles; an image model renders it, and the result is posted to Mastodon and shown on the mirror. Instant satire from the morning news.

Claude assistant page

A self-written chat module with an inline DE/CH keyboard, Markdown rendering and optional web search – the family can ask anything directly on the mirror. The comic generation can be triggered from here as well.

More pages

Weather (OpenWeather one-call), Pi-hole statistics, live football scores, F1 dashboard, a math clock (AlbertClock), a German word clock, YouTube playlists, Sonos control, Mastodon timeline, Home Assistant sensors (dishwasher status and even the car’s fuel level on the main page), and a thermal dashboard (see below).

Presence detection & power management

A Python script reads the mmWave sensor via GPIO and controls the display: DPMS + HDMI-CEC off after 1h without presence during the day, 15 min at night. When the screen turns off, the script also calls the MMM-Remote-Control API to switch the mirror to an empty hidden page.

Why that last step matters: I rewrote MMM-Webview so that embedded web pages unload their Electron renderer process when hidden and reload when shown. Combined with the presence script, all heavy web content dies as soon as nobody is around – a big win for RAM, CPU and temperature on a passively cooled Pi.

Heat management (passive case, no fan)

With several Electron webviews the Pi used to sit at 55–75 °C. To understand what was going on I built MMM-ThermalWatch: current temperature/clock/load, a 24h/7-day max-temperature bar chart (touch to switch views, tap a bar for details), throttle-flag decoding, and a peak log that captures which processes were actually busy whenever a temperature threshold is crossed – measured as instantaneous CPU from /proc snapshots, with proper labels for Electron child processes.

The verdict: the peaks were exactly the parallel webview renderers. Since the suspend/resume rewrite and the presence integration, evenings run noticeably cooler – all of it without a fan.

[SCREENSHOT: ThermalWatch page]

Complete module list

Navigation, layout & system

• MMM-pages – 19 pages plus hidden pages (screensaver, admin)
• MMM-Touch – swipe gestures for page navigation
• MMM-page-indicator – with custom FontAwesome icons per page via CSS
• MMM-TouchButton – shutdown / reboot / stop buttons on the mirror
• MMM-ModuleScheduler – automatic day/night layout switching
• MMM-Remote-Control (+ MMM-Remote-Control-Repository) – admin UI and REST API (also used by my presence script)
• MMM-Keyboard – on-screen keyboard, used by Bring!
• alert, updatenotification – MagicMirror core

Always visible

• MMM-FlipClock – flip-style clock
• MMM-DateOnly – date display
• MMM-Sonos – now-playing cards for all Sonos groups (mini mode, album-art colors, progress and source icons)

Calendars & family

• MMM-CalendarExt3 – merged family week view
• MMM-CalendarExt3Journal – 3× weekly timetable grid (one per child)
• calendar (core module) – ICS feed provider for all of the above: iCloud family calendars, exam calendar, school holidays, two football club match calendars, Juventus fixtures, F1 calendar, and both schools’ timetable exports
• MMM-homeassistant-sensors – 2× on the main page: dishwasher status (elapsed/remaining time, salt, rinse aid) and the car’s fuel level + mileage from Home Assistant

Content pages

• MMM-OpenWeatherForecast – current conditions, hourly and daily forecast
• MMM-pihole-stats – Pi-hole DNS statistics
• MMM-Webview – 5× (own rewrite, see below): Home Assistant dashboard, football live scores, betting-pool rankings, F1 dashboard, Sonos web app
• MMM-HTMLSnippet – AlbertClock (math clock, hosted locally on the Pi-hole)
• MMM-germanwordclock – word clock
• MMM-RemoteYoutube – YouTube playlists with time-based switching
• MMM-Mastodon – Mastodon timeline (shows the generated comics, among other things)
• MMM-Bring – Bring! shopping lists with touch add/check-off
• MMM-Tandoor – meal plan / recipe of the day (self-written)
• MMM-NewsComicFeed – 2× news ticker, top (Swiss news) and bottom (Juventus + F1), with tap-to-comic (self-written)
• MMM-ComicButton – comic generation pipeline (self-written)
• MMM-Claude – AI assistant page (self-written)
• MMM-ThermalWatch – thermal dashboard (self-written)

Self-written modules in this build

• MMM-NewsComicFeed – RSS ticker with tap-to-comic function
• MMM-ComicButton – Claude → image model → Mastodon pipeline, 15 comic styles
• MMM-Claude – chat assistant with on-screen keyboard and web search
• MMM-Tandoor – meal plan / recipe display from a self-hosted Tandoor instance
• MMM-Webview (rewrite) – webview embedding with suspend/resume of hidden pages
• MMM-ThermalWatch – thermal dashboard with process-level peak diagnosis

MMM-PWSWeather is a module that displays real-time weather data from your Personal Weather Station at Weather Underground.
The provider can be used by the default weather module and other weather modules that support the weatherProvider configuration option.

Hello,

I would like to increase the text size for the Description text in the default NewsFeed module. I have checked the newsfeed.css file but there doesn’t seem to be a section for the Description text that I can add to my custom.css file to modify.

Regards,

Tom

Hi @sdetweil Howzit Sam? I upgraded using the upgrade script this weekend on my Mirror. However, I ran into an issue. The script installed Node 22.21.1 but MM requires 22.22.2. Not sure if this is just an oversight? I also noticed that it installed an earlier version of npm that is also not supported.

I checked the install log and there is not much going on in there.

I had to manually install node 22.22.2 and npm v11 before it worked.

Just thought I would give you the heads-up.

Besides the issue with the install, the upgrade is the second one that crashed my MicroSD. The one in April and now this one as well. I suspect something might be doing this. My SD card could not have gone within 4 month. But hey, i might be wrong.

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.22.2 <23 || >=24 (no change to previous release) (update July 6)

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!