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.