Read the statement by Michael Teeuw here.
How to MANUALLY install MM on your Pi. For absolute beginners.
-
@Mykle1
The MM autostarts when booting up the Pi, what’s the command you use to apply/run the config.js right after you save it? -
@noorm91 said in How to MANUALLY install MM on your Pi. For absolute beginners.:
The MM autostarts when booting up the Pi, what’s the command you use to apply/run the config.js right after you save it?
When the mirror is running, press your
Alt
key to drop down a menu bar. ChooseMinimize
from the Window menu. Assuming pm2 is autostarting for you, open a terminal and typepm2 stop mm
to quit MM.You can start MM after saving your config in the terminal by typing
pm2 start mm
, or if MM is still running, from the drop down menu, View, Reload -
The problem was the module watchdog !
Also with fresh install it throws errors with the newest update.Fixed for me. Thank you @Mykle1 !!!
-
I don’t know if this is the right place for me to reply but I’m desperate.
I’m supposed to do a project for school with the MM but I can’t even seem to get it up and running.
I made an issue on the forum but so far I’ve gotten no replies :(I followed these steps to reinstall the MM but instead of making my own config file I used the one provided. When I run it, the screen is black and I can see in dev tools that the “moment” npm package is having some issues but I can’t find any info anywhere on how to solve it or anyone that has a similar issue.
-
@fox said in How to MANUALLY install MM on your Pi. For absolute beginners.:
Fixed for me. Thank you @Mykle1 !!!
You’re welcome, mate.
-
@axellejamous said in How to MANUALLY install MM on your Pi. For absolute beginners.:
I followed these steps to reinstall the MM but instead of making my own config file I used the one provided. When I run it, the screen is black and I can see in dev tools that the “moment” npm package is having some issues but I can’t find any info anywhere on how to solve it or anyone that has a similar issue.
I see that you have fixed your issue in another topic. Very good! Can I ask, are you saying you had this issue after a manual installation? The symptoms and fix you used are commonly associated with the automatic installer or version update. I’m just curious because I have not heard of this happening after a manual installation.
-
@Mykle1
I did luckily!
I indeed had the issue after manual installation. Fact is, the automatic installation script would actually get stuck on two of my Pi’s at the node modules installation.
So I had to manually install.In the issue that helped me find the answer, he did do a manual install as well and had the same problem.
But someone did mention “in the latest version there is a npm install task in the vendor folder as well which gets executed automatically after a successful install, yours wasn’t successful so this was never executed” which means I probably made a mistake in my manual installation, although I have no clue what it could’ve is as I followed the steps thoroughly on 2 different pi’s, getting the same result. -
@axellejamous said in How to MANUALLY install MM on your Pi. For absolute beginners.:
I probably made a mistake in my manual installation,
No sir, you made no mistake. You download the software and run npm install in the MagicMirror directory. If, and when that fails, it is no fault of yours.
I’m glad you solved your problem and thanks for the information. It’s good to know that in case anyone else encounters that problem with a manual installation.
-
@axellejamous I still got no luck making 2.1.3 works. the log said MM run without error. Unfortunately, got a black screen using default config.js (copy from config.js.sample). If I remove config.js, the MM display to create a config. Still no clue how to solve this.
-
@slametps said in How to MANUALLY install MM on your Pi. For absolute beginners.:
If I remove config.js, the MM display to create a config. Still no clue how to solve this.
You did a manual install and ran
npm install
in the MagicMirror directory? He solved his problem by runningnpm install
in the vendor directory. I don’t know if you have the same issue.But it seems to me if MM is reporting “Create a config” that MM is launching correctly. You could try getting a fresh copy of the config.js.sample (in case something is wrong with the one you have) and trying again.
Good luck