Read the statement by Michael Teeuw here.
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 -
@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?
Greetsall you have to do before run the module:
// Navigate to the new MMM-SystemStats folder and install the node dependencies. npm install // restart mm
-
Yes, thanks - the error has gone.
So i have to do npm install once and as a first step for every new moduleBut i didn’t have any values for CPU, RAM and Load …
Do you have an idea?
Thanks -
@MyMirror said in Need help to install the first new module to the mirror ...:
Yes, thanks - the error has gone.
So i have to do npm install once and as a first step for every new moduleBut i didn’t have any values for CPU, RAM and Load …
Do you have an idea?
ThanksNot 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.
-
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.bakThat’s all there is to it! :) Then you’re safe!