MMM-Remote-Control

[sdetweil]

@rkorell said in MMM-Remote-Control:

npm ci

be careful… the package.json was built and tested on a cloud based virtual machine.
pi and other hardware types MAY need a different version of a dependency, i’ve only seen it myself twice in 6 years, but

npm ci uses the exact package.json
npm install will get the appropriate for this platform, even if the version changes.

anyhow… I use npm install --omit=dev when I do the installs script or MMM-Config

[rkorell]

@sdetweil
OK; thanks for this hint.
May npm install has avoided the resulting error which I had to solve…

Anyway: Thanks a LOT!
Regards,
Ralf

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

[KristjanESPERANTO]

@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

[sdetweil]

@KristjanESPERANTO n also allows you to change version on the fly.

One nvm ‘benefit’, it stores the node versions in the users home folder at .nvm

So, on a multi-user system each user could have different node versions.

As MagicMirror is deployed as only user, it’s functionally the same.

One n benefit, it stores the version in the /usr/ local folder
So it requires sudo to make the change, cannot be accidental

[KristjanESPERANTO]

@sdetweil said in MMM-Remote-Control:

So it requires sudo to make the change, …

This can also be seen as a disadvantage 🙂

[sdetweil]

@KristjanESPERANTO maybe, if you never use sudo, but we use it very often

[meikelrix]

@KristjanESPERANTO Hi, I very much like MMM-Remote-Control!

The last update has possibly introduced an error with respect to the “Custom Menu Items” => I have a menu item which still shows, but the sub menu items don’t show anymore?

Else wise please let me repeat: excellent job on MMM-Remote-Control!

[meikelrix]

said in MMM-Remote-Control:

@KristjanESPERANTO Hi, I very much like MMM-Remote-Control!

The last update has possibly introduced an error with respect to the “Custom Menu Items” => I have a menu item which still shows, but the sub menu items don’t show anymore?

Else wise please let me repeat: excellent job on MMM-Remote-Control!

FWIW: I’m using the showModuleApiMenu: true setting in config.js as well and the submenus there don’t show either, any more?

[KristjanESPERANTO]

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

[KristjanESPERANTO]

@meikelrix Please check new release 4.1.1 🙂

[meikelrix]

@KristjanESPERANTO said in MMM-Remote-Control:

@meikelrix Please check new release 4.1.1 🙂

Thank you very much, that has fixed my custom menu!

On the other hand I still don’t see the content of “Modules Controls” menu, although “showModuleApiMenu: true” is set in config.js?

[KristjanESPERANTO]

