@knubbl - It will be at your router. It depends on the brand, but this sort of thing is usually in the advanced menu.

… or you could follow the instructions in the post here.

@jeffreyking - We’re going to need a little more information than that.
Do you have any other modules working?
What behavior are you seeing?
What does the relevant portion of your config.js say?
What errors are showing up in your log files?

@duraturk - You seem to be well on your way. I honestly don’t think the monitor quality matters all that much for a normal Magic Mirror installation. And by “normal” I mean “using the standard white-on-black interface to display text” installation. Compliments, calendar, weather, newsfeed, plus some sort of transit schedule.

You might notice a difference in monitor quality if you plan on watching full screen video or high resolution photos of the Earth or some such. But I doubt it.

As for the size of the glass vs the size of your monitor, I think you have it right. The barely-bigger-than size will do just fine. Push comes to shove, you can remove the bezel from the monitor to reduce its size a little bit. Additionally, with a close fit you won’t have to worry about suspending or supporting your monitor behind the glass outside of the regular box that is the normal design. The “other components and cables” usually fit behind the monitor in the various gaps left by a flat wall up against a decidedly non-flat monitor case. In my experience, the depth necessary just to accommodate the monitor electronics is more than enough to fit the Pi and the power source.

I have shopped with TwoWayMirrors before and they provided excellent service.

@major - It looks like electron didn’t install properly.

If you run npm install from inside the /home/pi/MagicMirror folder, it should automatically install electron. If that doesn’t work, you can install electron specifically by typing sudo npm install electron@2.0.0

@postremalone - Could you provide some more information? Tell us what command you entered and specifically what messages you received. Remember to use the markup tags.

Very clever idea. Nice work.

@shazglass - Ah. Okay, easy enough.

You’re missing the mm.sh script. I’m not sure how you had this registered in pm2 earlier, but we can fix it. We’ll use nano to create a new mm.sh file:

cd ~
nano mm.sh

This will give you a blank screen with the nano options at the bottom. Enter the following lines:

cd ~/MagicMirror
DISPLAY=:0 npm start

When you’re done, hit ctl+o to save the file and then ctl+x to exit nano. Then just like you did earlier, make your script executable by entering chmod +x mm.sh

Before we go any further, we need to test your script. From the command line, enter ./mm.sh
Your mirror should start after 30 seconds or so. Try this and report back with any errors and behaviors. Also, please use the markup commands when posting code and logs (follow this link for a quick tutorial).

Excellent! I can finally get my mirror to respond to a particular swear word. It’s a literary reference. Honest.

@shazglass - Hmm. I don’t know. It should be working normally at this point. Let’s try switching to the previous process. We’ll delete the one that the installer created, then add the one to your script.

First, we remove the existing process:

cd ~
pm2 delete MagicMirror
pm2 save

Then we use your mm.sh script that you had earlier.

pm2 flush
pm2 start mm.sh
pm2 save

At this point, your mirror should come up in about 30 seconds. If it does not, enter pm2 log mm and copy the results here. Be sure to use the forum markup tools to help format your log messages.

After a day, the flashing effect seems to occur about an hour after mirror boot. So far, it has occurred twice. Rebooting the mirror seems to be the only way to fix it.

Stopping the MagicMirror process will drop me back to the desktop, but it will still have the graphical corruption.