Read the statement by Michael Teeuw here.
Problem after installing MM on Pi Zero W
-
Ok I was a bit too fast.
After installing the libaries no errors occur, but after rebooting the PiZeroW this happens:
pi@magicmirror:~ $ npm start npm ERR! Linux 4.9.35+ npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" npm ERR! node v4.2.1 npm ERR! npm v2.14.7 npm ERR! path /home/pi/package.json npm ERR! code ENOENT npm ERR! errno -2 npm ERR! syscall open npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' npm ERR! enoent This is most likely not a problem with npm itself npm ERR! enoent and is related to npm not being able to find a file. npm ERR! enoent npm ERR! Please include the following file with any support request: npm ERR! /home/pi/npm-debug.log
I did not search for this in the forum yet, maybe you have a quick answer for this again.
(maybe this is easy again, but I’m not good at debuging this error output) -
-
@Mykle1 said in Problem after installing MM on Pi Zero W:
Are you running npm start from your MagicMirror directory?
pi@magicmirror~/MagicMirror
no I didn’t , now there are no errors. Thanks.
But now the screen is black again.
npm start
works, … hmm …is the configsample.js maybe not working with the Pi Zero ?Is there a way to test the MM with an other method ? ( I’m using Midori, like in the tutorial)
-
@abergy if there is a module using es6 features it could be a reason for the black screen. can you check the developer console in midori for errors?
-
Can I check the errorlog over the commandline somehow?
If I google the “Black screen” problem with the Pi zero W, there are a lot of questions but now solutions.
Someone said ist maybe because of the ARM6 Arch. on the Pi Zero!?Should I buy a Raspi3 to save my nerves ^^?
-
@abergy said in Problem after installing MM on Pi Zero W:
Should I buy a Raspi3 to save my nerves ^^?
There is certainly less trouble with a Pi3. Installation is more direct and you don’t need any work-arounds. Your nerves are another matter. :^)
-
@abergy actually you can’t as the logs are related to your browser (midori)
-
I had the same issue. Tried Chromium instead Midori, where it works fine.