MMM-Selfieshot has been updated.

• The rotateCountdown parameter will allow you to rotate just the countdown and “shoot message”.
• The rotatePreview parameter will allow you to rotate just the display of the selfie.
• The rotation parameter has been removed.

That looks a lot like what I had a few months ago. You can read more about it in this post.

My solution was to go away from the “fake” OpenGL driver and to set the desktop resolution to “monitor default” instead of the monitor resolution. I don’t know which of those two fixed it.

The OP message appears to be confined to the fonts of the mirror. At least, I don’t see anything else in there.

First, when posting error messages, please use the markdown features of the board. It helps with readability.

Second, I would try reinstalling the fonts for the mirror. I think this is how to do it without having to reinstall the entire mirror framework:

cd ~/MagicMirror/fonts
npm install

With luck, it will regenerate your fonts folder and fix whatever this error is.

@Stoffbeuteluwe - You probably can’t. The version of Electron on the Mac Mini can’t support the OpenGL used to create the globe graphic. It’s possible that you can update the version of Electron that you’re using to the latest version and that might make it work.

You can, however, configure your Mac Mini to open a browser in kiosk mode on boot and set the home page to http://localhost:8080. That will give you what you’re looking for with only a little more work & overhead.

@alborzs - other than the hard way, no. Remove all of the modules and then add them back one at a time with an eye on your CPU usage.

The other thing to double-check is to make sure that you have one of the OpenGL drivers active. The regular one or the fake one, it doesn’t really matter which. The non-OpenGL driver uses a lot of CPU time.

@j-ason said in Background Image question ~ EasyBack:

{
module: “MMM-EasyBack”,
position: “fullscreen_below”,
config: {
bgName: “Example.jpg”,
videoName: “”,
youTubeID: “”,
height: “1080px”,
width" “1920px”,
}

I think I found it. It should read width: "1920". You’re missing the : and have an extra ".

Can you ping from the Pi to your Windows box?

@JohnBachini - I suspect it’s Electron. IIRC, it doesn’t support hardware acceleration for graphics. So all of the animation is done by the CPU.

As a test, you can start your mirror in server only mode and then open the mirror interface in a web browser. Firefox, Chrome & Edge all support hardware acceleration. Chromium might. See if that affects CPU usage and your temperature.

@ashishtank - It has been my experience that shutting off the power without shutting down the Pi will corrupt the SD card after about 18 months of daily hard shutoffs. Rebuilding the SD card with a backup config is about a 45 minute process by this point, most of it just waiting for the npm install routine to finish.

I have a lot of Pi laying about due to work, so I usually have 3-6 unconfigured Buster installations on SD cards on my desk. Run the installation script, copy the config.js file from backup, do a whole bunch of git clone commands and I’m off & running again. SD cards are cheap. Easy enough to have a spare card for the mirror ready to go.

(If you were really paranoid, you could have the spare SD card taped to the inside of your mirror. Corrupted card? Shutdown, swap, boot. Rebuild corrupted card during your spare time)

The only information that is unique to my mirror is the module configuration. I just back up the config.js file whenever I make a change to the mirror configuration. If the mirror needs to be rebuilt, I can quickly build a slick Buster installation, SSH into the Pi, run the installation script, drop the backup config.js to the config folder and then do a half-dozen git clone commands.

Once the mirror is up & running, I can do the boring maintenance stuff (apt get update && apt get upgrade) and just let it run in the background.