@kurt

If you want to start the process with npm start then you have to do that inside ~/MagicMirror
However if you want to use pm2 then I would advise following the instructions again: https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror

pm2 seems to be working fine on your raspberry, so I would start here:

---

Make a MagicMirror start script. To use PM2 in combination with MagicMirror, we need to make a simple shell script. Preferable, we put this script outside the MagicMirror folder to make sure it won’t give us any issues if we want to upgrade the mirror.

cd ~
nano mm.sh

Add the following lines:

cd ~/MagicMirror
DISPLAY=:0 npm start

Save and close, using the commands CTRL-O and CTRL-X. Now make sure the shell script is executable bij performing the following command:

chmod +x mm.sh

You are now ready to the MagicMirror using this script using PM2.

please run npm list, which electron version are you running?

If it is 1.4 then please run

npm rebuild --runtime=electron --target=1.4.0 --disturl=https://atom.io/download/atom-shell --build-from-source

@Leotrap said in Sorry for this...:

Hi @bhepler thanks for the answering… so as i can see if i dont have the Pi i cant check if its working,isnt it? Thanks again

Of course you can. Just install node.js on your windows machine, clone the magicmirror package, install it and start developing. There is an instruction here: https://forum.magicmirror.builders/topic/548/building-mirror-without-programing/2

I installed it some days ago on a spare windows 7 laptop without any issues.
The only thing you can’t do is accessing GPIO ports … of course, because your windows machine does not have these.

bhelper’s answer to question 3 was to access your mirror once your raspberry is running.

I broke down the list to make it more compact

#	username	sizes (m)	area (m²)	location	additional comments	pickup/delivery
01	yawns	~ 0.8 * 0.8	~ 0.64	Germany, Cologne	polished edges	delivery
02	gustav1976	0.6 * 1.8	1.08	Germany, Koblenz	polished edges	?
03	gustav1976	1.0 * 1.2	1.20	Germany, Koblenz	polished edges	?
04	gustav1976	1.4 * 0.8	1.12	Germany, Koblenz	polished edges	?
05
06
07
08
09
10

@Andrius-ok
position should be fullscreen_above or fullscreen_below

@tbbear said in MMM-NOAA - Another Weather Module:

@Johans OK, so let me check what is possible
(by the way u must have a very sensible skin to feel decimals … only joking)

MMM-NOAA.js starting line 310. Math.round() is used which rounds up or down and eliminates decimals.
Maybe you could add a config option to specify number of decimals?

I see several formatting errors (missing , and too many } ). I did not test it, but please try this instead. Oh, and please remove your api keys and your personal calendar urls before posting the config file on the internet :)

{
	module: 'iFrame',
	position: 'bottom_bar', // This can be any of the regions.
	config: {
		// See 'Configuration options' for more information.
		url: "https://www.youtube.com/embed/6kgH6kqNuWM?list=PL24DEF584E7DBB4CF",
		width: "50px", // Optional. Default: 100%
		height: "50px", //Optional. Default: 100px
	}
},

@Stehman07
you need to edit the file as root, the normal user pi does not have sufficient rights.

Run sudo nano /boot/config.txt instead

Please try this in custom.css:

body {
  margin-top: 250px;
  margin-bottom: 250px;
  height: calc(100% - 500px); 
}

That should give a 250px margin from the top and the bottom and it should center the content on screen again. If you play with margin-top or margin-bottom values please adjust the height calculation.

@Mykle1 said in Hello-Lucy:

@yawns said in Hello-Lucy:

After show modules the screen is crowded.

SHOW MODULES by default will show ALL modules. So, if you have several pages employed it can get busy real fast. Still, it was intentional to have the ability to hide/show all modules, individual modules and pages of modules.

I see, thanks for clarification Mykle!