RPi 3B+ / high %CPU / high temp

Ebson

![CPU]()
![Proc]()

sdetweil

@Ebson what does it look like without MM started?

Ebson

)
I guess too many 3rd party modules ;/ I will try to look for the one that causes problems.

Ebson

Please discard my previous post. Here is some more detailed testing:

It looks like ‘Weather or Not’ and ‘DarkSky’ forecast cause some problems. I will try to play with update interval.

Anyway, like in here: old discussion, my %CPU with default modules look a bit higher than the one presented in old post.

Do you think that electron version has some influence?
Could someone else present own %CPU with default modules?

Mykle1

@Ebson said in RPi 3B+ / high %CPU / high temp:

'Weather or Not’

CPU usage and heat have arisen now and again. If you search the forum you’ll find lots to read and perhaps a solution. At times it has been the version of Pi and other times the version of electron.

Concerning MMM-WeatherOrNot: There are only 2 things that I can think of that might affect your Pi negatively.

An extremely low updateInternal. The default is updateInterval: 10 * 60 * 1000, (10 minutes)
The use of the animated icons option.

I would like to hear from others if they are having the same issue, whether with a low updateInterval or the animated icons.

Ebson

I used:

Weather or Not:
updateInterval: 60 * 60 * 1000,
icons: Climacons (no animation)
DarkSky:
useAnimatedIcons: false,
animateMainIconOnly: false,
updateInterval: 60,
requestDelay: 1000,
updateFadeSpeed: 2000
2x Newsfeed:
reloadInterval: 10*60*1000,
updateInterval: 15000,
animationSpeed: 0

and I ended up with:

I still need to consider adding fan but increasing intervals and turning off animation helped a lot
Maybe I will play also with some older electrons.

Thank you for your reply;)

Mykle1

@Ebson

Honestly, I don’t think a 60 minute updateInterval is necessary for WeatherOrNot.

DarkSky updateInterval is 60 ms??? (I don’t use that module). If that is miiliseconds it would certainly cause trouble.

Ebson

You are right. I will change it into 6h… or even longer.
There is written in DarkSky’s Documentation that the value should be given in minutes. I don’t really know how to check whether it is not a mistake in Doc. I will make some testing;)

Ebson

DarkSky:

  setInterval(function() {
    self.getData();
  }, self.config.updateInterval * 60 * 1000); //convert to milliseconds

So, value should be given in minutes in config file. Anyway, I will increase a value. BTW, it is also nice module for weather.

Mykle1

@Ebson said in RPi 3B+ / high %CPU / high temp:

Anyway, I will increase a value.

No, I meant that 60 minutes is more than adequate.

BTW, it is also nice module for weather.

I use a few of my own.