Read the statement by Michael Teeuw here.
cant get magicmirror to show up on screen
-
Hey there,
i have completed all the steps in order to configure the rasp pi to run magicmirror but after running “pm2 start mm.sh” as on the guideline, the only thing I get is a terminal message approving that mm is running but it does not boot up.
Thanks in advance
-
Are you, by any chance, using a Raspberry Pi 1?
-
No, i am not. I am using the Raspberry Pi 3 Model B.
-
Alright. What happens when you open a browser window on your Pi and go to http://localhost:8080?
-
I get the “this site cant be reached” error
-
What information comes up when you enter “pm2 logs mm” in the terminal window?
-
I get a whole bunch of errors, but the output tells me that I either have wrong versions of nodejs or npm or the magicmirror package itself is the one to blame. After that comes the message that electron js/electron.js fails
Here is the log file that need to be submitted according to the log output:0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/nodejs’, ‘/usr/bin/npm’, ‘start’ ]
2 info using npm@3.10.3
3 info using node@v6.5.0
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle magicmirror@2.0.0~prestart: magicmirror@2.0.0
6 silly lifecycle magicmirror@2.0.0~prestart: no script for prestart, continuing
7 info lifecycle magicmirror@2.0.0~start: magicmirror@2.0.0
8 verbose lifecycle magicmirror@2.0.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle magicmirror@2.0.0~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
10 verbose lifecycle magicmirror@2.0.0~start: CWD: /home/pi/MagicMirror
11 silly lifecycle magicmirror@2.0.0~start: Args: [ ‘-c’, ‘electron js/electron.js’ ]
12 info lifecycle magicmirror@2.0.0~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.0.0 start:electron js/electron.js
13 verbose stack spawn ENOENT
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:33:16)
13 verbose stack at emitTwo (events.js:106:13)
13 verbose stack at ChildProcess.emit (events.js:191:7)
13 verbose stack at maybeClose (internal/child_process.js:877:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
14 verbose pkgid magicmirror@2.0.0
15 verbose cwd /home/pi/MagicMirror
16 error Linux 4.4.13-v7+
17 error argv “/usr/bin/nodejs” “/usr/bin/npm” “start”
18 error node v6.5.0
19 error npm v3.10.3
20 error file sh
21 error code ELIFECYCLE
22 error errno ENOENT
23 error syscall spawn
24 error magicmirror@2.0.0 start:electron js/electron.js
24 error spawn ENOENT
25 error Failed at the magicmirror@2.0.0 start script ‘electron js/electron.js’.
25 error Make sure you have the latest version of node.js and npm installed.
25 error If you do, this is most likely a problem with the magicmirror package,
25 error not with npm itself.
25 error Tell the author that this fails on your system:
25 error electron js/electron.js
25 error You can get information on how to open an issue for this project with:
25 error npm bugs magicmirror
25 error Or if that isn’t available, you can get their info via:
25 error npm owner ls magicmirror
25 error There is likely additional logging output above.
26 verbose exit [ 1, true ] -
Ok, there might be a problem with your electron installation.
Can you go into your MagicMirror folder and type “node serveronly”?Then, go back to your browser window and type in “localhost:8080”
-
Ok it is now working.
I will now try to enable kioskmode. -
This would mean that there seems to be a problem with your electron installation. Since you’ve got a Pi 3, I would try to get that fixed, it’s much easier to have the mirror act the way you want it to if the kiosk mode comes up automatically. I’m running the mirror on a Pi 1 and it took me forever to get everything set up so that the system boots into the mirror, I had to make sure the browser didn’t start too early, and so on. It requires many manual modifications and I’m almost certain that’s not the path you want to take :).
Your mirror installation is not properly set up, I would try to fix that.
I’m not sure if the problem on your system is electron or the mirror installation, as I’m not able to use electron on my Pi I have no experience with using it. But you can try going to your MagicMirror folder and typing in: “npm install electron”, this may set things right.
If it doesn’t, maybe try a reinstall.
-
I get an error every time. Both with npm install electron and by reinstalling the whole package. I dont get what the error is but it seems to be with nodejs.
-
Hm, like I said, anything I’m suggesting at this stage is purely experimental as I have no experience with setting up the MagicMirror electron environment, but you could try upgrading your node installation.
Please only do that if you are willing to set up your Pi all over again (Reinstalling Raspbian, etc.) should this fail, because it’s hardly ever a good idea to turn your system into a patchwork project.
Someone at stackexchange.com said this helped them in installing Node.js on their Pi 3:
curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash - sudo apt-get install -y nodejs sudo apt-get install -y build-essentialSource: http://raspberrypi.stackexchange.com/questions/45319/install-newer-node-version-on-pi-3
If you’re not willing to reinstall everything, should this compromise your Raspbian setup, I would suggest waiting for other forum members’ suggestions on how to proceed.
-
I had done just that, even before your post. And when i run nodejs -v it outputs v6… which is just fine. I don’t know, maybe I will reinstall raspbian and start it all over again
-
That might be the best way of going about it if you are only planning on using the Pi for the Magic Mirror.
Did you start out with a brand new Pi or did you install some other software on it as well? -
No, only this, but I first followed wrong instructions and installed unnecessary software that might have somehow affected the other installations.
-
Then do it again, since you’re only just starting, you will only lose an hour or so and hopefully end up with a working system. This way you can ensure you have a working mirror that is fun to configure. At this stage you’re having problems with it starting up, who knows what other problems might be lurking in the darker corners of your Raspbian installation. Just make sure you grab the latest Raspbian image when reinstalling.
Let us know whether it worked the second time round.
-
I will certainly let you know. Do you think that it would be better to run the automatic installation command or manually install nodejs, clone the rep and the install npm?
-
i did it like this on several pi’s now and never had issues https://forum.magicmirror.builders/topic/236/complete-setup-tutorial
-
@lysnikolaou Unfortunately, I have no experience with the automatic installation because it isn’t supported for my hardware setup. But it seems to be the best way of going about it and the instructions in the link @strawberry-3-141 has posted is the way to go, @KirAsh4 has put a lot of energy into it and if you follow it closely, I’d be surprised if you still ran into trouble.
-
Thanks a lot to both of you. I will inform you about the results, as soon as I have it done.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login