@meikelrix I’ll take a look asap :-)

@Mati_93 This sort of thing happens to others from time to time as well. It would be really interesting to know how you came across the old version 🕵️. We have the module list, which refers to the fork from shabatm since a while. Did you come across the old version in the forum?

@sdetweil said in MMM-Remote-Control:

So it requires sudo to make the change, …

This can also be seen as a disadvantage 🙂

@S374n said in MMM-Remote-Control:

First update changes my main.css - took me a while to figure it out and redo all my customizations.

You should not change main.css. All customizations should be made in custom.css: https://docs.magicmirror.builders/modules/customcss.html#custom-css

Thanks for the feedback!

Since Sam has already addressed some of the issues, I won’t go into them again.

A few problems were mentioned, some of which I have just addressed with v4.1.0. E.g.:

• Restart/Shutdown: Should now also work on systems without PM2.
• Minimize: Now says “restart to restore” so you know how to undo it.

---

About the monitor control issue:

This would be tricky to get running by default everywhere because every system uses different commands (X11/Wayland/etc). You have to check the Monitor Control docs and configure the right commands for your specific setup - the defaults won’t work everywhere.

---

About the “npm install/npm ci” topic:

Yes, npm ci can be problematic for modules with native dependencies that need platform-specific builds. However, MMM-Remote-Control only uses pure JavaScript dependencies (marked, qrcode, simple-git, swagger-ui-dist, uuid) - no native modules that require compilation.

For this module, npm ci is actually the better choice because:

• Guarantees exact tested versions which the developers released
• Faster installation (no dependency resolution)
• Same behavior in CI and production
• No change on the package-lock.json

So the warning about npm ci is valid in general, but doesn’t apply here.

---

About the microupdates. Since the test suite does not a lot parts yet, some details simply go unnoticed after major changes. If you are not experiencing any problems with the module, you do not need to install every update.

---

About node update: I recommend using nvm for node updates. This is also what is offered as default for Linux on the official download page. This makes many things easier - like if something does not work after an update, you can easily switch back to the previous node version. So you don’t need to be so afraid of updates.

@rkorell said in MMM-Remote-Control:

Node.js v20.18.1

@rkorell Thanks for the feedback and the good error description! I’ll optimize the error logging, but unfortunately you have to update to at least node 22. I recommend version 24.

For the current MagicMirror version, you also need at least version 22.

Hey everyone!

Even though MMM-Remote-Control is the most popular third-party MagicMirror² module (measured by GitHub stars), it looks like it never properly introduced here in the forum. Today’s v4 release seems like the perfect opportunity to change that!

What is MMM-Remote-Control?

MMM-Remote-Control lets you control your MagicMirror² from any device on your network – your phone, tablet, or computer. So you can control your mirror from your couch using your cell phone, for example.
No need to SSH into your Pi or edit config files manually anymore. With a simple web interface, you can:

• Show/hide modules on the fly
• Adjust brightness and color temperature
• Update modules and MagicMirror² itself
• Install new modules directly from the interface
• Edit your config.js with a visual editor
• Restart or shut down your mirror
• Send notifications and alerts
• Control your monitor (turn on/off)
• And much more through a comprehensive REST API

How to use it?

Just follow the instructions on the GitHub page.

What’s new in v4?

This release is the biggest update in years – a complete modernization of both the user interface and the underlying code:

For Users:

• Completely redesigned interface – Modern look, smoother animations, better usability
• QR Code on your mirror – Just scan it with your phone to instantly access the remote control. No more typing IP addresses!

Under the Hood:

• Code modernized to current JavaScript standards
• Massively expanded test suite for better reliability
• Enhanced error handling throughout
• Better documentation and maintainability

Important Note: While there shouldn’t be any breaking changes, I recommend testing thoroughly after updating due to the extent of the changes.

You can find the complete changelog and installation instructions on GitHub.

I’m looking forward to your feedback! If you run into any issues or have ideas for improvements, feel free to open an issue on GitHub.

Have fun with the update!

Some Screenshots

On Mobile Device

Main Menu

Power Menu

View Menu

optional QR Code on the mirror

MMM-WindyV2 seems not maintained anymore. Did you see there is a newer fork: https://github.com/jhogendorn/MMM-WindyV3/ ?

@MikeTheYeti On the module list (https://modules.magicmirror.builders/) is no module named MMM-WindyV2. Where did you get it?

@hearter Looks good :-) Don’t forget to add it to the module list: https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-party-modules

@ercanermis I like that! Don’t forget to add it to the module list: https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-party-modules :-)

MMM-Mastodon is a compact module that displays Mastodon timelines directly on the mirror.

What is Mastodon?

Mastodon is a decentralized social network where users toot, connect, and join open communities across the fediverse.

See: https://joinmastodon.org/

What makes Mastodon special

• Decentralized: independent instances with their own rules.
• Community-focused: chronological feeds and topic-based communities.
• Open-source: the software is open and can be self‑hosted or audited.
• Privacy-friendly and open compared to centralized platforms.

