How I got my Magic Mirror working on a Raspberry Pi 0 (zero)

hoggboss22

Hello everyone.

I’ve followed the instructions and did everything in the comments (all 12 pages) to make sure I am doing them right. I was able to see MM2 thru the browser but on my screen, it is showing white screen.

Loading config ...
Loading module helpers ...
No helper found for module: alert.
Initializing new module helper ...
Module helper loaded: updatenotification
No helper found for module: clock.
Initializing new module helper ...
Module helper loaded: calendar
No helper found for module: compliments.
No helper found for module: currentweather.
No helper found for module: weatherforecast.
Initializing new module helper ...
Module helper loaded: newsfeed
All module helpers loaded.
Starting server on port 8080 ... 
Server started ...
Connecting socket for: updatenotification
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: newsfeed
Starting module: newsfeed
Sockets connected & modules started ...

Ready to go! Please point your browser to: http://localhost:8080
Whoops! There was an uncaught exception...
{ [Error: listen EADDRINUSE :::8080]
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '::',
  port: 8080 }
MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues

mind helping me out with this?

A Former User

@hoggboss22 your mm seems being excuted multiple. Common pitfal is that more than one browser are opened.(maybe your previous test running?)
Or your machine is already using port 8080.

Kill all browsers(and node or npm) and restart. Or change port in your config like 8088.

hoggboss22

I thought the same thing, i changed from 8080 to 9090 and it gave me the same error. I ran the net stat command to find the port being in used and guess what… there was nothing that is using 8080 or 9090

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN     
tcp6       0      0 [::]:tproxy             [::]:*                  LISTEN     
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN     
udp        0      0 0.0.0.0:mdns            0.0.0.0:*                          
udp        0      0 0.0.0.0:49645           0.0.0.0:*                          
udp        0      0 0.0.0.0:bootpc          0.0.0.0:*                          
udp6       0      0 [::]:mdns               [::]:*                             
udp6       0      0 [::]:44605              [::]:*                             
raw6       0      0 [::]:ipv6-icmp          [::]:*                  7          
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node   Path
unix  2      [ ACC ]     STREAM     LISTENING     7951     /var/run/dbus/system_bus_socket
unix  2      [ ACC ]     STREAM     LISTENING     7954     /var/run/avahi-daemon/socket
unix  2      [ ACC ]     STREAM     LISTENING     7957     /run/thd.socket
unix  2      [ ACC ]     STREAM     LISTENING     10463    @/tmp/.X11-unix/X0
unix  2      [ ACC ]     STREAM     LISTENING     5161     /run/systemd/fsck.progress
unix  2      [ ACC ]     STREAM     LISTENING     10321    /run/user/1000/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     10326    /run/user/1000/gnupg/S.gpg-agent
unix  2      [ ACC ]     STREAM     LISTENING     10329    /run/user/1000/bus
unix  2      [ ACC ]     STREAM     LISTENING     4967     /run/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     10331    /run/user/1000/gnupg/S.gpg-agent.browser
unix  2      [ ACC ]     STREAM     LISTENING     10363    /run/user/1000/gnupg/S.gpg-agent.ssh
unix  2      [ ACC ]     STREAM     LISTENING     10365    /run/user/1000/gnupg/S.gpg-agent.extra
unix  2      [ ACC ]     STREAM     LISTENING     8845     /var/run/dhcpcd.sock
unix  2      [ ACC ]     STREAM     LISTENING     5005     /run/systemd/journal/stdout
unix  2      [ ACC ]     STREAM     LISTENING     8847     /var/run/dhcpcd.unpriv.sock
unix  2      [ ACC ]     SEQPACKET  LISTENING     5325     /run/udev/control
unix  2      [ ACC ]     STREAM     LISTENING     10464    /tmp/.X11-unix/X0

12wsx

Hello:) I have similar problem. Magic Mirror installed from image downloaded from this thread. Installed on piZero. Working ok. On screen there was a message to update. I did this and now MM not working. Try config with only clock. Not help.
Full update log.

 Starting MagicMirror: v2.1.0
Loading config ...
Loading module helpers ...
No helper found for module: clock.
All module helpers loaded.
Starting server op port 8080 ...
Server started ...
Sockets connected & modules started ...

Ready to go! Please point your browser to: http://localhost:8080
Whoops! There was an uncaught exception...
{ [Error: listen EADDRINUSE :::8080]
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '::',
  port: 8080 }
MagicMirror will not quit, but it might be a good idea to check why this happene                                                                                                                     d. Maybe no internet connection?
If you think this really is an issue, please open an issue on GitHub: https://gi                                                                                                                     thub.com/MichMich/MagicMirror/issues

