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
    22 Posts 5 Posters 53 Views 5 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.
    • S Do not disturb
      sdetweil @rkorell
      last edited by

      @rkorell if you pull the tags, you can use the tag name

      git checkout v3.3.2

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      R 1 Reply Last reply Reply Quote 0
      • R Online
        rkorell @sdetweil
        last edited by rkorell

        @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

        S 1 Reply Last reply Reply Quote 0
        • S Do not disturb
          sdetweil @rkorell
          last edited by

          @rkorell I was just about to add that you needed to redo the npm install for the module after deleting the node_modules folder
          else you were trying to run the new dependencies with the old code

          but you fixed it…

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          R 1 Reply Last reply Reply Quote 0
          • R Online
            rkorell @sdetweil
            last edited by

            @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

            S 1 Reply Last reply Reply Quote 0
            • S Do not disturb
              sdetweil @rkorell
              last edited by

              @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

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              R 1 Reply Last reply Reply Quote 0
              • R Online
                rkorell @sdetweil
                last edited by

                @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

                1 Reply Last reply Reply Quote 0
                • 1
                • 2
                • 3
                • 3 / 3
                • 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