What the module does

• Displays Home timelines, hashtag feeds, or profile timelines.
• Supports media thumbnails, QR codes linking to posts, and a rotation mode for posts.

Screenshot

---

Repository: github.com/KristjanESPERANTO/MMM-Mastodon

@edwardbuck said in MM2 fails to start after upgrade from 2.29 to 2.33 on windows:

I have MagicMirror running on Windows10.

You certainly knew that, but Windows 10 support ends tomorrow. It’s about time to think about an alternative. See https://distrochooser.de/.

[2.33.0] - 2025-10-01

Thanks to: @Crazylegstoo, @dathbe, @m-idler, @plebcity, @khassel, @KristjanESPERANTO, @rejas and @sdetweil!

⚠️ This release needs nodejs version v22.18.0 or higher

Added

• Add configuration option for User-Agent, used by calendar & news module (#3255)
• [linter] Add prettier plugin for nunjuck templates (#3887)
• [core] Add clear log for occupied port at startup (#3890)

Changed

• [clock] Add CSS to prevent line breaking of sunset/sunrise time display (#3816)
• [core] Enhance system information logging format and include additional env and RAM details (#3839, #3843)
• [refactor] Add new file js/module_functions.js to move code used in several modules to one place (#3837)
• [refactor] Use global.root_path where possible and add tests for config:check (#3883, #3885, #3886, #3889)
• [tests] refactor: simplify jest config file (#3844)
• [tests] refactor: extract constants for weather electron tests (#3845)
• [tests] refactor: add setupDOMEnvironment helper function to eliminate repetitive JSDOM setup code (#3860)
• [tests] replace console with Log in calendar debug.js to avoid exception in eslint config (#3846)
• [tests] speed up e2e tests, cleanup and stabilize weather e2e tests, update snapshot url (#3847, #3848, #3861)
• [tests] refactor translation tests (#3866)
  • Remove sinon dependency in favor of Jest native mocking
  • Unify test helper functions across translation test suites
  • Rename setupDOMEnvironment to createTranslationTestEnvironment for consistency
  • Simplify DOM setup by removing unnecessary Promise/async patterns
  • Avoid potential port conflicts by using port 3001 for translator unit tests
  • Improve test reliability and maintainability
• [tests] add alert module tests for different welcome_message configurations (#3867)
• [lint-staged] use prettier --write --ignore-unknown in lint-staged to avoid errors on unsupported files (#3888)

Updated

• [calendar] Update defaultSymbol name and also the link to the icon search site (#3879)
• [core] Update dependencies including electron to v38 as well as github actions (#3831, #3849, #3857, #3858, #3872, #3876, #3882, #3891, #3896)
• [weather] Update feels_like temperature calculation formula (#3869)
• [weather] Update null value handling for weather type (#3892)
• [layout] Update styles for weather and calendar (#3894)

Fixed

• [calendar] Fixed broken unittest that only broke on the 1st of July and 1st of january (#3830)
• [clock] Fixed missing icons when no other modules with icons is loaded (#3834)
• [weather] Fixed handling of empty values in weathergov providers handling of precipitationAmount (#3859)
• [calendar] Fix regression handling of limit days (#3840)
• [calendar] Fixed regression of calendarfetcherutils.shouldEventBeExcluded (#3841)
• [core] Fixed socket.io timeout when server is slow to send notification, notification lost at client (#3380)
• [tests] refactor AnimateCSS tests after jsdom 27 upgrade (#3891)
• [weather] Use apparent_temperature data from openmeteo’s hourly weather for current feelsLikeTemp (#3868).
• [weather] Updated envcanada Provider to use new database/URL schema for accessing weather data (#3878).

@CuddlyCow Interesting. Let us know when it’s available again, than I or someone else can re-add it to the list again. I had to remove it because a not reachable repository breaks the workflow for the module list website. I’m working on improving that, but I don’t think I’ll manage it anytime soon.

@CuddlyCow That sounds frustrating. Hang in there! 🙂

@CuddlyCow The URL still doesn’t work 😕 I have removed it from the module list. Please add it back once the issue has been resolved.

Even your GitHub user profile is not accessible, which is really strange 🤔

@lucallmon said in NFL games not showing up?:

MMM-MyScoreboard

Do you use the fork from @dathbe?

Run git remote -v in the module’s directory to find out.

@mvrlogins said in [MMM-Remote-Control] Cannot GET /remote.html:

0|MagicMir | [2025-09-21 16:44:59.284] [ERROR] Error when loading MMM-Remote-Control: require() of ES Module /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/uuid/dist-node/index.js from /home/pi/MagicMirror/modules/MMM-Remote-Control/API/api.js not supported.

To make it clear here as well: “require() of ES Module ... not supported” shows that you are using a very old (unsupported) Node version. Like I said in the GitHub issue, you have to update Node.

I recommend using NVM to update Node (like recommended on the Node website).

FYI: I’ve created a fork, refactored it and optimized the README. It should be easier to install :-)