@meikelrix Did you set showModuleApiMenu like this?

    {
      module: "MMM-Remote-Control",
      position: "bottom_right",
      config: {
        showModuleApiMenu: true,
      ....

Do you also have modules with recognizable notifications? Newsfeed is quite good for testing, for example.

If it doesn’t work, show me your config (without secrets of course).

[meikelrix]

@KristjanESPERANTO I did set the showModuleApiMenu: true,
I do get the “Module Controls” menu entry, but it has no content AND other notification based modules are working.
I noticed as well that the “Updates” doesn’t show modules, anymore. The only one shown is “MagicMirror”, below the message “!No module loaded.”

Ok, I renamed MMM-Remote-Contol directory and re-installed following the github instructions. All is working now!
Thank you for your help and a great module!

[Snille]

@KristjanESPERANTO
I have this problem that has been bugging me for a while…
Check this clip: https://photos.app.goo.gl/Zahc5xqttn33frbKA < From API

My mirror have lot’s of modules many are multi instances (like MMM-MotionEye in this example).
I see the same behavior (or similar) with other modules, mainly my “MMM-homeassistant-sensors”…
I often makes API-calls from Node Red in Home Assistant, like this clip: https://photos.app.goo.gl/K9ktuXGKawoyHEez5

Errors from the log:

0|mmdev  | [2026-01-05 12:24:13.812] [ERROR] undefined Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
0|mmdev  |     at ServerResponse.setHeader (node:_http_outgoing:700:11)
0|mmdev  |     at ServerResponse.header (/var/www/html/magicmirror/m/node_modules/express/lib/response.js:686:10)
0|mmdev  |     at ServerResponse.json (/var/www/html/magicmirror/m/node_modules/express/lib/response.js:249:10)
0|mmdev  |     at Class.sendResponse (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:687:28)
0|mmdev  |     at Class.handleSimpleSocketNotification (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:965:10)
0|mmdev  |     at SHOW (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:1024:28)
0|mmdev  |     at Class.executeQuery (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:1049:7)
0|mmdev  |     at Class.answerModuleApi (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/API/api.js:442:14)
0|mmdev  |     at /var/www/html/magicmirror/m/modules/MMM-Remote-Control/API/api.js:299:14
0|mmdev  |     at Layer.handleRequest (/var/www/html/magicmirror/m/node_modules/router/lib/layer.js:152:17)
0|mmdev  |     at next (/var/www/html/magicmirror/m/node_modules/router/lib/route.js:157:13)
0|mmdev  |     at Route.dispatch (/var/www/html/magicmirror/m/node_modules/router/lib/route.js:117:3)
0|mmdev  |     at handle (/var/www/html/magicmirror/m/node_modules/router/index.js:435:11)
0|mmdev  |     at Layer.handleRequest (/var/www/html/magicmirror/m/node_modules/router/lib/layer.js:152:17)
0|mmdev  |     at /var/www/html/magicmirror/m/node_modules/router/index.js:295:15
0|mmdev  |     at param (/var/www/html/magicmirror/m/node_modules/router/index.js:600:14)
0|mmdev  | [2026-01-05 12:24:28.662] [ERROR] undefined Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
0|mmdev  |     at ServerResponse.setHeader (node:_http_outgoing:700:11)
0|mmdev  |     at ServerResponse.header (/var/www/html/magicmirror/m/node_modules/express/lib/response.js:686:10)
0|mmdev  |     at ServerResponse.send (/var/www/html/magicmirror/m/node_modules/express/lib/response.js:163:12)
0|mmdev  |     at ServerResponse.json (/var/www/html/magicmirror/m/node_modules/express/lib/response.js:252:15)
0|mmdev  |     at Class.sendResponse (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:687:28)
0|mmdev  |     at Class.handleSimpleSocketNotification (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:965:10)
0|mmdev  |     at HIDE (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:1023:28)
0|mmdev  |     at Class.executeQuery (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:1049:7)
0|mmdev  |     at Class.answerModuleApi (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/API/api.js:442:14)
0|mmdev  |     at /var/www/html/magicmirror/m/modules/MMM-Remote-Control/API/api.js:299:14
0|mmdev  |     at Layer.handleRequest (/var/www/html/magicmirror/m/node_modules/router/lib/layer.js:152:17)
0|mmdev  |     at next (/var/www/html/magicmirror/m/node_modules/router/lib/route.js:157:13)
0|mmdev  |     at Route.dispatch (/var/www/html/magicmirror/m/node_modules/router/lib/route.js:117:3)
0|mmdev  |     at handle (/var/www/html/magicmirror/m/node_modules/router/index.js:435:11)
0|mmdev  |     at Layer.handleRequest (/var/www/html/magicmirror/m/node_modules/router/lib/layer.js:152:17)
0|mmdev  |     at /var/www/html/magicmirror/m/node_modules/router/index.js:295:15

I also experience that when calling a specific module to show with “module_number_modulename”, it often shows the “wrong” module-instance (of that type of module, like MMM-homeassistant-sensors, but the wrong one)… I don’t know if it’s related to this.

Let me know if you need anything more…
Thank you for this great module! :)

[KristjanESPERANTO]

@Snille Thanks for the detailed report. I think I’ve fixed it. Please update to the new release v4.1.4 and give me some feedback 🙂

[Snille]

@KristjanESPERANTO You are welcome, It’s me who should thank you for all the great stuff! :) It’s almost working…
The error messages are gone, but it still shows and hides “both” modules (MMM-MotionEye in my example clip)… :)

Let me know if you want anything else? There is nothing in the “logs” now… :)

[KristjanESPERANTO]

@Snille That was tricky, but I think I’ve solved that too. Please take a look at the new release v4.1.5 🙂

[Snille]

@KristjanESPERANTO It is working!! Awesome! Thanks you very much! :)

[KristjanESPERANTO]

@Snille Cool. I’m glad it works 🎉