I played around with this a bit. In the end, running omxplayer with a resized and rotated video was the way to go. Oh, and I re-edited a few videos together in order to provide a more seamless experience. I’ll see about capturing some video tomorrow and uploading it.

I used pm2 to manage a quick script to keep the video going in case of failure. Overall, I’m quite pleased. Now to do the same to my office mirror…

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.

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

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.

@fox Did you try reinstalling electron via the instructions given? ie, delete /home/pi/MagicMirror/node_modules/electron and reinstalling?

This should be close:

cd /home/pi/MagicMirror/node_modules
sudo rm -rf electron
cd ..
npm install electron@1.4.15

After that, I suspect a npm install and then npm start.

Please use the markdown features to make your code easier to read.

The name of the module must match the name of the Github project and (more importantly) the name of the directory where the module resides. Try module: “MMM-rainfc”,. Also, it looks like you closed the config of the rainfc module, but you didn’t close the module itself. So:

{
module: “MMM-rainfc”,
position: “top_right”,
header: “Rain forecast”,
config: {
lat: “52.525”,
lon: “5.71806”,
width: 200,
height: 150,
lineWidth: 2,
lineColor: “#e0ffe0”,
fillColor: “#e0ffe0”,
maxPower: 300,
rainText: "Tot: ",
noRainText: "Geen regen tot: ",
nrOfTimeLabels: 5 // advised values: 2-5
}  
},

In my experience, the technique used in the Complete Setup Tutorial no longer works as intended. In order to keep the mirror on all the time, I recommend the following:

• Install X-Screensaver by entering sudo apt-get install x-screensaver
• Turn off your MM briefly by clicking Alt-Q. (If you’re using PM2 to maintain the process, enter pm2 stop mm or whatever).
• Using a mouse, configure X-screensaver to not use a screensaver. I believe you can access the X-screensaver configuration interface by clicking on the Raspberry icon -> Preferences -> Screensaver. The drop-down to select the screensaver mode will have an option for “disable screen saver”.
• Close the configuration panel and then run your MagicMirror process normally.

Credit goes to @sgtwtf for this suggestion.

You can stop them all at once by entering pm2 stop all

Okay, a couple things. sono.sh is your script that starts your process. ~ is the shortcut to the pi user’s home directory, also known as /home/pi. In order to run scripts from the command line, you have to precede the script name with ./

So let’s take a moment to verify the state of your pi. Change to the home directory and pull up the file list with a couple switches to see if sonos.sh exits:

pi@raspi:~ $ cd ~
pi@raspi:~ $ ls -lh sonos.sh
-rwxr-xr-x 1 pi pi 26 April 15 11:50 sonos.sh

There will be some variation in your results. If you see the phrase “No such file or directory”, then the file does not exist at that location. Also, you may not have any “x” entries when you do see the file listed. If so, the file is not marked executable, so it won’t run. You can fix this by typing chmod +x sonos.sh

I’m a little unclear as to what commands exactly are in your sonos.sh file. Could you please enter cat sonos.sh and reply with the results?

Adding the script to pm2 is done by typing pm2 start sonos.sh. You can then verify that pm2 has picked it up by typing pm2 status all. That will give you a list of the processes that pm2 is controlling. You should see both your mm.sh process and your sonos.sh process.

Give that a go and report back to us.

@zdenek First, how big is your SD card?

Second, you can probably copy off the config.js file out of the /home/pi/MagicMirror/configure folder and then delete the entire /home/pi/MagicMirror folder. That should give you enough space to get your Pi back up & running.

Third, you can remove the applications that come with the Raspian operating system that aren’t necessary for the Magic Mirror to function with this command:
sudo apt-get remove --purge idle3 java-common libreoffice* minecraft-pi scratch nuscratch penguinspuzzle python-minecraftpi python3-minecraftpi smartsim sonic-pi wolfram-engine
Follow it up with the automated cleanup: sudo apt-get autoremove -y.

That should free up some space once you get your Pi booted again.