MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. rkorell
    3. Posts
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    R
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 23
    • Posts 379
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: MMM-Remote-Control

      @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

      posted in Utilities
      R
      rkorell
    • RE: MMM-Remote-Control

      @sdetweil
      Yes :-)

      In fact I’ve used

      npm ci --omit=dev
      

      this does the deletion of the node_modules folder inherently AFAIK …

      Thanks again, dear Sam!

      Ralf

      posted in Utilities
      R
      rkorell
    • RE: MMM-Remote-Control

      @sdetweil
      For some really strange reasons, neither

      pi@MagicMirrorPi5:~/MagicMirror/modules/MMM-Remote-Control $ git fetch --all --tags
      pi@MagicMirrorPi5:~/MagicMirror/modules/MMM-Remote-Control $ git fetch --tags
      

      currently give any feedback…

      So I’ve worked with the found git-hash:

      git checkout 1f451ce
      

      This at least worked and rolled back to V. 3.3.2.

      Unfortunately some dependencies (package-lock.json ???) are not strict enough, so the rollback produces an error message:

      [ERROR] Error when loading MMM-Remote-Control: require() of ES Module /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/uuid/dist-node/index.js from /home/pi/MagicMirror/modules/MMM-Remote-Control/API/api.js not supported.
      

      So I downgraded UUID:

      cd ~/MagicMirror/modules/MMM-Remote-Control
      npm install uuid@9.0.1
      npm ci --omit=dev
      

      With this module is running again.

      From now on I’m in a in ‘detached HEAD’ state - but this seems OK.
      Thanks for your time, effort and always great help!

      Ralf

      posted in Utilities
      R
      rkorell
    • RE: MMM-Remote-Control

      @sdetweil I’ve found V3.3.2 and just try "git checkout 1f451ce "

      posted in Utilities
      R
      rkorell
    • RE: MMM-Remote-Control

      @sdetweil
      BTW: Do you know if it is possible to restore the “old” version from remote-control?
      May THIS is the better option for me?

      posted in Utilities
      R
      rkorell
    • RE: MMM-Remote-Control

      @sdetweil
      just ran a testrun of your upgrade script:

      pi@MagicMirrorPi5:~/MagicMirror $ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"
      update log will be in /home/pi/MagicMirror/installers/upgrade.log
      
      doing test run = true, NO updates will be applied!
      
      Check current Node installation ...
      Node currently installed. Checking version number.
      Minimum Node version: v22.18.0
      Installed Node version: v20.18.1
      Node should be upgraded.
      Node.js upgrade defered, doing test run
      Check current NPM installation ...
      NPM currently installed. Checking version number.
      Minimum npm version: V10.9.2
      Installed npm version: V10.8.2
      npm should be upgraded.
      npm upgrade defered, doing test run  ...
      
      saving custom.css
      reverting to master branch from _fix_clipping, saving changed files
      would restore file modules/default/weather/current.njk before switch back to master branch
      would restore file package-lock.json before switch back to master branch
      would restore file package.json before switch back to master branch
      error: Your local changes to the following files would be overwritten by checkout:
              package-lock.json
              package.json
      Please commit your changes or stash them before you switch branches.
      Aborting
      unable to change back to master branch, stopping execution
      

      What does the last message mean?
      “unable to change back to master branch, stopping execution”
      What have I to do?

      posted in Utilities
      R
      rkorell
    • RE: MMM-Remote-Control

      @sdetweil
      Good point!
      Unfortunately I’ve already DONE the upgrade of remote-control - and now it doesn’t work anymore :-)

      posted in Utilities
      R
      rkorell
    • RE: MMM-Remote-Control

      @sdetweil
      Dear Sam,
      thanks for this.

      Until now I had avoided to upgrade with the thought “never touch a running system” …
      Now it seems to be time for an upgrade - because I like MMM-Remote-Control.
      @kristjanesperanto said: " at least node 22. I recommend version 24" - would one of these versions be installed by your current upgrade-script?

      Than I would feel much better using your script than doing it manually …

      As far as I remember i had some local (code) modifications in standard-weather module - this would prevent your upgrade-script from upgrading, as far as I remember.
      Is this still true? And if yes: There was a “force” ooption in the script?

      Thanks a lot for your work!

      Warmest regards,
      Ralf

      posted in Utilities
      R
      rkorell
    • RE: MMM-Remote-Control

      @KristjanESPERANTO

      OK…

      New version now shows the same error…
      Actually my mirror works pretty fine…
      So I hesitate to update node …
      What are the risks - and if: How do I do update node?

      • Will my mirror run afterwards or do I have to upgrade the mirror as well?

      Thanks for any advise!

      Warmest regards,
      Ralf

      I’m not able to attach the logfile…
      [2025-12-20T10_58_15_392Z-debug-0.log](Invalid file type. Allowed types are: .jpg, .jpeg, .png, .gif, .png, .jpg, .jpeg, .gif)

      posted in Utilities
      R
      rkorell
    • RE: MMM-Remote-Control

      @KristjanESPERANTO Good Evening!
      Nice work!
      I like it but with this update it doesn’t work anymore (for me, at least).
      I get an error message: “Cannot GET /remote.html”.

      I first tried to update with

      git pull
      npm ci --omit=dev
      

      This runs smooth, but results in the mentioned error message (mirror restarted :-) :

      pi@MagicMirrorPi5:~/MagicMirror/modules/MMM-Remote-Control $ npm ci --omit=dev
      
      > mmm-remote-control@4.0.1 postinstall
      > node scripts/postinstall.js
      
      modules.json already exists, skipping copy.
      
      > mmm-remote-control@4.0.1 prepare
      > simple-git-hooks || echo 'No problem. Skipping git hooks installation.'
      
      sh: 1: simple-git-hooks: not found
      No problem. Skipping git hooks installation.
      
      added 38 packages, and audited 39 packages in 9s
      
      4 packages are looking for funding
        run `npm fund` for details
      
      found 0 vulnerabilities
      
      

      After this I’ve tried to do the manual installation via:

      pi@MagicMirrorPi5:~/MagicMirror/modules/MMM-Remote-Control $ ~/MagicMirror/modules/MMM-Remote-Control/installer.sh
      

      this at least showed an error:

      Installation for the MagicMirror² Remote-Control module started!
      
      Notice: This script and the installed software is provided “as is”, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.
      
      >>> Continue? [y/N]? y
      
      Directory /home/pi/MagicMirror/modules/MMM-Remote-Control already exists.
      
      You are currently on the master branch.
      
      >>> Do you want to switch to the develop branch? [y/N]? N
      
      >>> Do you want to update your branch? [Y/n]? Y
      
      Pulling changes...
      Already up to date.
      
      Checking for new dependencies to install...
      
      
      > mmm-remote-control@4.0.1 postinstall
      > node scripts/postinstall.js
      
      modules.json already exists, skipping copy.
      
      > mmm-remote-control@4.0.1 prepare
      > simple-git-hooks || echo 'No problem. Skipping git hooks installation.'
      
      sh: 1: simple-git-hooks: not found
      No problem. Skipping git hooks installation.
      
      added 38 packages, and audited 39 packages in 3s
      
      4 packages are looking for funding
        run `npm fund` for details
      
      found 0 vulnerabilities
      Done.
      
      Update finished!
      node:internal/modules/cjs/loader:1544
            throw err;
            ^
      
      **Error [ERR_REQUIRE_ESM**]: require() of ES Module /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/uuid/dist-node/index.js from /home/pi/MagicMirror/modules/MMM-Remote-Control/[eval] not supported.
      Instead change the require of index.js in /home/pi/MagicMirror/modules/MMM-Remote-Control/[eval] to a dynamic import() which is available in all CommonJS modules.
          at [eval]:1:13
          at [eval]-wrapper:6:24 {
        code: 'ERR_REQUIRE_ESM'
      }
      
      Node.js v20.18.1
      
      >>> Do you want to view instructions on how to configure the module? [Y/n]? n
      
      You should also set an API key in your config section!
        It's dangerous to go alone! Take this.
        apiKey: ''
        I made it just for you.
      
      Have fun with the module, if you have any problems, please search for help on github or in the forum:
      
         Github : https://github.com/Jopyth/MMM-Remote-Control
         Forum  : https://forum.magicmirror.builders
      
      Do not forget to restart your MagicMirror² to activate the module! Installation finished.
      

      So my third and last try was a complete fresh installation - but again with no luck - and the same error message, which I’m not able to handle:

      pi@MagicMirrorPi5:~/MagicMirror/modules $ bash -c "$(curl -s https://raw.githubusercontent.com/Jopyth/MMM-Remote-Control/master/installer.sh)"
      
      Installation for the MagicMirror² Remote-Control module started!
      
      Notice: This script and the installed software is provided “as is”, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.
      
      >>> Continue? [y/N]? y
      
      MagicMirror² detected in: /home/pi/MagicMirror
      
      >>> Is this correct and do you want to start installation? [y/N]? y
      
      You can use either the master or the develop branch.
      The develop branch contains more features, but is also more likely to cause errors or crashes.
      This can be changed later by executing this script again, or using the git branch command.
      
      By default the master branch will be installed.
      
      >>> Do you want to install the develop branch instead? [y/N]? n
      
      Cloning the repository on master branch...
      
      Cloning into 'MMM-Remote-Control'...
      remote: Enumerating objects: 2748, done.
      remote: Counting objects: 100% (1098/1098), done.
      remote: Compressing objects: 100% (317/317), done.
      remote: Total 2748 (delta 866), reused 932 (delta 780), pack-reused 1650 (from 3)
      Receiving objects: 100% (2748/2748), 2.50 MiB | 1.13 MiB/s, done.
      Resolving deltas: 100% (1913/1913), done.
      
      Installing dependencies...
      
      
      > mmm-remote-control@4.0.1 postinstall
      > node scripts/postinstall.js
      
      Successfully created modules.json from template.
      
      > mmm-remote-control@4.0.1 prepare
      > simple-git-hooks || echo 'No problem. Skipping git hooks installation.'
      
      sh: 1: simple-git-hooks: not found
      No problem. Skipping git hooks installation.
      
      added 38 packages, and audited 39 packages in 3s
      
      4 packages are looking for funding
        run `npm fund` for details
      
      found 0 vulnerabilities
      Done.
      
      Installation finished.
      node:internal/modules/cjs/loader:1544
            throw err;
            ^
      
      **Error [ERR_REQUIRE_ESM]**: require() of ES Module /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/uuid/dist-node/index.js from /home/pi/MagicMirror/modules/MMM-Remote-Control/[eval] not supported.
      Instead change the require of index.js in /home/pi/MagicMirror/modules/MMM-Remote-Control/[eval] to a dynamic import() which is available in all CommonJS modules.
          at [eval]:1:13
          at [eval]-wrapper:6:24 {
        code: 'ERR_REQUIRE_ESM'
      }
      
      Node.js v20.18.1
      
      >>> Do you want to view instructions on how to configure the module? [Y/n]? n
      
      You should also set an API key in your config section!
        It's dangerous to go alone! Take this.
        apiKey: ''
        I made it just for you.
      
      Have fun with the module, if you have any problems, please search for help on github or in the forum:
      
         Github : https://github.com/Jopyth/MMM-Remote-Control
         Forum  : https://forum.magicmirror.builders
      
      Do not forget to restart your MagicMirror² to activate the module! Installation finished.
      
      

      Do you please have a hint for me how to solve this?

      MM is running on a Pi5 / NVME.

      Thanks for any advice!

      Warmest regards,
      Ralf

      posted in Utilities
      R
      rkorell
    • 1 / 1