I get that with MMM-Carousel too - the difference is that MMM-Carousel takes care of it. I’m ASSuming that MM is initializing all the modules before they get a chance to get hidden, then when it repeats later, it’s a module updating while hidden, so it reshows.

Could be something else. usually for me, a black screen appears when I forgot to run the ‘npm i’ on a module somewhere…

There’s been modifications to everything involved in the MM2 process. Some things are left in the readme for older versions of software/OS/whatever just in case.

in his case, it was simply horrible config.js layout. Missing syntax all over the place.

cd ~/MagicMirror
npm run config:check
cd ~

Best script ever right there. I can’t express how important that is.

@dcarls91 Don’t give up.

Keep at it, you’re so close to having a working MM - a little self study and work and it’s done.

I’m aware there’s too many commas by ‘traditional thinking’ - but I kept getting config errors without it.

This was the default config, modified for testing.

I’m having an issue with MMM-Buttons.

Connecting a button like the image attached, and using the config attached, no matter how I press a button, I get the long press effect… can someone help me figure out what’s wrong?

Thanks!

{
			module: 'MMM-Buttons',
			config: {
				minShortPressTime: 0,
				maxShortPressTime: 1000,
				minLongPressTime: 1500,
				bounceTimeout: 1000,
				buttons: [
					{
					pin: 18,
					name: "test",
					longPress: {
						notification: "SHOW_ALERT",
						title: "title",
						message: "Long Press",
					},
					shortPress: undefined, 
				},
				]
			},
		}, 

One of the best commands to know is

 npm run config:check

Start at the topmost error and work your way down the file - it’s got lots of problems, but is easily fixed. Also, I highly recommend a graphical type editor if possible - Geany is what I use.

I installed samba on my magic mirror so I can edit with the PC version of Geany and save it right to the Pi. It’s great.

heh, whatever works. Just found it amusing. :)

Lower right hand corner, is that a set of headphones modified for use here?

I had a blank screen for the first time when I got home today. System had been running for a couple of weeks without an issue.

I’ve now added a cron job to restart every sunday…

@dazza120 Course, I can report the opposite, with my setup. While I don’t have exact figures the one thing that seems to have happened is that my system isn’t triggering the temp. icon anymore now that I’m back on the normal driver.

That being said, I’ve got a fan+heatsink on the way for the final setup, there’s no reason not to protect the pi.

No problem. The “adverse effect” is apparently more CPU use, but, as most MM projects are on single use Pi computers, there’s no issue IMO.

Actually, I’d be more interested in the mechanics in getting it to work down to the module level more than anything, would be nice to use it for say “Grabbing Attention” in a particular module…

So, you’re saying the NOAA weather app does rainbow colors for other modules?

… Okay.

@mykle1 doing what? I was referring to the original rainbow color. Would be cool to apply it to modules of choice.

Love the concept, actually. Would love to see it limited to the user’s choice of modules, however.

sudo Raspi-config 

Advanced Options -> GL Drivers -> Legacy.

“legacy” and “normal” drivers are the same thing.

I recommend in your custom.css file:

.MMM-RTSPStream .innerWrapper {
border: 0;
}

No more border. :)

Actually:

0 */2 * * * pm2 restart mm

https://crontab.guru/every-2-hours