Re: MMM-Carousel - how to configure a module multiple times on the SAME page?

I looked through that thread but it doesn’t quite help with my issue.
I’m using scenes 2 on my calendars to rotate between the various family calendars.

In the top_left in trying to display weather info that rotates separately and aren’t part of the scenes . I’m trying to do that with carousel. It works great with 3 modules all different. The moment I had another instance of weather into the mix the last module no longer shows. I just get a blank area when it should show that module .

Any pointers on where to look?

I used to get a weekly summary in the mail every sunday.
Has something changed, because this is sudenly stopped.

Hi guys . Any new module looking good and fresh? I need something that slides the pages like smartphone.
Mmm-carousel looks good but is rather for keybindings.

Hi All

Since the update to version 4 of RTSPStream, I can no longer get my IP Camera to show on the screen. I have attempted a reinstall, and checked the settings. Just the outline of the module, with the heading, but no image. The best I have had was a still image in the centre of the screen which vanished shortly after.

AFAIK my camera has had no firmware or software updates.

Does the hive mid have any suggestions?

Many thanks

Bambulink Module for MagicMirror

Module: MMM-Bambulink

This MagicMirror module,

MMM-Bambulink is a third-party module for MagicMirror² designed to display information about your Bambu Lab printer directly on your MagicMirror screen. The module connects to your printer over the local network using Bambu Lab’s LAN credentials and updates information automatically at a configurable interval.

Important: ONLY LAN mode NOT must be enabled on the printer.

Requirements

To use this module, you need the following information:

• The IP address of your Bambu Lab printer
• The printer’s LAN Access Code
• The printer serial number

These three values are required in the configuration to establish the connection with your printer. MagicMirror² documentation recommends clearly listing required external dependencies and setup information in a module README.

Key Features

• Monitor your Bambu Lab printer directly from MagicMirror².
• Secure local connection using MQTT/TLS on port 8883.
• Configurable refresh interval for automatic updates.
• Custom printer title using the printerModel option.
• Two temperature display modes:
  • tile view (tiles)
  • graph view (graph)
• Visual AMS display including:
  • AMS temperature,
  • filament color,
  • loaded filament type for each slot.
• Automatic highlight of the active AMS slot during printing, including when the printer switches filament. Bambu’s AMS workflow is built around slot-based filament selection and color mapping, which makes this type of visual highlighting consistent with how AMS data is handled in local workflows.
• Simple installation inside the standard MagicMirror² module structure.

Development Status

The module is functional and ready to use in a standard MagicMirror² environment. Installation, Node.js dependencies, configuration, and update steps follow the usual module workflow inside ~/MagicMirror/modules, which is the standard location for third-party MagicMirror² modules.

The project is still evolving, especially in terms of UI improvements, advanced display options, and visual customization.

Compatibility

MMM-Bambulink is designed for MagicMirror² and Bambu Lab printers with LAN mode enabled.

The required parameters such as ip, accessCode, serial, mqttPort, and useTLS indicate that the module is intended to communicate with the printer locally through a secure network connection.

Installation

Go to your MagicMirror modules directory:

cd ~/MagicMirror/modules

Clone the repository:

git clone https://github.com/TAGinside/MMM-Bambulink

Enter the module directory:

cd MMM-Bambulink

Install the Node.js dependencies:

npm install

MagicMirror’s module guides recommend keeping installation steps simple and directly copyable from the README.

Configuration

Add the module to the modules array in your config/config.js file:

modules: [
  {
    module: "MMM-Bambulink",
    position: "top_left",
    config: {
      ip: "192.168.1.x",                // Printer IP address
      accessCode: "xxxxxxxx",           // LAN Access Code
      serial: "XXXXXXXX",               // Printer serial number
      updateInterval: 5000,             // Refresh interval in ms

      printerModel: "H2S",              // Displayed printer name or model
      temperatureDisplayMode: "tiles",  // "tiles" or "graph"

      display: {
        scale: 1,
        width: 320,
        graphMinutes: 1
      },

      temperatureColors: {
        nozzle: "#ff4d4f",              // Red
        bed: "#ff9f1a",                 // Orange
        chamber: "#4da3ff"              // Blue
      }
    }
  }
]

MagicMirror² modules are configured through config/config.js, where each module is added to the modules array with its own config object. [web:134][web:267]

How to Use

After adding the module to config/config.js, restart MagicMirror².

