Hi,
I didn’t find anything about this. Ever since I update to Home Assistant 2023.4.6 the CPU temperature of the RPi 4 CPU ist significantly higher.
Does anybody know why this happens?
Thanks
Nana
It looks like you have only updated a couple of hours ago.
Is it still higher after 24 hours (it may be doing some post-update optimisation etc)?
Sorry, should have used the newer screenshot:
as you can see it is still going on.
Assuming CPU load did not increase (because that would do it too) - maybe your cooler fan died?
It’s a passively cooled RPi4. The ambient temperature did not increase either.
The question is why would the cpu load suddenly increase after an update?
I’m running (docker) on a RPi4 2GB. I cannot see any noticeable increase in temp.
It may be a sign of something about to fail so make sure you have a current backup (just in case).
I am running HA Supervised on a RPI 4b 8 gig with a 1 TB SSD. I thought I noticed an increase in temperature as well, but hesistated in saying anything as I thought it might be transient as well, but looking back upon the last three weeks (when I have had very few changes except adding one sensor and a couple automation code tweaks), my graph does show a slight increase in temps as well:
I do run sudo apt update / sudo apt upgrade on the host via telnet outside of HA on a regular basis and also implement any updates to HA or HACS integrations/addons typically as soon as they are made available to me (no beta stuff).
This one might be pretty hard to chase down - thoughts?
Looking at the CPU load of the RPi I noticed that the load is at least 25% at all times which looks like one core is at full load which would explain the jump in temperature. I just don’t know how to find out what exactly causes the CPU load.
Update: after looking through all my addons I found out what is causing the load spike: Silicon Labs Multiprotocol (Version 1.1.1) from the skyconnect stick. No devices connected at the moment.
I have the same issue with a heated RPI. I have a active cooling on it which turns on at 50°C. For years it only run sporadically but now it’s on almost all the time.
I need to check the CPU activity but for sure the temperature is different
Ho much RAM and what kind and how much?
It seems this is happening not only on the pi.
Since recently, the average cpu usage of my hassio VM is stuck @ around 30-50%, used to be 10% on average, no real changes. and in the VM i cannot see any cpu being used, tried with the glances integrations, but can´t find anything.
Been testing integrations and addons. Now on to disabling default config stuff, have not found the issue yet.
4mb and 30% used. CPU average around 5-6%. It has spikes.
Temperature seems to be up by 10°C but the cooling in on all the time keeping it below 50°C
Mine seems to have settled down.
and my CPU has gotten much lower %, especially today (there were a bunch of debian updates just over the last few days, about 25 packages or so -
Later addition (May 1): Although I update/upgrade all the Debian packages on the host on a regular basis, I was surprised to see something like ~23 debian packages available this morning for upgrade. I bit the bullet and it made my installation unhealthy - docker cgroup v2 and systemd log issues. In my cleanup efforts I noticed the Home Assistant OS Agent is now 1.5.1 instead of 1.4.1, so I cleaned out/removed all the docker containers and a bunch of other packages before the required reinstalls - now back up and running and back to where I was before (same temperatures and percentages if not a little better than the graphs shown above).
Somehow mine is also back to normal. I can’t really say what caused it but its running like usual again.
Mine’s even better than it used to be (now something bad will happen… ugh!). The slight spikes around 7:05am every morning is an automated full backup. Since it is an RPI4B w/8 GIG of RAM running on a 1TB SSD, it used to crap out about once a week for no apparent reason which is normal these days on the RPI with HA evidently. I automated reboots as well with some widgets on a dashboard that allow me to set the day of the week and time for reboot. It has been running like clockwork ever since. I can’t believe how well it is running considering I have HA Supervised with maybe 200 sensors (about 250 automations) as well as daemons running on the host outside of HA transmitting weather data all over the world using weewx from an AmbientWeather WS-2902C weather station:
It’s typically running about 5% CPU:
and 105-107 degrees F:
System Information
| version | core-2023.5.2 |
|---|---|
| installation_type | Home Assistant Supervised |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.10.11 |
| os_name | Linux |
| os_version | 5.10.0-22-arm64 |
| arch | aarch64 |
| timezone | America/New_York |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 1.32.1 |
| Stage | running |
| Available Repositories | 1352 |
| Downloaded Repositories | 25 |
AccuWeather
| can_reach_server | ok |
|---|---|
| remaining_requests | 25 |
Home Assistant Cloud
| logged_in | false |
|---|---|
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Debian GNU/Linux 11 (bullseye) |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2023.04.1 |
| agent_version | 1.5.1 |
| docker_version | 23.0.6 |
| disk_total | 915.4 GB |
| disk_used | 14.9 GB |
| healthy | true |
| supported | true |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Duck DNS (1.15.0), Mosquitto broker (6.2.1), Samba share (10.0.1), AdGuard Home (4.8.6), Log Viewer (0.15.0), Home Assistant Google Drive Backup (0.110.4), File editor (5.6.0), Terminal & SSH (9.7.0), Core DNS Override (0.1.1), Studio Code Server (5.5.7) |
Dashboards
| dashboards | 5 |
|---|---|
| resources | 17 |
| views | 30 |
| mode | storage |
Recorder
| oldest_recorder_run | April 10, 2023 at 8:52 PM |
|---|---|
| current_recorder_run | May 9, 2023 at 7:09 PM |
| estimated_db_size | 1283.50 MiB |
| database_engine | sqlite |
| database_version | 3.40.1 |
