@umeeq - Looking at your info, the pm2 process is expecting to find the mm.sh file in the folder /home/pi

It’s this line: script path /home/pi/mm.sh

So move the script to that location.

mv /home/pi/MagicMirror/mm.sh /home/pi
chmod +x /home/pi/mm.sh

@pascal456 That looks awesome! Do you have a build log? Or pictures of the back? What are you using to attach the mirror to the monitor?

This reminds me of a joke.

Q: How many software engineers does it take to change a light bulb?
A: None. It’s a hardware problem.
Q: How many hardware engineers does it take to change a light bulb?
A: None. Just tell the software engineers to code around it.

@Calrus - I’m glad you got it working. In the future, please use the markdown features of the board when posting code.

Update for 2024!

• Latest version has a more robust image loading which should cut down on missing images.
• Implemented the overTime variable, which will allow you to override the calculated date & time for Santa’s trip. This is useful for testing beforehand.

Merry Christmas!

The upcoming wedding of a friend was the excuse I needed to build a mirror. Their decorating tastes are a bit more frilly than most, so I went with a different look than most mirror builders.

The UI is a bit plain, but because it’s a gift I don’t have access to schedule feeds, Instagram accounts, commutes, etc. After the wedding, I’ll talk to them and see if they want changes.

@moris The basic installation of MagicMirror includes a sample config.js file. It’s located at ~/MagicMirror/config/config.sample.js

If you copy or rename that file to config.js that should help get you started. cp ~/MagicMirror/config/config.sample/js ~/MagicMirror/config/config.js Once you have it copied, you can restart your mirror and it should use that simple config.js to run the mirror software.

Installing other modules is pretty simple. Navigate to the modules directory: cd ~/MagicMirror/modules and then clone the module repository git clone [module url]. Follow the directions at the GitHub repository for that module in case there is anything special about installing that module.

Okay, I have the weather integration working. I’ll spare you the process I went through to figure it out, but the short version is that I am a worse developer than I originally suspected. The remoteFile capability works by replacing the three compliment arrays (morning, afternoon & evening). The weather integration works (sensibly, IMHO) by adding weather-specific compliments to the existing arrays.

So in order to get them both working, you need to specify both the original arrays and the weather-specific arrays. You can delete any weather-specific arrays you wish, but you must have the morning, afternoon & evening arrays. Copy & paste this compliments.json file to your mirror and then modify accordingly.

{
  "morning": ["Morning compliment"],
  "afternoon": ["Afternoon compliment"],
  "evening": ["Evening compliment"],
  "day_sunny" : [
    "Day Sunny Compliment 1",
    "Day Sunny Compliment 2"
  ],
  "day_cloudy" : [
    "Day Cloudy Compliment 1",
    "Day Cloudy Compliment 2"
  ],
  "cloudy" : ["Cloud 1"],
  "cloudy_windy" : ["Cloud windy"],
  "showers" : ["Showers"],
  "rain" : ["Rain"],
  "thunderstorm" : ["Thunderstorm"],
  "snow" : ["Snow"],
  "fog" : ["Fog"],
  "night_clear" : ["Night clear"],
  "night_cloudy" : ["Night Cloudy"],
  "night_showers" : ["Night showers"],
  "night_rain" : ["Night Rain"],
  "night_thunderstorm" : ["Night thunderstorm"],
  "night_snow" : ["Night Snow"],
  "night_alt_cloudy_wind": ["Night Cloudy Winds"]
}

I’m going to work on this a bit and hopefully the next release of the MirrorMirror software will be a bit more friendly. As an aside, I’ve noticed that the weather integration technique continually adds to the arrays. So the memory usage will grow and grow at whatever frequency you set the compliment refresh. This isn’t terrible, as straight text doesn’t take a whole lot of memory. But it may have unintended effects if you leave your mirror running for months at a time or if you are expecting a true randomization of the compliments you enter.

@steed - You should not be modifying the compliments.js file. Any compliments you wish to insert into the module should be specified in the config.js file. In your case, you want to modify the config.js file to point to your large compliments JSON file.

Roughly:

{
	module: "compliments",
	position: "lower_third",	
	config: {
		remoteFile:'/home/pi/bookCompliments.json'
	}
}

Thank you for the inspiration. At the moment, this is a work in progress.

It’s a very basic implementation of planetary.js. But it seems to be a mature framework.