Read the statement by Michael Teeuw here.
MMM-Remote-Control
-
@meikelrix Please check new release 4.1.1 🙂
-
@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?
-
@meikelrix Did you set
showModuleApiMenulike 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).
-
@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! -
@KristjanESPERANTO
I have this problem that has been bugging me for a while…
Check this clip: https://photos.app.goo.gl/Zahc5xqttn33frbKA < From APIMy 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/K9ktuXGKawoyHEez5Errors 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:15I 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! :) -
@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 🙂
-
@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… :)
-
@Snille That was tricky, but I think I’ve solved that too. Please take a look at the new release v4.1.5 🙂
-
@KristjanESPERANTO It is working!! Awesome! Thanks you very much! :)
-
@Snille Cool. I’m glad it works 🎉
