#Temp spikes

1 messages · Page 1 of 1 (latest)

stuck flame
#

It certainly looks like some kind of scheduled process - though whether it's HASS or not, hard to tell. I don't know the best way to trouble shoot this on Linux.

However, not solving the problem but maybe reducing the impact of this sort of thing, I just bought one of these cases: https://www.amazon.com.au/Raspberry-Metal-Passive-Cooling-Case/dp/B07WG4DW52 - It brought my idle temp from ~54c in the cupboard down to high 30s, and peak load is now in 40's instead of 65+. I know it doesn't solve the issue of what is causing this, but may make it more palatable for you when your pi runs at 100% utilization?

prime sigil
#

Your install method channel can help you with the tools available to troubleshoot

#

The Pi4 is known to run hot though, that's pretty normal

stuck flame
#

Yeah, I was surprised at how warm it got when I got mine a few weeks ago.

On tracking down the issue - actually you could look at something like Glances which you can install with python or in docker - you can have it log processes stats every minute or so to a CSV so later you can come back and analyze what is using the CPU

stuck flame
#

docker run -it -v /usr/you/glances/:/usr/log/ --network none docker.io/nicolargo/glances glances -t 60 --export-csv-file /usr/log/glances.csv I think will spit you out your stats including processes every 60 seconds to that CSV, no need to install anything (if you have docker already)

#

I did a little testing - I can't get it to run in detached mode unfortunately, so that would require you to leave your SSH session open - unless someone knows a little better than I do

wicked venture
#

I think I have found maybe what was the issue.
I have a Zwave network and recently migrated to Zwave JS from the deprecated one. I read on a reddit that you can use the zwave2mqtt addon to look at the network as this isn't in the JS option so I installed the addon for zwave2mqtt and Musquitto MQTT broker. Now since I"ve stopped these services my CPU degrees whent back down to normal. I think moving forward I will get these into a docker container on my NAS instead of the Pi4

#

either Musquitto or zwave2mqtt or both of these addons were the cause.

stuck flame
#

The case I suggested, or even getting a few heatsinks can make a significant different - TBH I suspect there is no issue running a Pi at 75c all the time anyway, sounds hot to us but chips are fairly resilient

wicked venture
#

I had a case with a fan on it but damn that sucker was on 24/7 and it was noisy as hell. Removed the case with the fan now only have heat sink and works great....I'll still put these addons on a docker container instead of the pi. But you're probably right. 75C isn't a big deal but for us mortal humans that's a lot

#

good feedback from everyone. Thanks for answering and theorizing with me.

stuck flame
#

The case I bought and shared - the case is actually pressed into a shape that it becomes a heatsink for the processor (cut in half here) - and yeah, dropped it by 20c by popping it into this case: https://m.media-amazon.com/images/I/61FtAh0TRBL._AC_SL1500_.jpg (obviously they have cut the top of the case in half to demonstrate here 🙂 )

#

Otherwise you can get little heatsink fins to stick on as well