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?

@Natacha3
I also tested the motiondetector of alexyak, without success and therefore installed Motion, which works without problems. However, I understand, that the process to compile it for your self is not easy for a beginner.
Are you aware of https://forum.magicmirror.builders/topic/988/motion-detection-with-raspicam-non-module-version
The linked thread provides a precompiled version of Motion and some recommended settings.

@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 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
I still don’t understand what update you are referring to.
Both error messages sound like there are modules missing (either “express” or “colors”).

What happens if you do

cd ~/MagicMirror && sudo npm install
cd ~/MagicMirror/vendor && npm install

@SebTota

• Do you also get this error if you use a very minimal config file like

var config = {
        port: 8080,
        ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1"],
        language: "en",
        timeFormat: 24,
        units: "metric",
        modules: [
                {
                        module: "clock",
                        position: "top_left"
                },
        ]
};

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

If this works, you can step by step add the modules you want and see which one causes the problem.

• The exact error message would be helpful for an analysis.

@SebTota
Which updates are you referring to? I’m still using Raspbian Jessie Light (I didn’t use the image provided in this thread but my own installation and didn’t update so Stretch yet), which is up to date (according to sudo apt-get update && sudo apt-get upgrade) and the latest version of MagicMirror (according to cd ~/MagicMirror && sudo git pull) and don’t see any (new) issues on my Pi Zero W.

What are your problems?
`

@delusional112
I didn’t use the image but used my own installation. Therefore In can’t tell for sure. However,where ist the wpa_supplicant.conf you are referring to located? Did you use/create one directly on /boot? This should automatically be copied to the “normal” location and then automatically get deleted.

My wpa_suplicant.conf file looked like

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
ssid="NAMEOFNETWORK"
psk="WPA2KEY"
}

(of course you have put your network name and key in, but keep the quotation marks).
Which editor did you use (not that there is a problem with the line end or something similar)?

Once it worked, I replaced the clear text psk by a passphrase by using wpa_passphrase.

`

@jdahli1
Can you just execute /opt/vc/bin/tvservice --preferred to see if it is tvservice or chvt that does not respond?

Here https://news.screenly.io/how-to-automatically-turn-off-and-on-your-monitor-from-your-raspberry-pi-5f259f40cae5 also problems with turning the screen back on using tvservice are mentioned. Maybe the other methods mentioned in the article are worth a try. If they work you can simply change the commands used in ~/MagicMirror/modules/motiondetector/node_helper.js

@jdahli1
I don’t know this error, therefore the following two comments might be totally wrong:

The motion detector uses

/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chvt 7

to switch the monitor on. What happens if you execute this command manually while the observed problem occurs (I assume you can still login to the PI?). Then you might know weather it is a problem of the motion detection (and MMM) or if it is a more general problem. Maybe you even get additional error messages that help you to identify the problem

2. Do you know the HDMI-settings in /boot/config.txt ?
   Maybe it is worth to play around with hdmi_force_hotplug, hdmi_drive, hdmi_group and hdmi_mode . See the file and here https://raspberrypi.stackexchange.com/tags/config.txt/info for more information. Maybe the “AR” in your error stands for “aspect ratio”, this could be set explicitly be these parameters.

If somebody got this module to work on a Raspberry Pi Zero (using the Midori browser) I would be highly interested in how it was done!