New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CPU Speed a little loads the CPU and raises temperature of the CPU #71388
Comments
cpuspeed documentation |
Hey there @fabaff, @frenck, mind taking a look at this issue as it has been labeled with an integration ( |
More load usually means higher temperatures. There are temperature peaks (approx. 63 °C) at 03.00 every day according the provided graphs. Your measures show also that the monitored CPU run between 43 °C and and 52 °C. I highly doubt that the |
Why then i don't see this behavior once |
The CPU Speed integration reads a single, local, file descriptor every 30 seconds. It is hard to accept such an action can cause any of the reported issues in this issue. Have you tried keeping the integration active, but disabling the updates? (for the sake of science). |
Can't reproduce the problem. I suggest waiting 1-2 days. |
I guess the root cause here is that |
Thanks |
The problem
The integration
CPU Speed
a little loads the CPU and raises temperature of the CPUI restarted the instance 2 times and delete the integration, after that the temperature of the CPU normalized.
I added the debug log for the integration, but nothing logged.
What version of Home Assistant Core has the issue?
core-2022.4.7
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
CPU Speed
Link to integration documentation on our website
https://www.home-assistant.io/integrations/cpuspeed/
Diagnostics information
config_entry-cpuspeed-9110886256fcc7b758944fe70a2a9e26.json.txt
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: