Electron CPU usage

Mykle1

Yes, I downgraded due to high CPU usage with MM2.1.1 & electron1.4.17. Top showed a usage between 100 and 200% and my own written moduls had a really bad performance.

Ok, thank you. I’m glad that you’re seeing the benefit of this workaround. Let’s hope that it gets addressed and corrected sometime in the future.

Kugelfang

@Mr.Sponti

I tried your precise instructions but my system still installed electron 1.7.9

i started with a fresh jessy install on my raspberry pi 3. i then installed the latest version of node.js and copied the MM 2.10 folder to my pi. I then modified the dependancy for electron to 1.4.15 in the package.json and run the installation. However i still ended up with electron 1.7.9 which runns really bad…

it would be great if someone could help me

Mykle1

@Kugelfang said in Electron CPU usage:

it would be great if someone could help me

npm install electron@1.4.15

Mr.Sponti

@Kugelfang said in Electron CPU usage:

I tried your precise instructions but my system still installed electron 1.7.9

cd $HOME/MagicMirror
npm uninstall -g electron
npm uninstall electron
npm install electron@1.4.15

Kugelfang

@Mykle1: that seems to have worked. I just entered the MagicMirror folder and ran the command! thanks a lot! the animations are a lot better now!

However, now i have another problem: it seems that the weather forecast module does not work. All other modules work as expected but the forecast does not show up. I double checked all the settings in the config.js and they seem ok.

@Mr-Sponti: thanks for the input but it seems that simply installing 1.4.15 over the 1.7.9 seems to have already working

Could it be that the weatherforecast plugin comming with MM 2.10 is the problem?

Mykle1

@Kugelfang said in Electron CPU usage:

Could it be that the weatherforecast plugin comming with MM 2.10 is the problem?

I don’t think so. It’s more of an API key issue. The newer API keys are being rejected by the API source. You can search this forum. I don’t know if there is a fix. Or, try another weather module in the meantime

Kugelfang

That is odd, my current config.js was working with my API keys for both actual weather and weather forecast modules brilliantly with the most recent mm version (the slow one)

With 2.10/1.4.15 the actual weather module still works but the weather forecast modules simply does not show up on the screen although it’s fully setup in the config file including the proper API key