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 from 2.15 to 2.16

    Scheduled Pinned Locked Moved Solved Troubleshooting
    35 Posts 5 Posters 10.5k 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.
    • A Offline
      andyyy @sdetweil
      last edited by

      @sdetweil

      I tried it again. Now the electron does not even start.

      > magicmirror@2.16.0 start
      > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
      
      sh: 1: ./node_modules/.bin/electron: not found
      

      I tried to re-install electron with "sudo npm install electron@latest
      ", but no change.

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

        @bdream so you need to go to the
        MMM-DWD-Pollen folder and do
        npm install request --save

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          bdream @sdetweil
          last edited by

          @sdetweil I did it but don’t know what to do with these messages :face_with_rolling_eyes:

          pi@MagicMirror:~/MagicMirror/modules/MMM-DWD-Pollen $  npm install request --save
          npm WARN EBADENGINE Unsupported engine { package: 'magicmirror@2.16.0',
          npm WARN EBADENGINE   required: { node: '>=12' },
          npm WARN EBADENGINE   current: { node: 'v10.23.1', npm: '7.15.1' } }
          npm WARN EBADENGINE Unsupported engine { package: 'eslint-plugin-jsdoc@35.4.0',
          npm WARN EBADENGINE   required: { node: '>=12' },
          npm WARN EBADENGINE   current: { node: 'v10.23.1', npm: '7.15.1' } }
          npm WARN EBADENGINE Unsupported engine { package: 'jsdoc-type-pratt-parser@1.0.4',
          npm WARN EBADENGINE   required: { node: '>=12.0.0' },
          npm WARN EBADENGINE   current: { node: 'v10.23.1', npm: '7.15.1' } }
          npm WARN deprecated har-validator@5.1.5: this library is no longer supported
          npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
          npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
          npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
          
          added 628 packages, and audited 921 packages in 12m
          
          110 packages are looking for funding
            run `npm fund` for details
          
          found 0 vulnerabilities
          
          

          –
          cheers, bdream

          1 Reply Last reply Reply Quote 0
          • A Offline
            andyyy @sdetweil
            last edited by

            @sdetweil

            I got electron installed again with specifying a version (sudo npm install electron@6.1.12). No idea, why electron disappeared in the first place.

            @Fozi

            The MMM-MyCalender has indeed an issue with 2.16. causing a black screen. And MMM-Fuel is saying “undefined” for an unknown reason. Both modules are disabled for now.

            My MM boots and shows the all other modules again.

            With each MM update something crashes, mostly one of the 3rd party modules because one or more dependencies are lost/changed or deleted.

            Thanks for your help. Great community!

            S 2 Replies Last reply Reply Quote 0
            • S Do not disturb
              sdetweil @andyyy
              last edited by sdetweil

              @andyyy yeh, version 2.1.6 is on electron 11.4.9

              Sam

              How to add modules

              learning how to use browser developers window for css changes

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

                @andyyy i see you have npm version 7 installed… causes quite a few problems…

                I would fall back to npm 6

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                A 2 Replies Last reply Reply Quote 0
                • A Offline
                  andyyy @sdetweil
                  last edited by

                  @sdetweil

                  How do I revert to npm v6?

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

                    @andyyy sudo npm install -g npm@6.14.3

                    you will then have to cleanup from 7

                    cd ~/MagicMirror
                    rm -rf node_modules
                    npm install
                    

                    u may have to do the same in any module folder with a package.json file

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    1 Reply Last reply Reply Quote 0
                    • A Offline
                      andyyy @sdetweil
                      last edited by

                      @sdetweil

                      made it with npm install -g npm@6.14.14.

                      I still have issues with the default wheater module. The old “currentweather” module works but new default “weather” module just says “loading”.

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

                        @andyyy I would look in the window where u start mm

                        npm start or pm2

                        if pm2, the pm2 logs --lines=100

                        for any messages

                        loading is the default output til data arrives.
                        so it didn’t get the content from the api

                        is that forecast u are waiting for?
                        there is a timing issue, workaround with setting
                        (look it up for exact spelling)
                        initialLoadDelay:100

                        Sam

                        How to add modules

                        learning how to use browser developers window for css changes

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