Read the statement by Michael Teeuw here.
MMM-Remote-Control
-
@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! :)If you cant find it, make it and share it
MMM-homeassistant-sensors,MMM-Modulebar,MMM-Profilepicture,MMM-Videoplayer,MMM-TautulliLatest -
@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ā¦ :)
If you cant find it, make it and share it
MMM-homeassistant-sensors,MMM-Modulebar,MMM-Profilepicture,MMM-Videoplayer,MMM-TautulliLatest -
@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! :)
If you cant find it, make it and share it
MMM-homeassistant-sensors,MMM-Modulebar,MMM-Profilepicture,MMM-Videoplayer,MMM-TautulliLatest -
@Snille Cool. Iām glad it works š
-
@KristjanESPERANTO - Cannot GET /api/refresh (or any API call)
MMM-Remote-Control is working fine on the same computer that the API is not found. This occurred in the last couple of updates. Nothing else changed in the configuration and/or modules.magicmirror2 = 192.168.4.21
http://magicmirror2:8080/remote.html#main-menu WORKS from 192.168.4.210
http://magicmirror2:8080/api/refresh Does NOT Work from 192.168.4.210MM Config: address: "0.0.0.0", port: 8080 basePath: "/", ipWhitelist:[], module: 'MMM-Remote-Control', config: { customCommand: {} showModuleApiMenu: true, secureEndpoints: true, apiKey: '********-****-****-****-************' showQRCode: falseGET http://magicmirror2:8080/api/refresh?apiKey=********-****-****-****-************ 404 (Not Found)What has changed? Did I miss an update? Any assistance will be great
-
@bloodknot I think I solved it, please update to v4.2.0 and check š
-
@KristjanESPERANTO
Update to 4.2.0 fixed the issue. Thanks for the quick response!! -
@kristjanesperanto
It looks like something also happened to showalert:TypeError: Cannot read properties of undefined (reading 'showalert') at Class.answerModuleApi (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/API/api.js:457:35) at /home/bloodknot/MagicMirror/modules/MMM-Remote-Control/API/api.js:296:14 at Layer.handleRequest (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/lib/layer.js:152:17) at next (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/lib/route.js:157:13) at Route.dispatch (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/lib/route.js:117:3) at handle (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:435:11) at Layer.handleRequest (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/lib/layer.js:152:17) at /home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:295:15 at param (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:600:14) at param (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:610:14) at param (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:610:14) at processParams (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:664:3) at next (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:291:5) at /home/bloodknot/MagicMirror/modules/MMM-Remote-Control/API/api.js:148:7 at Layer.handleRequest (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/lib/layer.js:152:17) at trimPrefix (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:342:13) -
@bloodknot Thanks for reporting. Release v4.2.1 should fix it. Please check š
-
@KristjanESPERANTO
I donāt get a failure, however the alert/showalert function does not work:{"success":false,"message":"Module alert does not have any actions defined."} -
@bloodknot Thanks for the quick feedback. Okay, that was still progress. Now please try v4.2.2.
-
@KristjanESPERANTO
That seems to have fixed my specific problem. Thank you!!!
I have tested:
http://magicmirror2:8080/api/monitor/on -
@KristjanESPERANTO
Sorry for the split message.
I have successfully tested:
http://magicmirrorip:8080/api/monitor/on
http://magicmirrorip:8080/api/monitor/off
http://magicmirrorip:8080/api/refresh
http://magicmirrorip:8080/api/reboot
http://magicmirrorip:8080/api/alert/showalert -
@bloodknot Perfect, thank you for testing! š
-
hey guysā¦
having some issues using the shutdown/reboot commandsā¦they throw this error, even though I have the API key in the config
{āsuccessā:false,āmessageā:āForbidden: API Key Not Provided!ā}
hereās the config
{ module: 'MMM-Remote-Control', // position: 'bottom_left', // Required to show URL/QR code on mirror // you can hide this module afterwards from the remote control itself config: { showModuleApiMenu: true, secureEndpoints: true, apiKey: "111111111-2222-3333-4444-555555555555", customCommand: { monitorOnCommand: 'loginctl unlock-session 1', monitorOffCommand: 'loginctl lock-session 1', shutdownCommand: 'systemctl poweroff', rebootCommand: 'systemctl reboot', // Optional, See "Using Custom Commands" below }, } }, -
said in MMM-Remote-Control:
hey guysā¦
having some issues using the shutdown/reboot commandsā¦they throw this error, even though I have the API key in the config
{āsuccessā:false,āmessageā:āForbidden: API Key Not Provided!ā}
hereās the config
{ module: 'MMM-Remote-Control', // position: 'bottom_left', // Required to show URL/QR code on mirror // you can hide this module afterwards from the remote control itself config: { showModuleApiMenu: true, secureEndpoints: true, apiKey: "111111111-2222-3333-4444-555555555555", customCommand: { monitorOnCommand: 'loginctl unlock-session 1', monitorOffCommand: 'loginctl lock-session 1', shutdownCommand: 'systemctl poweroff', rebootCommand: 'systemctl reboot', // Optional, See "Using Custom Commands" below }, } },i figure it outā¦had to append the apiKey at the end of the url for all commands
http://192.168.1.5:8888/api/command/rebootCommand?apiKey=111111111-2222-33333-4444
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better š
Register Login