@juvesito If you are comfortable to go without destkop i would go that way.
Otherwise, both works.

@juvesito Go with Jessie.

Any pi except Raspberry Pi Zero.
Jessie is the way to go for autoinstaller.

Raspberry pi 3 is the fastest atm (and i would by that decider the best).

However, you will have a rough time in front of you if you see installing Magic Mirror by the manual process is a heartache.

@nobita As tbear said. Also make sure your PWK is set corect.

This is the part of the config we are talking about:

	apiKey: "YOUR API KEY",    // https://www.wunderground.com/weather/api  select the middle plan... 
	useAir: false,             // set to false if you do not want to use Air Quality Index
	airKey: "YOUR API KEY",    // IF you want Air Quality Index
	pws: "KNYELMIR13",         // go here to find your pws: https://www.wunderground.com/wundermap

You dont need the airKey if you have it set to false. You only need this if you want the Air-data.

https://forum.magicmirror.builders/topic/4684/electron-cpu

Please read this thread.

This post may help you after:
https://forum.magicmirror.builders/topic/4928/ghost-overlay-omxplayertransparency/27

@Reotch2
Sorry that it does not seem to work.
The only thing i can think about now is the read speed of your micro SD card.
In video editing playback often is limited due to read speeds of the drive.
But here we talk about 100MB+ per second. And that is an understatement.

I would try to see if you can get html video running from a embedded source such as Youtube.
Else, if you have not tried running OMXPlayer and the PIR module as “behind” in the config i have no idea.

Im interesting in following up this project in the future, when i run out of things to incorporate in my MM.

If you decide to not follow this up anymore i would love to see a summary post what you have up and running, including scripts and such. Also a summary of what did and did not work in your research

@Reotch2
I got helped with this yesterday from Mykle and i went from 80-100% cpu usage to 2-45% cpu usage.
The biggest difference was by downgrading electron to 1.4.15.
But running MM 2.1.0 instead of 2.1.2 also made a improvement.

How to downgrade electron
Navigate to your home folder, from here delete all maps including electron. there should be two:
.electron & .electron-glpyh.
Navigate to you node-modules inside MM.

§ cd ~/MagicMirror/node_modules

Uninstall electron by

§ sudo npm uninstall electron

install electron with desired version in this case 1.4.15 by:

§ sudo npm install electron@1.4.15

Now open file manager or navigate to “~/MagicMirror/node_modules/electron” and look in package.json
Here you can confirm your version number of electron.

How to downgrade MagicMirror
If you want to downgrade your MM version you will need to make a new install.
I would suggest everyone doing this to NOT delete it BEFORE you have made a backup.

You can find MM 2.1.0 here (thanks to Mykle for providing me with link):
https://github.com/MichMich/MagicMirror/archive/v2.1.0.zip.

Unpack the zip in you home folder, and rename it to MagicMirror
then just run npm install from the folder.

§ cd ~/MagicMirror/
§ npm install

Note: You will need to re-install electron 1.4.15 after the clean install of MM 2.1.0.
Make sure to have everything up and running before you do that.

I did run the gun and needed to redo everything twice.

@Reotch2
Is you other widgets also laggy chunky?
Im thinking about the transitions on the RSS module etc.

@Mykle1 Well… You cant understand how everything works right away!
I though i needed to copy all CSS from main to custom. So i made a local backup of the Main.css instead.

I now know better! lol

@cowboysdude No worries! I also added the missing part in the Swedish translation.
Anything else i can help with?