I was about to go down the rabbit hole of installing two entirely separate instances in different folders, but using the environment variable for the config file is way cleaner. Managing them both with PM2 makes it so much easier to handle reboots too.

CX3 is definitely one of the most versatile modules, but getting the CSS right for those background images can be a bit of a rabbit hole! I’ve found that if the background image is too ‘busy,’ it completely kills the readability of the event symbols.
I’ve actually been using https://solidbg.com/ to quickly strip the backgrounds off custom icons or logos before I host them for my mirror. It’s way faster than manually editing PNGs when you just want a clean, transparent symbol that doesn’t clash with the CX3 ‘glance’ view.
Are you applying the background image to the .CX3 .event container specifically, or are you trying to do a full module background? Sometimes the z-index acts up depending on the position of other modules.

I was about to go down the rabbit hole of installing two entirely separate instances in different folders, but using the environment variable for the config file is way cleaner. Managing them both with PM2 makes it so much easier to handle reboots too.

Most of the older Google Fit modules broke when Google changed their API and authentication rules a few years back. MMM-GoogleFit (by amcolash) used to be the gold standard, and while it’s technically ‘archived,’ some people have had luck getting it to work by manually updating the dependencies. If you’re okay with a bit of a workaround, a lot of us have switched to using MMM-Withings if you have their scale/watch, or even MMM-Strava for activity tracking, as those seem to be better maintained lately!

That error is actually a ‘safety feature’ of the newer Raspberry Pi OS. Since they started protecting the system Python environment, you can’t just use pip install globally anymore. The easiest way around this is to use pipx. Try running these two commands-
sudo apt install pipx
pipx install mmpm

This installs MMPM in its own little ‘bubble’ so it doesn’t mess with the rest of your Pi’s system.

If MMM-SelfieShot is giving you trouble, you might want to look at MMM-TelegramBot or MMM-OpenCV. Most of the older camera modules struggle with the newer Pi camera drivers (libcamera), but OpenCV is much more flexible. For a university project, using the OpenCV module might even give you some extra ‘tech’ points since it can handle face detection too!

I was pulling my hair out trying to figure out why my modules weren’t loading. The npm run config:check tip is a total lifesaver - found a missing comma in two seconds.

Hey @bachoo786, I’ve been following your progress with the folder nesting—it’s a tricky bit of logic to get right in the node_helper, but it’ll be worth it for the cleaner UI!
One thing I noticed while setting up my own music module is that the player looks a lot better if the MP3 metadata (ID3 tags) is actually clean. If the tags are messy, the ‘Artist’ and ‘Title’ fields on the mirror usually end up looking like a jumble of underscores and file extensions.
Since you’re organizing a big library right now, I’ve been using https://editmp3tags.com/ to quickly fix the tags in the browser before dropping them into the music folder. It’s way faster than using a heavy desktop app and helps the module display everything correctly once you get that ‘better method’ logic sorted out.

Hey, I ran into a similar issue before — the popup didn’t appear even though the alarm triggered. In my case, it turned out to be a config issue with the notification settings in the module. Try checking if the showPopup option is enabled and that you don’t have another module overlapping it on the screen.

Also, while testing your setup, you can use something like onlinealarm.co
to verify your alarm times are correct before syncing it with MagicMirror — makes debugging way easier.