One more data point: The Pi behind my office mirror was doing okay, until I enabled the MMM-Snow module. Short version is that I had to downgrade Electron to 1.4.15 but now it’s running pretty well with 50 snowflakes.

@Vauxdvihl Can’t you just specify 1 as the daily count?

@heed Double check to make sure your internet connection is up & running. Without a working internet connection, the script and packages will not install.

Easy check: Enter curl www.espn.com and look for a wall of HTML text. If you get a bunch of junk it works. If not, you need to troubleshoot your internet connection.

@Mykle1 At work we use both Pi and Debian for our software. We’ve found that while Debian works, it’s just different enough to present several annoyances. The paths for common Linux features are different and some commands are just not present. These are not insurmountable problems, but they do present extra hurdles for the development team.

In short: You can probably do it, but expect to spend some extra time on it.

@dam4 What the hell… ls is the “list” command. It should only show you the listing for the file, including dates and permissions. But it’s… executing.

Just to be sure: pm2 shows two separate processes when you type pm2 status, correct?

If you’re not terribly wedded to Windows, I would recommend Ubuntu. For two significant reasons:

1. Boot times will be faster.
2. The various threads here in the forum include paths to software installations to help troubleshoot. These paths will be much closer to your environment in Ubuntu than they will be using Windows.

@dam4 Hmm. It sounds like a permissions issue. IIRC, you installed motion with sudo. It’s possible that the pm2 process doesn’t have rights to the motion folder.

If you enter ls -ah /home/pi/motion, what does that return?

@jasonarends Have you tested your Pi camera to make sure it is properly connected and the Pi is aware of the camera? Have you enabled the camera via the Pi configuration interface?

@AnduriI If you’re worried about overhead and other useless applications on your Pi, the Complete Setup Tutorial has a useful command to uninstall a lot of the stuff you won’t use in a normal Raspbian image. It will pull out the Wolfram engine, LibreOffice, Minecraft, etc.

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

@AnduriI It should be. The motion system will operate independently of the mirror and only controls the signal running down the HDMI cable to the monitor. The Pi camera and the Magic Mirror process are still running.

If you create a simple python script to control the pinouts on the Pi, you should be able to switch on some simple LED lights to illuminate the front of the mirror.

@fischi87 Not entirely. They still have to get through your router. You should be okay.

First thing to try in my opinion is to make sure you have the whitelist format configured properly. User another computer, phone or whatever and add its IP address to the white list. Use it to connect to the mirror and make sure you can see the interface.

Once you’re sure you can correctly modify the whitelist, add the router’s IP address. Then configure your router to forward a port (any port will do) to the IP address of the mirror. This will vary by router brand, but with a little research you should be able to figure it out.

At that point, use a computer NOT on your network to hit your router’s external ip address at the port you specified. For example, if your router has received an external IP address of 104.236.171.165, you would want to use a computer outside your network and go to http://104.236.171.165:675 (or whatever port you had set up to forward to your mirror).

@axellejamous I want to verify a couple of things, just to be sure.

1. You’re running npm start on the Pi itself, not via an SSH connection from another computer.
2. Your monitor is hooked up to the Pi via the HDMI port.

@aayush447 Serveronly is included with the MagicMirror framework. What it does is skip displaying the interface on the Raspberry Pi via Electron and the HDMI video output. You can still see the interface by pointing a web browser (especially the browser included with the Raspberry Pi operating system) at the Pi. But the Pi itself will still display the desktop and/or command prompt.

This is especially useful for people who remote in to their Pi for development, multiple displays or remote access. For example, you could have one Pi run the MagicMirror framework and have a mirror in your bathroom, a display in your kitchen and a display in your man cave all showing the same output of the Pi.

I use node serveronly during my development on my office PC. It lets me use a web browser to view the interface, which I can resize, move to a different monitor, etc. Otherwise, Electron would take over one entire monitor to display the output of the Magic Mirror framework.

@fischi87 Right. According to the Github page for MagicMirror2, you can control which IP addresses the mirror will authorize (the Whitelist). What’s actually happening is that when some computer makes an attempt to connect to the web server that the Mirror is running, the MagicMirror2 framework consults the IP Whitelist configuration and determines if the IP address of the computer making the call falls within the settings. If it is, then server will return the MagicMirror2 interface (what you normally see on your mirror). If not, then you get the Unauthorized message. This includes the Raspberry Pi itself, which is why the IP address 127.0.0.1 is included in the Whitelist by default.

The default configuration is this:

var config = {
	ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:172.17.0.1"]
};

In order to authorize connections from outside of the mirror itself, you need to add more IP addresses to the Whitelist. The first thing I would try is to add the IP address of your router. So if your router exists at 192.168.1.1, you would change the Whitelist to read:

var config = {
	ipWhitelist: ["127.0.0.1", "192.168.1.1", "::ffff:127.0.0.1", "::1", "::ffff:172.17.0.1"]
};

Substitute the IP address of your router as appropriate. If that doesn’t work, you can just delete everything in between the [ and ] in the above code and open your Mirror up to any connection.

Video of the ghost in the mirror can be found here: https://youtu.be/6hb1N1tYcPc

As an aside, this morning I changed the command to omxplayer -p -o local --loop --alpha 85 boo.mp4 to cut the sound from the video file. It woke me up when the mirror switched on this morning at 5 AM.

@user_Stephan Double check to make sure you have an internet connection from your Pi. Once you’ve used Putty to get to the pi’s command line, try curl www.espn.com and see what comes back. You should get a mess of html text. If you do not, then you need to troubleshoot your Pi’s internet connection.

I haven’t run the install script in a good long while, so I don’t know how much text it throws at the screen. After you run it, do you have a folder at /home/pi/MagicMirror?

@fischi87 You’ll need to add the domain where your connection is originating in order for the mirror to authorize the connection. Either the IP address range where your company’s internet resides, or just open the mirror to accept all connections.

Hmm… I wonder if you can just add your router’s IP address to the list? That may be worth a try.