MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    MMM-Remote-Control

    Scheduled Pinned Locked Moved Utilities
    52 Posts 9 Posters 2.1k Views 8 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B Offline
      bloodknot @bloodknot
      last edited by

      @kristjanesperanto
      It looks like something also happened to showalert:

      http://magicmirrorip:8080/api/module/alert/showalert?message=Hello&timer=2000&apiKey=********-****-****-****-**********

      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)
      
      KristjanESPERANTOK 1 Reply Last reply Reply Quote 0
      • KristjanESPERANTOK Offline
        KristjanESPERANTO Module Developer @bloodknot
        last edited by

        @bloodknot Thanks for reporting. Release v4.2.1 should fix it. Please check 🙂

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          bloodknot @KristjanESPERANTO
          last edited by

          @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."}
          
          KristjanESPERANTOK 1 Reply Last reply Reply Quote 0
          • KristjanESPERANTOK Offline
            KristjanESPERANTO Module Developer @bloodknot
            last edited by

            @bloodknot Thanks for the quick feedback. Okay, that was still progress. Now please try v4.2.2.

            B 2 Replies Last reply Reply Quote 0
            • B Offline
              bloodknot @KristjanESPERANTO
              last edited by

              @KristjanESPERANTO
              That seems to have fixed my specific problem. Thank you!!!
              I have tested:
              http://magicmirror2:8080/api/monitor/on

              1 Reply Last reply Reply Quote 0
              • B Offline
                bloodknot @KristjanESPERANTO
                last edited by

                @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

                KristjanESPERANTOK 1 Reply Last reply Reply Quote 0
                • KristjanESPERANTOK Offline
                  KristjanESPERANTO Module Developer @bloodknot
                  last edited by

                  @bloodknot Perfect, thank you for testing! 😃

                  1 Reply Last reply Reply Quote 0
                  • V Offline
                    vtek
                    last edited by

                    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
                                                                },
                    
                                }
                                },
                    
                    V 1 Reply Last reply Reply Quote 0
                    • V Offline
                      vtek @vtek
                      last edited by

                      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

                      1 Reply Last reply Reply Quote 2
                      • 1
                      • 2
                      • 3
                      • 4
                      • 5
                      • 6
                      • 3 / 6
                      • First post
                        Last post
                      Enjoying MagicMirror? Please consider a donation!
                      MagicMirror created by Michael Teeuw.
                      Forum managed by Sam, technical setup by Karsten.
                      This forum is using NodeBB as its core | Contributors
                      Contact | Privacy Policy