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.

    Update breaks MM

    Scheduled Pinned Locked Moved Solved Troubleshooting
    4 Posts 2 Posters 251 Views 2 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.
    • R Offline
      ReD1470
      last edited by

      Hey Guys

      Still a noob at this, just love the mirror for daily use, info, etc

      So i decided yo run the 1 july update.
      (how i hate these updates, they rarely go well)

      got some errors back, other people had them as well
      npm error code EBADENGINE
      npm error engine Unsupported engine
      npm error engine Not compatible with your version of node/npm: magicmirror@2.32.0
      npm error notsup Not compatible with your version of node/npm: magicmirror@2.32.0
      npm error notsup Required: {“node”:“>=22.14.0”}
      npm error notsup Actual: {“npm”:“10.8.2”,“node”:“v20.18.1”}

      so i ran SdetWeil script to fix all
      now MM starts… until 3 seconds later, electron crashes

      0|mm | ### SYSTEM: manufacturer: ; model: ; virtual: false
      0|mm | ### OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.34+rpt-rpi-v8
      0|mm | ### VERSIONS: electron: 32.2.7; used node: 22.14.0; installed node: 22.14.0; npm: 10.9.2; pm2: 5.4.3
      0|mm | ### OTHER: timeZone: Europe/Amsterdam; ELECTRON_ENABLE_GPU: undefined
      0|mm | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT

      SO what oh what could it be.

      What are we gonne do? What log do you need?
      Much appreciated.

      S 1 Reply Last reply Reply Quote 0
      • S Offline
        sdetweil @ReD1470
        last edited by

        @ReD1470 this version, like last needs node version 22, you have version 20.

        if you had used the upgrade script, it would have updated that too.

        but once you do it manually and get to the current state, my script will abort

        reun the upgrade script with force as the parm instead of apply

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        1 Reply Last reply Reply Quote 1
        • R Offline
          ReD1470
          last edited by

          Sam,

          100% right! bad move on my part.
          But yes i did run your script 2x, and used apply. Force is not mentioned on https://github.com/sdetweil/MagicMirror_scripts

          So ran it again with force at the and…
          This must be a new record, the fastest fix!
          Not a single errog line in the log!

          Tnx Sam

          ps if u dont mind, i’ll be saving this command for later updates

          S 1 Reply Last reply Reply Quote 0
          • R ReD1470 has marked this topic as solved on
          • S Offline
            sdetweil @ReD1470
            last edited by

            @ReD1470 dont use force unless i tell you.

            it skips some checks that are useful.

            its not documented intentionally.

            Sam

            How to add modules

            learning how to use browser developers window for css changes

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