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.

    Need help to install the first new module to the mirror ...

    Scheduled Pinned Locked Moved Troubleshooting
    8 Posts 4 Posters 3.4k Views 4 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.
    • M Offline
      MyMirror
      last edited by

      Thanks … i’ll read it :-)

      M 1 Reply Last reply Reply Quote 0
      • M Offline
        MyMirror @MyMirror
        last edited by

        @yawns
        First step - first Problem :-(
        When i install async i’ll get following:
        npm WARN grunt-yamllint@0.2.0 requires a peer of grunt@-0.4.0 but none was installed.

        I’ve ignored this warning, and get new contend on my mirror.
        CPU Temp/System Load/Free RAM : all “fetching” but no content
        Where is my fault?
        Greets

        slametpsS 1 Reply Last reply Reply Quote 0
        • slametpsS Offline
          slametps @MyMirror
          last edited by

          @MyMirror said in Need help to install the first new module to the mirror ...:

          @yawns
          First step - first Problem :-(
          When i install async i’ll get following:
          npm WARN grunt-yamllint@0.2.0 requires a peer of grunt@-0.4.0 but none was installed.

          I’ve ignored this warning, and get new contend on my mirror.
          CPU Temp/System Load/Free RAM : all “fetching” but no content
          Where is my fault?
          Greets

          all you have to do before run the module:

          // Navigate to the new MMM-SystemStats folder and install the node dependencies.
          npm install
          // restart mm
          

          regards,

          Slamet PS

          M 1 Reply Last reply Reply Quote 0
          • M Offline
            MyMirror @slametps
            last edited by

            @slametps

            Yes, thanks - the error has gone.
            So i have to do npm install once and as a first step for every new module

            But i didn’t have any values for CPU, RAM and Load …
            Do you have an idea?
            Thanks

            slametpsS 1 Reply Last reply Reply Quote 0
            • slametpsS Offline
              slametps @MyMirror
              last edited by

              @MyMirror said in Need help to install the first new module to the mirror ...:

              @slametps

              Yes, thanks - the error has gone.
              So i have to do npm install once and as a first step for every new module

              But i didn’t have any values for CPU, RAM and Load …
              Do you have an idea?
              Thanks

              Not every module required npm install. Pls refer to each module documentation.

              Please execute the following commands on your raspi shell (refer to node_helper.js of MMM-SystemStats):

              /opt/vc/bin/vcgencmd measure_temp
              cat /proc/loadavg
              free | awk '/^Mem:/ {print $4*100/$2}'
              

              all commands output something? If there are, pls check the mm-log or browser console-log.

              regards,

              Slamet PS

              1 Reply Last reply Reply Quote 0
              • cowboysdudeC Offline
                cowboysdude Module Developer
                last edited by cowboysdude

                I have found that I need to slow down and read the entire readme… many modules require “npm install”… that right there is more than 1/2 of the errors ;)

                I’m so glad you came to ask for help! I know it’s hard to do at times… I know myself I have an extremely difficult time asking for help…

                BUT just remember when you’re new at this go slow… take your time :) If you get into trouble just ask. HUGE suggestion… when you have a working config.js you should make a copy of it before you change anything in it… that way if you get into trouble you have a backup that you know works!

                Easy in a terminal window:

                ~MagicMirror/config
                cp config.js config.bak

                That’s all there is to it! :) Then you’re safe!

                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