(EE)
Fatal server error:
(EE) Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.
(EE)
(EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
(EE)
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 7 requests (7 known processed) with 0 events remaining.
pi@raspberrypi:~ $ ^C
pi@raspberrypi:~ $ sudo su
root@raspberrypi:/home/pi# cd ~/MagicMirror && sudo npm install
bash: cd: /root/MagicMirror: No such file or directory
root@raspberrypi:/home/pi# cd MagicMirror
root@raspberrypi:/home/pi/MagicMirror# sudo npm install
npm WARN peerDependencies The peer dependency stylelint@^8.0.0 included from stylelint-config-standard will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency stylelint@^8.0.0 included from stylelint-config-recommended will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency stylelint@^8.0.0 included from grunt-stylelint will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm ERR! Linux 4.4.34+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package stylelint@7.7.1 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer grunt-stylelint@0.9.0 wants stylelint@^8.0.0
npm ERR! peerinvalid Peer stylelint-config-standard@17.0.0 wants stylelint@^8.0.0

npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/MagicMirror/npm-debug.log
root@raspberrypi:/home/pi/MagicMirror# vendor && npm install
bash: vendor: command not found
root@raspberrypi:/home/pi/MagicMirror#

A Former User

@12wsx
Sometimes, this error seems to happen when MM is terminated abnormally. (I don’t know what is normal termination. :D)
In my case, execution npm for debug or test after first normal pm2 bootup makes this error.(Of course, before npm start dev I stopped pm2 process.)
For the solution, I change port from 8080 to 8081 or from 8081 to 8080(when I meet this problem again). It seems that after some minutes the port is freed automatically(or by execution with port changed.). And fortunately for me, first execution of MM(by pm2 on bootup) is always a success. So… I stop caring about this.

12wsx

my I please someone to make an image of sd card with installed and working MM? i’m trying about week to run MM on piZero and nothing… all the time diffrent errors which i don’t understand.

psteimann

@12wsx Change the Port from 8080 to 8099 and then try again…solved a lot of problems for me…

Hawking

After some weeks with the MagicMirror running, my SD card got corrupted and I decided to reinstall the system from scratch. I switched from “Jessie Light” to “Stretch light”, used node 6.11.4 and of course the latest MagicMirror 2.1.3.

I can access the MM from the browser of my laptop, but Midori only shows a white page. Even for a very simple config file:

var config = {
        address: "",
        port: 8080,
        ipWhitelist: ["192.168.2.185", "127.0.0.1", "::ffff:127.0.0.1", "::1"],
        language: "en",
        units: "metric",
        modules: [
        {
                module: "helloworld",
                position: "bottom_bar",
                config: {
                        text: "Hello world!"
                }
        }
        ]

};

/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== "undefined") {module.exports = config;}

The start of MM gives no error

Starting MagicMirror: v2.1.3
Loading config ...
Loading module helpers ...
No helper found for module: helloworld.
All module helpers loaded.
Starting server on port 8080 ...
Server started ...
Sockets connected & modules started ...

Ready to go! Please point your browser to: http://localhost:8080

and if I change from

midori -e Fullscreen -a http://localhost:8080

to

midori -e Fullscreen -a http://www.google.de

I see the google page. So Midori itself and the output on screen seems working as well.

Is anybody having an idea where to search for the error?
Is anybody using MagicMirror 2.1.3 on its Pi Zero?

Doubleve

@Hawking same problem rpi 1

noorm91

This post is deleted!

12wsx

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

Doubleve

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! enoent

npm 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

Doubleve

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 ]

Hawking

@Doubleve
In which directory did you execute npm 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 :-/

Doubleve

as you said I was not in the right record.
I had an error with the libnss3 library. Now more error

DISPLAY =: 0 npm start

magicmirror@2.1.3 start / home / pi / MagicMirror
sh run-start.sh

pi @ raspberrypi ~ / MagicMirror $ npm run config: check

magicmirror@2.1.3 config: check / home / pi / MagicMirror
node tests / configs / check_config.js

Checking file … /home/pi/MagicMirror/config/config.js
Your configuration file not containt syntax error :)

but it still does not work with midori

noorm91

What does npm start do in /MagicMirror

bhepler

@noorm91 npm start is the command to start the Magic Mirror application and display the interface on the screen.

noorm91

@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 start

pi@raspberrypi:~/MagicMirror $
pi@raspberrypi:~/MagicMirror $ npm start

magicmirror@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

Hawking

@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 start

Thats 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”?

Doubleve

I took everything back with the first post everything works !!!