Once running, the module will display your Bambu Lab printer information in the selected MagicMirror position, such as top_left, using the temperature display mode you configured.

Update

To update the module:

cd ~/MagicMirror/modules/MMM-Bambulink
git pull
npm ci

Then restart MagicMirror².

Use Cases

MMM-Bambulink is especially useful in:

• a workshop,
• a technical office,
• a home lab,
• a smart home dashboard centered around MagicMirror².

It allows you to quickly monitor an active print, confirm that the printer is responding, and keep a live visual overview of the current job without constantly opening Bambu Studio.

About

MMM-Bambulink brings Bambu Lab printer monitoring directly into MagicMirror², making it possible to integrate 3D printing status into a broader smart home, workshop, or technical dashboard.

The module is open source and free to use and modify. For more information, updates, or contributions, visit the GitHub repository:

https://github.com/TAGinside/MMM-Bambulink

Feedback is always welcome, especially for printer compatibility, AMS behavior, and display improvements.

Trying to upgrade my RPI5 v2.33 to V2.36 and get the following error while doing the “docker compose Pull”:

ron@rpi5:~/magicmirror/run $ docker compose pull
[+] Pulling 16/18
 ✔ init Skipped - Image is already being pulled by magicmirror             0.0s 
 ⠏ magicmirror [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 386.2MB / 390.3MB Pulling               23.9s 
   ⠏ 76b7b92b680d Extracting         181kB/181kB                          22.9s 
   ✔ 0479d40f39a3 Download complete                                        2.4s 
   ✔ 2d0f308d8afe Download complete                                        0.4s 
   ✔ 06d4fbe68d7c Download complete                                        5.6s 
   ✔ 245238857a72 Download complete                                        5.7s 
   ✔ 50618a6ac35d Download complete                                        7.2s 
   ✔ d0d0bce19890 Download complete                                       10.8s 
   ✔ d0326d1e8758 Download complete                                       10.8s 
   ✔ 22ef58b941aa Download complete                                       10.8s 
   ✔ 3cbe9d4d3f1b Download complete                                       11.1s 
   ✔ 8ce16659ba64 Download complete                                       11.1s 
   ✔ bd6473435aa5 Download complete                                       11.1s 
   ✔ 153a60e41e92 Download complete                                       19.2s 
   ✔ 4ac394d170cb Download complete                                       11.3s 
   ✔ 7c3a6344e52e Download complete                                       22.9s 
   ✔ 4f4fb700ef54 Download complete                                       16.7s 
failed to register layer: Error processing tar file(exit status 1): archive/tar: invalid tar header

Tried it twice with the same error
system info:
RPI 5, 4GB ram, 128GB SSD, RPI OS Bookworm

I ran the update script a few days ago after seeing PM2 error messages about the MMM-Jast module requiring Node 22.0.0. I saw posts about issues with node on the Pi 0, but didn’t see a workaround, or at least didn’t understand a workaround.

My current branch is Master
I tried “git checkout -b oldbranch tags/v2.30”

If Pi Zero2w is no longer viable, would a 3B+ work?

Hi,

I’d appreciate help with resolving this issue:

Thank you!

A JavaScript error occurred in the main process
Uncaught Exception:
TypeError: styleText is not a function
    at /home/pi/MagicMirror/js/logger.js:40:42
    at Object.<anonymous> (/home/pi/MagicMirror/js/logger.js:114:2)
    at Module._compile (node:internal/modules/cjs/loader:1141:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1196:10)
    at Module.load (node:internal/modules/cjs/loader:1011:32)
    at Module._load (node:internal/modules/cjs/loader:846:12)
    at f._load (node:electron/js2c/asar_bundle:2:13330)
    at Module.require (node:internal/modules/cjs/loader:1035:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/home/pi/MagicMirror/js/app.js:7:13)

This sort of thing isn’t my strong suit so please be patient! Any help would be greatly appreciated!!!

MonthlyCalendar isn’t showing events more than 5-6 days in advance, and no past events. I created this MM with a RaspPi 3b+ less than 3 months ago.

 {
    module: "MMM-MonthlyCalendar",
    position: "lower_third",
        
    config: {
	mode: "fourWeeks",
	maximumNumberOfDays: 365,
	wrapEvents: true,
	fetchInterval: 900000,
	maximumEntries: '10000',
	broadcastPastEvents: true,
	coloredText: true,
	coloredBorder: false,
	coloredBackground: false,
      calendars: [
        {
			url: 'https://calendar.google.com/calendar/ical/be2031826a7855c5e317a2ea6ae3ade05aed2e9bd58f7d5cd3849d56215c6be6%40group.calendar.google.com/public/basic.ics',
			color: '#ffa500'
					
		},
		{
			url: 'https://calendar.google.com/calendar/ical/47b238f74068084be290b71f9e9e05746149408c3b0473c712a06ea00b686643%40group.calendar.google.com/public/basic.ics',
			color: '#cf1e26'
			
		},
			{
			url: 'https://calendar.google.com/calendar/ical/9sqcibn7flt9tup1ebb4378a1k%40group.calendar.google.com/public/basic.ics',
			color: '#7a263a'
			
		},
		{
			url: 'https://calendar.google.com/calendar/ical/up10glq48b1ufoni5hgm47sc04%40group.calendar.google.com/public/basic.ics',
			color: '#132257'
			
		},
			{
			url: 'https://calendar.google.com/calendar/ical/up10glq48b1ufoni5hgm47sc04%40group.calendar.google.com/public/basic.ics',
			color: '#034694'
			
		},
		{
			url:  redacted
			color: '#c33332'
			
		},
			{
			url:  redacted
			color: '#8a00c2'
			
		},
		{
			url:  redacted
			color: '#3b8132'
			
		},
			{
			url:  redacted
			color: '#CC5500'
			
		},
			{
			url:  redacted
			color: '#fee12b'
			
		},
		{
			url:  redacted
			color: '#818380'
			
		},
		{
			url: 'https://calendar.google.com/calendar/ical/v3134htvj13o064cjb7tb6m59q9a9ls1%40import.calendar.google.com/public/basic.ics',
			color: '#ffffff'
			
		},
		{
			url: 'http://ics.sync2cal.com/categories/get_ics/8205354e-0333-4e82-a1e3-c64595e2b6ac.ics',
			color: '#e6ff00'
			
		},
                     
           ],
    }
      
    },
  
		{
		module: "MMM-CalendarWeek",
		position: "top_bar",	// This can be any of the regions. Best results in bottom region.
		config: {
		  maximumNumberOfDays: 6,
		  maximumEntries: 200,
		  allowDuplicate: false,
		  wrapEvents: true,
		  colored: true,
		  coloredSymbolOnly: true,
		      calendars: [
			{
			url: 'https://calendar.google.com/calendar/ical/be2031826a7855c5e317a2ea6ae3ade05aed2e9bd58f7d5cd3849d56215c6be6%40group.calendar.google.com/public/basic.ics',
			symbol: 'fa-light fa-futbol',
			color: '#ffa500',
					
		},
		{
			url: 'https://calendar.google.com/calendar/ical/47b238f74068084be290b71f9e9e05746149408c3b0473c712a06ea00b686643%40group.calendar.google.com/public/basic.ics',
			symbol: 'fa-light fa-futbol',
			color: '#cf1e26'
			
		},
			{
			url: 'https://calendar.google.com/calendar/ical/9sqcibn7flt9tup1ebb4378a1k%40group.calendar.google.com/public/basic.ics',
			symbol: 'fa-ight fa-futbol',
			color: '#7a263a'
			
		},
		{
			url: 'https://calendar.google.com/calendar/ical/up10glq48b1ufoni5hgm47sc04%40group.calendar.google.com/public/basic.ics',
			symbol: 'fa-light fa-futbol',
			color: '#132257'
			
		},
			{
			url: 'https://calendar.google.com/calendar/ical/up10glq48b1ufoni5hgm47sc04%40group.calendar.google.com/public/basic.ics',
			symbol: 'fa-light fa-futbol',
			color: '#034694'
			
		},
		{
			url: redacted
			symbol: 'fa-solid fa-bolt-lightning',
			color: '#c33332'
			
		},
			{
			url:  redacted
			symbol: 'fa-solid fa-cat',
			color: '#8a00c2'
			
		},
		{
			url:  redacted
			symbol: 'fa-solid fa-frog',
			color: '#3b8132'
			
		},
			{
			url:  redacted
			symbol: 'fa-solid fa-jedi',
			color: '#CC5500'
			
		},
			{
			url:  redacted
			symbol: 'fa-solid fa-people-group',
			color: '#fee12b'
			
		},
		{
			url:  redacted
			symbol: 'fa-light fa-calendar',
			color: '#818380'
			
		},
		{
			url: 'https://calendar.google.com/calendar/ical/v3134htvj13o064cjb7tb6m59q9a9ls1%40import.calendar.google.com/public/basic.ics',
			symbol: 'fa-light fa-baseball',
			color: '#ffffff'
			
		},
		{
			url: 'http://ics.sync2cal.com/categories/get_ics/8205354e-0333-4e82-a1e3-c64595e2b6ac.ics',
			symbol: 'fa-solid fa-trophy',
			color: '#e6ff00'
			
		},
		
		],

I just applied the April update, during which I spotted this message:

npm notice
npm notice New major version of npm available! 10.9.4 -> 11.14.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.14.0
npm notice To update run: npm install -g npm@11.14.0
npm notice

Should I run this update, or leave npm as it is?
Thanks!

MMM-Charms is a MagicMirror² module for displaying rotating affirmations, reminders, reflective prompts, and curated quote/dialogue packs from multiple named sets.

It supports local JSON packs, simple text sets, manual switching between packs, tap/click cycling, and optional time-based pack switching.

Current packs include:

• General
• Calm
• Confidence
• Family
• Gentle Reminders
• Hard Days
• Grounding
• Quotes
• Bollywood
• Video Game Quotes

The idea behind MMM-Charms came with a desire to add quotes from Bollywood movies and video games :) . It then became an attempt to make the mirror feel a little more reflective and customizable. It can now be used for personal affirmations, family-oriented prompts, calmer household messaging, themed quote packs, reminders for timed chores or fun pop-culture rotations. I am curious to find out what packs users might come up with. It is rightly placed under ‘Entertainment’ on this forum. Please remember this is not a substitute for professional mental health, medical, therapeutic, or crisis support.

Screenshots:

Download:

[card:testingonlypi/MMM-Charms]

The readme file clearly states the use of AI to create this module. I am not and will never be a coder of any standard, and would never seek to replace those who are more experienced, committed and better at this… same as I can take photos, but may not be a professional photographer.

Version 0.1.0

• First public release
• Added support for multiple named packs
• Added manual switching between packs
• Added optional tap/click cycling
• Added optional time-based pack switching
• Added JSON pack support
• Included curated packs for General, Calm, Confidence, Family, Gentle Reminders, Hard Days, Grounding, Quotes, Bollywood, and Video Game Quotes

Hi

After a recent reboot (to update MMM-CalendarExt3Agenda and add some more dates to MMM-MyGarbage) I’ve noticed that the clock and agenda modules have reverted to UTC (should be BST right now).

A quick look shows the docker container is now running with UTC (although the RPi is correctly on BST):

magicm@magicmirror:~ $ date
Sun  3 May 09:02:24 BST 2026
magicm@magicmirror:~ $ docker exec -it mm bash
node@magicmirror:/opt/magic_mirror$ date
Sun May  3 08:02:36 AM UTC 2026

I’ve not set the timezone (or date format) explicitly for the Docker before. Has a new release of Docker changed that and, if so, how do I pass that setting through?

Many thanks

Steve

Hi everyone!

I wanted to share something that came from my own frustration developing MagicMirror modules.

For years, testing a module meant either setting up a full MagicMirror installation (overkill for just iterating on one module), or developing blind and hoping it works when you finally deploy.

I built MagicMirror Module Sandbox to change that. It’s a lightweight dev tool that spins up a local testing environment for your module in seconds — no full MagicMirror install, no Docker, just your module and a browser window.

What you get:

• 🚀 Zero setup — Run npx @angeldeejay/magicmirror-module-sandbox from inside your module folder and you’re done
• ⚡ Live reload — Changes to your config or module files reload instantly
• 🎛️ Visual config editor — Edit your module’s config through a browser UI instead of hand-editing JSON
• 🔄 Full MagicMirror lifecycle — Simulates start(), notificationReceived(), updateDom(), and all real lifecycle hooks
• 🔌 Real node_helper.js support — Socket.io communication works exactly like production
• 🐛 Debug panel — Inspect both helper logs (server-side) and browser console in one place
• 📡 Notifications inspector — Send frontend notifications, monitor socket traffic in real time
• ✅ Module quality check — Quick analysis against MagicMirror’s third-party module standards

How to use it:

One-off test (no install needed)

npx @angeldeejay/magicmirror-module-sandbox

Then open http://localhost:3010 and start hacking.

Works great for:

• Rapid iteration while developing
• Validating config changes before deploying to your Pi
• Testing in CI pipelines (Playwright integration test support included)
• Debugging why a module behaves differently on the actual MagicMirror

GitHub: https://github.com/angeldeejay/magicmirror-module-sandbox
npm: https://www.npmjs.com/package/@angeldeejay/magicmirror-module-sandbox

This is v1.1.0, tested across real third-party modules. Stable and ready to use.

If you’re a module developer, I’d love to hear what you think — open issues if something doesn’t behave as expected, or let me know what you’d like to see next.

Hello,
As a dedicated user of Magic Mirror I am frequently searching for a module for my car, a hybrid Toyota Yaris 2025.
I can check my car from inside my house, but a MMM-MyToyota module would be very helpful.
I don’t have the skills to build such a module, but maybe there is somebody in this forum who is able to do so.

Thanks

Pim

Description:

A MagicMirror² module that displays your photos as a stack of overlapping, slightly-rotated polaroid-style cards. At a configurable interval a new photo flies in from off-screen and lands on top of the stack, while the oldest card drops off the back once the stack has grown beyond its configured size.

Screenshots:

Download:

[card:skarabaeus/MMM-PhotoStack]

Version 1

Initial Version

uhm hi, its been awhile since i updated my MM.

i ran sdetweil upgrade script and these were being upgrade.

doing test run = false
Node currently installed. Checking version number.
Minimum Node version: v22.21.1
Installed Node version: v20.9.0
installing correct version of node and npm, please wait
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v22.21.1
Installed Node version: v22.21.1
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V10.9.4
Installed npm version: V10.9.4
No npm upgrade necessary.

saving custom.css

upgrading from version 2.28.0 to 2.36.0
fetching latest revisions
updating MagicMirror runtime, please wait

> magicmirror@2.36.0 postinstall
> git clean -df fonts vendor modules/default


> magicmirror@2.36.0 prepare
> [ -f node_modules/.bin/husky ] && husky || echo no husky installed.

no husky installed.

i then tried to pm2 start and ran into this error. Ok not exactly error, but the mirror just keep going to blackscreen and nothing then back to wall paper then blackscreen and keep looping this.

(node:1971942) [DEP0044] DeprecationWarning: The `util.isArray` API is deprecated. Please use `Array.isArray()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

then i ran npm start and get the punycode error

[ERROR] [unknown] (node:1970698) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `electron --trace-deprecation ...` to show where the warning was created)
[1970698:0501/224750.044913:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
[1970698:0501/224750.044978:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:281] Failed to initialize Wayland platform
[1970698:0501/224750.044995:ERROR:ui/aura/env.cc:246] The platform failed to initialize.  Exiting.
/home/hsa/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

i then read in another thread to do npm run start:x11
this works but the punycode still appear but mirror runs.

feels like theres multiple item for me to fix and im kinda lost.

can some kind soul help me out?

Release Notes

Thanks to: @cgillinger, @khassel, @KristjanESPERANTO, @sonnyb9

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

Compare to previous Release v2.35.0

This release falls outside the quarterly schedule. We opted for an early release due to:

• Security fix for the internal cors proxy
• API change of the weather provider smi
• Several bug fixes

Breaking Changes

The cors proxy is now disabled by default. If required, it must be explicitly enabled in the config.js file. See the documentation.

⚠️ Security

You can find several publicly accessible MagicMirror² instances.

This should never be done. Doing so makes your entire configuration, including secrets and API keys, publicly visible. Furthermore, it allows attackers to target the host; this is only prevented beginning with this release.

Public MagicMirror² instances should always run behind a reverse proxy with authentication.

[core]

• Prepare Release 2.36.0 (#4126)
• Allow HTTPFetcher to pass through 304 responses (#4120)
• fix(http-fetcher): fall back to reloadInterval after retries exhausted (#4113)
• config endpoint must handle functions in module configs (#4106)
• fix replaceSecretPlaceholder (#4104)
• restrict replaceSecretPlaceholder to cors with allowWhitelist (#4102)
• fix: prevent crash when config is undefined in socket handler (#4096)
• fix cors function for alpine linux (#4091)
• fix(cors): prevent SSRF via DNS rebinding (#4090)
• add option to disable or restrict cors endpoint (#4087)
• fix: prevent SSRF via /cors endpoint by blocking private/reserved IPs (#4084)
• chore: add permissions section to enforce pull-request rules workflow (#4079)
• update version for develop

[dependencies]

• update dependencies (#4124)
• chore: update dependencies (#4088)
• refactor: enable ESLint rule “no-unused-vars” and handle related issues (#4080)

[modules/newsfeed]

• fix(newsfeed): prevent duplicate parse error callback when using pipeline (#4083)

[modules/updatenotification]

• fix(updatenotification): harden git command execution + simplify checkUpdates (#4115)
• fix(tests): correct import path for git_helper module in updatenotification tests (#4078)

[modules/weather]

• fix(weather): use nearest openmeteo hourly data (#4123)
• fix(weather): avoid loading state after reconnect (#4121)
• weather: fix UV index display and add WeatherFlow precipitation (#4108)
• fix(weather): restore OpenWeatherMap v2.5 support (#4101)
• fix(weather): use stable instanceId to prevent duplicate fetchers (#4092)
• SMHI: migrate to SNOW1gv1 API (replace deprecated PMP3gv2) (#4082)

[testing]

• ci(actions): set explicit token permissions (#4114)
• fix(http_fetcher): use undici.fetch when dispatcher is present (#4097)
• ci(codeql): also scan develop branch on push and PR (#4086)
• refactor: replace implicit global config with explicit global.config (#4085)

Hi Guys
As a young lad I was an avid traveler and hitched hiked from John O Groats to Lands End at the age of 14 and I have had the travel bug ever since . My children and grandkids have also got the travel bug - my youngest granddaughter is about to embark on a round the world trip with her parents and younger brother. She has already visited 9 countries so far – not bad for a 2 year old.

So I decided to try and make a module that would be helpful to them on their travels and allow me and the wife to share in their adventures from afar.

Where to start – well there was only one place , the innovative MMM-iHaveBeen there by Sebastian Merke. This is the module that first got me hooked on Magic Mirror, and it got me thinking how could I modify it to fit with my four loves, family, flying, football and travel.

After lots of trial and many errors and frequent help from AI assistance I would now like to introduce the result - MMM-iAmGoingThere , a MagicMirror² module designed for travelers and flight enthusiasts to track their current live trips and visualize their past travel history and future planed trips.

https://github.com/gitgitaway/MMM-iAmGoingThere

Core Features:
Live Flight Tracking: Real-time updates via FlightAware AeroAPI, showing live flight paths, and estimated arrival times (ETA).
Dynamic Scenarios: Supports 6 distinct travel modes, including round trips, multi-leg “Round the World” journeys, multi-origin traveler tracking, and a dedicated Football Away Days mode.
Interactive Travel Visualization:
Great-Circle Paths: Smooth, color-coded arcs showing exactly where you’ve been and where you’re going.
Interactive Globe: Auto-rotates to keep active planes in focus on 3D projections.
Manual Mapping: Right-click any country to mark it as “visited” with persistent saving to a local cache.
Travel Companion Tools:
City Guides: Integrated Top 10 attraction lists that automatically update based on your active destination or marker clicks & links to airport terminal maps
Live Weather: Real-time destination weather updates via Open-Meteo.
Countdown Timers: Precision tracking for your next departure.

Currently, my CalendarExt3 module is only applying color to events that are within 48 hours. None of the events on the calendar past 48 hours have any coloring applied to them. I took a read through the pinned CSS guide but I’m not sure how to hunt down the sheet / items I need to change to implement this. I didn’t see anything obvious in the readme to edit this either.

Here is what my calendar looks like right now - only Sams Birthday which is today has color applied

And here is an example from Google where all of the events for the month have color applied to them:

Hello again guys,

In the rather small company I work, we do have this somewhat old school ( but maybe still a lot used in companies? ) calendar to mark peoples vacations, days of sickness, or some other reasons not to be at work with colored paper snippets ^^

So we plan to replace this board with a screen and obviously with a digitized version of it, where everyone related has access to the backend and can enter stuff.
First Ive been thinking of an online sheet like Googles or Excel online, but I had the thought, that there might be a way with a MM module?
Wed also like to use a different part of the screen to display some daily tasks for example, that would be also nice to set up with MM.

Does anybody know of such a calendar like our current analogue version?
Thanks a lot and regards from Germany