Read the statement by Michael Teeuw here.
How I got my Magic Mirror working on a Raspberry Pi 0 (zero)
-
first set:
set ipWhitelist: [] to allow all IP addresses.Warning, this enables from everywhere (on your net) have access.
then in webbrowser go to pizero ip with port set in config ex. 192.168.1.12:8080 and check if its working -
don’t work for me, cannot connect to destination :-(
when i do
DISPLAY=:0 npm start
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 related to npm not being able to find a file.
npm ERR! enoentnpm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2017-10-19T18_58_10_170Z-debug.log -
why he’s looking for /home/pi/package.json then it is /home/pi/MagicMirror/package.json ?
This is my log
/home/pi/.npm/_logs/2017-10-19T18_58_10_170Z-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/local/bin/node’, ‘/usr/local/bin/npm’, ‘start’ ]
2 info using npm@5.3.0
3 info using node@v8.3.0
4 verbose config Skipping project config: /home/pi/.npmrc. (matches userconfig)
5 verbose stack Error: ENOENT: no such file or directory, open ‘/home/pi/package.json’
6 verbose cwd /home/pi
7 verbose Linux 4.1.19+
8 verbose argv “/usr/local/bin/node” “/usr/local/bin/npm” “start”
9 verbose node v8.3.0
10 verbose npm v5.3.0
11 error path /home/pi/package.json
12 error code ENOENT
13 error errno -2
14 error syscall open
15 error enoent ENOENT: no such file or directory, open ‘/home/pi/package.json’
16 error enoent This is related to npm not being able to find a file.
17 verbose exit [ -2, true ] -
@Doubleve
In which directory did you executenpm start
? I would assume you would first go to your MagicMirror directory (cd /home/pi/MagicMirror
). This would also explain the problem with the missing package.json file.However, I’m not sure if
npm start
works at all in combination with the serveronly mode (needed for the Pi Zero). For starting, I use the method described in the first post of this thread in the section “Setting up boot scripts”.I can acccess my MM from remote, however still didn’t get it to show in the Midori browser :-/
-
as you said I was not in the right record.
I had an error with the libnss3 library. Now more errorDISPLAY =: 0 npm start
magicmirror@2.1.3 start / home / pi / MagicMirror
sh run-start.shpi @ raspberrypi ~ / MagicMirror $ npm run config: check
magicmirror@2.1.3 config: check / home / pi / MagicMirror
node tests / configs / check_config.jsChecking file … /home/pi/MagicMirror/config/config.js
Your configuration file not containt syntax error :)but it still does not work with midori
-
What does npm start do in /MagicMirror
-
@noorm91
npm start
is the command to start the Magic Mirror application and display the interface on the screen. -
@bhepler
I can’t seem to start MM with npm start, tried through SSH and directly on rpi with keyboard.pi@raspberrypi:~/MagicMirror $ DISPLAY=:0 nohup npm start &
[1] 890
pi@raspberrypi:~/MagicMirror $ nohup: ignoring input and appending output to ‘nohup.out’
^C
[1]+ Exit 1 DISPLAY=:0 nohup npm startpi@raspberrypi:~/MagicMirror $
pi@raspberrypi:~/MagicMirror $ npm startmagicmirror@2.1.0 start /home/pi/MagicMirror
electron js/electron.js/home/pi/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
npm ERR! Linux 4.4.34+
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! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! magicmirror@2.1.0 start:electron js/electron.js
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the magicmirror@2.1.0 start script ‘electron js/electron.js’.
npm ERR! This is most likely a problem with the magicmirror package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! electron js/electron.js
npm ERR! You can get their info via:
npm ERR! npm owner ls magicmirror
npm ERR! There is likely additional logging output above.npm ERR! Please include the following file with any support request:
npm ERR! /home/pi/MagicMirror/npm-debug.log -
@noorm91 said in How I got my Magic Mirror working on a Raspberry Pi 0 (zero):
@bhepler
I can’t seem to start MM with npm startThats what I expected for the Pi Zero. Did you try the method described in the first post of this thread in the section “Setting up boot scripts”?
-
I took everything back with the first post everything works !!!