Module Developers group

KristjanESPERANTO

So it requires sudo to make the change, …

This can also be seen as a disadvantage 🙂

KristjanESPERANTO

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

KristjanESPERANTO

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.

BKeyport

what’s with the microupdates? I’ve updated three times today. 🤣

KristjanESPERANTO

@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.

KristjanESPERANTO

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

wishmaster270

@Queasy
Great to hear that. As I am using Debian 12 at the moment I am optimistic it is working for older installations, too.

I think the topic is solved then.

wishmaster270

@Queasy
Hi and sorry for the late reply.

I released a new version of the module a couple of minutes ago which should fix the problem.

It uses the new version of the lib for newer operation systems and changes to a other branch if it is a old debian otherwise.

As expected the api of the lib changed and i needed to do a small change in the modules node_helper.js.

PierreGode

@johngalt @sdetweil @redbeardedninja @sarote @mischag @plainbroke @

New big update out now.
New reward system
more recurring options

Fixes and updates.

bhepler

@mmmallday - I don’t know why I’m not getting notifications from the forum but I’m just now seeing these replies to the thread.

Thank you for your work in updating the module. I’ve merged your pull request into the baseline. I encourage everyone to update the module and check out the new features.

P	paviro
M	MichMich
Y	yawns
M	morozgrafix
J	Jopyth
J	Jacopo1891
F	FrostByte
K	kcs897
B	Bocah4d
I	idproslotpay4d
L	liquortheka
S	staceyhughes271
P	preeti25
A	alexmann
A	abigailuna
2	2hdlockness
N	newkoll
M	mrprc
G	goof_smith
A	Andrei.L