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

SebTota

@Hawking My MagicMirror has been sitting for a long time. When I recently finished the frame to get the computer display and rpi zero out of my closet I booted the rpi zero and on the top of the display it said A New Version of Magic Mirror is available or something along those lines. So I went into the MagicMirror folder and used the command “git pull && npm install” as specified in the README file of MagicMirror.

Hawking

@SebTota said in How I got my Magic Mirror working on a Raspberry Pi 0 (zero):

git pull && npm install

Have there been errors when you did so?

I got

npm WARN lifecycle magicmirror@2.1.1~install: cannot run in wd %s %s (wd=%s) magicmirror@2.1.1 cd vendor && npm install /home/me/MagicMirror

Thats why I then did

cd ~/MagicMirror/vendor && npm install

in addition (see my post above). Maybe this also solves your problem.

SebTota

@Hawking Sorry to keep bothering you but I ended up making it work with the two commands you told me to do. Now my problem is when the Pi Zero W is booting it connects to the WiFi but when magic mirror boots the pi disconnects.

Hawking

@SebTota
Just to make sure that I understand the problem correctly:
You see the MagicMirror on the screen (Clock running etc). but you can no longer connect to the Pi Zero (using eg. ssh)?

Just as a test:
What happens if you disable the MagicMirror from autostart (for example by moving the MagicMirror start script from /etc/init.d/ to your home directory) and start it manually while you are already logged in? I don’t know your exact setup or your Linux knowledge, if you need further help how to do this, just let me know.

SebTota

@Hawking I actually eventually got it working. Thanks so much for all your help!

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.