Read the statement by Michael Teeuw here.
How to MANUALLY install MM on your Pi. For absolute beginners.
-
Hi @Mykle1 i get this error when i make
npm start
Error:
Whoops! There was an uncaught exception... { Error: listen EADDRINUSE 0.0.0.0:8080 at Object.exports._errnoException (util.js:1050:11) at exports._exceptionWithHostPort (util.js:1073:20) at Server.setupListenHandle [as _listen2] (net.js:1263:14) at listenInCluster (net.js:1304:12) at doListen (net.js:1428:7) at _combinedTickCallback (internal/process/next_tick.js:83:11) at process._tickCallback (internal/process/next_tick.js:104:9) at Module.runMain (module.js:607:11) at run (bootstrap_node.js:431:7) at startup (bootstrap_node.js:155:9) code: 'EADDRINUSE', errno: 'EADDRINUSE', syscall: 'listen', address: '0.0.0.0', port: 8080 }
edit:
withsudo netstat -lnptu
i saw that electron.js is already using the port. But i have a blank screen and nothing is shown. Also rebooted a couple of times.
-
@fox said in How to MANUALLY install MM on your Pi. For absolute beginners.:
i saw that electron.js is already using the port. But i have a blank screen and nothing is shown. Also rebooted a couple of times.
Hmm, make sure you only have 1 terminal open when you run npm start from the pi@user/MagicMirror directory. Also, make sure the
address: "0.0.0.0",
entry in your config is OUTSIDE the whitelist. If you’re running pm2 make sure that is not launching an instance of MM. Otherwise, is there anything else that you changed after the install? -
How do you apply after each module you try out? Is there a way or do you have to reboot every time?
-
@noorm91 said in How to MANUALLY install MM on your Pi. For absolute beginners.:
How do you apply after each module you try out? Is there a way or do you have to reboot every time?
You don’t have to reboot the Pi to launch MM after adding a module. Assuming you quit MM before you added the module, you simply launch MM as you normally would
-
@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.