• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
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-NewPIR v3

Scheduled Pinned Locked Moved System
67 Posts 18 Posters 25.0k Views 20 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 Away
    sdetweil @cowboysdude
    last edited by Sep 11, 2021, 2:23 AM

    @cowboysdude I don’t understand the question?

    it supports all the different screen dimming approaches

    Sam

    How to add modules

    learning how to use browser developers window for css changes

    C 1 Reply Last reply Sep 11, 2021, 2:43 AM Reply Quote 1
    • C Offline
      cowboysdude Module Developer @sdetweil
      last edited by Sep 11, 2021, 2:43 AM

      @sdetweil Thanks Sam.

      1 Reply Last reply Reply Quote 1
      • P Offline
        philmavedzenge
        last edited by Oct 6, 2021, 7:19 AM

        Hi guys,

        After updating my MagicMirror to the latest version, this modules does not work. I tried reinstalling but its giving an error that i do not understand. Could someone help please? I have attached the logs, not sure if they will help.

        at Module._compile (internal/modules/cjs/loader.js:778:30)
        

        npm WARN notsup Unsupported engine for electron-rebuild@3.2.3: wanted: {“node”:“>=12.13.0”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
        npm WARN notsup Not compatible with your version of node/npm: electron-rebuild@3.2.3
        npm WARN notsup Unsupported engine for @malept/cross-spawn-promise@2.0.0: wanted: {“node”:“>= 12.13.0”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
        npm WARN notsup Not compatible with your version of node/npm: @malept/cross-spawn-promise@2.0.0
        npm WARN notsup Unsupported engine for fs-extra@10.0.0: wanted: {“node”:“>=12”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
        npm WARN notsup Not compatible with your version of node/npm: fs-extra@10.0.0
        npm WARN notsup Unsupported engine for yargs@17.2.1: wanted: {“node”:“>=12”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})
        npm WARN notsup Not compatible with your version of node/npm: yargs@17.2.1

        npm ERR! code ELIFECYCLE
        npm ERR! errno 1
        npm ERR! @bugsounet/pir@1.0.6 postinstall: electron-rebuild
        npm ERR! Exit status 1
        npm ERR!
        npm ERR! Failed at the @bugsounet/pir@1.0.6 postinstall script.
        npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

        1 Reply Last reply Reply Quote 0
        • D Offline
          DJBOOB66
          last edited by Oct 6, 2021, 7:59 AM

          @philmavedzenge said in MMM-NewPIR v3:

          npm WARN notsup Unsupported engine for yargs@17.2.1: wanted: {“node”:“>=12”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})

          You need to update npm and node

          P 1 Reply Last reply Oct 6, 2021, 2:52 PM Reply Quote 0
          • P Offline
            philmavedzenge @DJBOOB66
            last edited by Oct 6, 2021, 2:52 PM

            @djboob66 said in MMM-NewPIR v3:

            @philmavedzenge said in MMM-NewPIR v3:

            npm WARN notsup Unsupported engine for yargs@17.2.1: wanted: {“node”:“>=12”} (current: {“node”:“10.24.0”,“npm”:“6.13.6”})

            You need to update npm and node

            Thanks for the response. How do I do that? Which folder should I update it in?

            F 1 Reply Last reply Oct 6, 2021, 5:10 PM Reply Quote 0
            • F Offline
              Fozi Project Sponsor @philmavedzenge
              last edited by Fozi Oct 6, 2021, 5:14 PM Oct 6, 2021, 5:10 PM

              @philmavedzenge in your home directory execute following two commands:

              sudo npm  install -g n
              sudo n latest
              

              This installs the latest node version

              Edit: added sudo

              HowTo: Replace PIR Sensor with a RCWL-0516 Microwave Sensor

              1 Reply Last reply Reply Quote 0
              • D Offline
                DJBOOB66
                last edited by Oct 6, 2021, 6:51 PM

                Ok you need to find a working node and npm for all module if you have Bugs Google Aisstant v3 then it is best to check the module first GA v3 needs,
                Node: v12.x.x upto v14.x.x
                npm: = v6.14.15 (some trouble with v7.x)
                I suggest trying.
                Do in this order.

                sudo npm cache clean -f
                sudo npm install -g n
                sudo n 14.0
                

                now check npm with npm -v
                If 6.14.15 do nothing more but over 7.x use below

                sudo npm install -g npm@6.14.15
                
                F P 2 Replies Last reply Oct 6, 2021, 7:54 PM Reply Quote 0
                • F Offline
                  Fozi Project Sponsor @DJBOOB66
                  last edited by Fozi Oct 6, 2021, 7:54 PM Oct 6, 2021, 7:54 PM

                  @djboob66 you’re right…I forgot that there might be potential issues with the latest version. Thanks for the correction!

                  @philmavedzenge : Generally I’d recommend to use @sdetweil update script when updating to a new MM version. (see here) As you already updated to 2.17.1, use this command with force at he end instead of apply

                  
                  bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force
                  
                  

                  Sam‘s script checks, if the correct node and npm versions are installed and updates them accorgingly if necessary.

                  HowTo: Replace PIR Sensor with a RCWL-0516 Microwave Sensor

                  P 1 Reply Last reply Oct 6, 2021, 8:50 PM Reply Quote 0
                  • P Offline
                    philmavedzenge @DJBOOB66
                    last edited by Oct 6, 2021, 8:48 PM

                    @djboob66 said in MMM-NewPIR v3:

                    sudo npm install -g npm@6.14.15

                    thank you guys very much, this worked for me

                    1 Reply Last reply Reply Quote 0
                    • P Offline
                      philmavedzenge @Fozi
                      last edited by Oct 6, 2021, 8:50 PM

                      @fozi i had used that script to update, i don’t know why it didn’t update the other components. Thanks a lot for your help

                      S 1 Reply Last reply Oct 6, 2021, 9:06 PM Reply Quote 0
                      • 1
                      • 2
                      • 3
                      • 4
                      • 5
                      • 6
                      • 7
                      • 6 / 7
                      • 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