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

Hawking

@Doubleve
Can you tell me which Linux distribution (lsb_release -a), node version ( node -v ) and version of MM you are using?

delusional112

Hi guys, I saw someone asked before, isn’t there anyone who has a working image for MM2 on a Pi Zero. I tried a lot of things before, cant get it to work. Now, I don’t have a lot of time to experiment with it, school and work are killing me. My mirror is lying around, unused. Please help me out here,
Thanks!!

noorm91

@delusional112
Here is an image, it has a couple of errors that needs fixing but the magicmirror starts at least.
If you have any solutions please keep us informed…this image is made by Sebtota.
https://mega.nz/#!XlIU3QjI!QSdvAE3yXp1oMsdRGNte6lt4SncgvfozSDU7xhxtbbM

Here is the topic I found the image at.
https://forum.magicmirror.builders/topic/1183/how-i-got-my-magic-mirror-working-on-a-raspberry-pi-0-zero/85?page=9

noorm91

Any clue on what is trying to start and not functioning alright here?

Starting MagicMirror: v2.1.0
Loading config ...
Loading module helpers ...
No helper found for module: alert.
Initializing new module helper ...
No helper found for module: clock.
No helper found for module: compliments.
No helper found for module: currentweather.
No helper found for module: weatherforecast.
Initializing new module helper ...
All module helpers loaded.
Starting server op port 8080 ...
Server started ...
Connecting socket for: updatenotification
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

(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.

bhepler

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

Ready to go! Please point your browser to: http://localhost:8080
Whoops! There was an uncaught exception…
{ [Error: listen EADDRINUSE
:::
8080]

This usually means that you already have a process trying to serve up web pages on port 8080. In my experience, this happens when you do not terminate your previous attempt to run the MM process and start up another one. The new one also tries to serve up pages on port 8080 and you get that error.

You can use ps ax | grep node to see if node is running when you attempt to start your mirror. If it is, node is already serving up pages, so you will want to stop whatever process is running first. Alternately, if you are running a web server on port 8080 already, you can switch the port of the MM process in the config.js file.

MarWind

So did anyone get MM2 on a Pi Zero W with Raspian Stretch lite running?
Or is it better to stay with Jessie?

Hawking

@MarWind
I still didn’t get it to work using Midori in combination with Raspian Stretch Lite.
On this distribution, I could only get it to work using Epiphany or Chromium. However, their performance is much slower than Midori (which worked fine in Jessie Lite). I can’t tell if this is due to some general changes in Stretch or in the newer versions of Midori.

noorm91

How did you install Chromium on rpi 0 ?

MarWind

@hawking, thanks for your answer!

I’ll do some more testing:

*So my main issue will be now the update of mm2 :-(
I’m running an working image on the pi zero w with npm 2.14 and node 4.2.1 for month’s now.
But after updating MM2 last week with git pull && npm install it’s broken :-(*

Hawking

@noorm91
I simply did

sudo apt-get install chromium-browser

and the start is by

chromium-browser --incognito --kiosk http://localhost:8080

I don’t know if this is a new possibility in Stretch light or is also possible in Jessie Lite (I know that there were some issues in the past). However, as I said, the performance is slow and not stable (I see that the free amount of memory gets low and the system freezes every few hours). Therefore I would prefer to use still Midori, whoch worked fine for me in Jessie. However, using Midori with Stretch I simply get a black screen. I don’t know if this is due to an error in my installation, due to changes from Jessie to Stretch, due to changes in the Midori browser, due to changes in MM (I tried to install an older version, which didn’t help) or yet another reason.