-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
Processor use shows 0% and 100% limits after updating to 2023.11 #103298
Comments
Interesting, I reported this in beta chat in discord, as I'm definitely seeing the same. |
what was the dev response on that? |
Just tried 2023.11.1. Still the same issue. |
I’m seeing the same. I had a random battery sensor show 100.0000000001% too so it makes me wonder if we got a round error or something. Just a guess though. |
Maybe this is related to some changes in psutil or its buffer in general? I couldn't see a direct trigger, but couldn't the behaviour be improved according the the psutil docs (it recommends to call the cpu_percent at least a 2nd time to get accurate results)?
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
still seeing this |
@Mariusthvdb still seeing exactly what and on which version? |
The faulty |
The drop to 0 has been fixed but I think perhaps that's not coming until next patch release. |
could you please explain why we see this from the mentioned update on, as this was never experienced before? Asking, because if you might believe we had these 100% before, I would have to state that was not the case. |
Regarding the However with the The frequency of the sensor is every 15s (I believe), could you try to change this to 20/30 or something to see what behavior we get? |
Not hindered by in depth knowledge of how this works, so I may be totally wrong. But if we have unexpected lows and unexpected highs in a time sampled measurement, then my first thought is that the 0 are points where measurements are missed, that are then counted later on at the unexpected highs. In that case, ignoring the 0's and keeping the highs would raise the average percentage, thus misrepresenting the situation. This combined with the fact the problem wasn't there before, and that it now only occurs in the hour after a reboot, makes me wonder how that can be. I understand that a reboot causes high cpu usage, but for an hour when there's no actual change to the system? If0's are expected from the measurement, then why do the 0's only happen in that first hour? Also, for what I've read 0 is expected only for the first measurement because there aren't any samples yet. But it's not something you'd ignore on a regular basis. I can imagine that cpu measurement is hard when the system is very busy, but it kind of defeats the purpose of cpu measurement if that is the case. And after an hour the 0's are gone, together with the highs. |
unknown is not unavailable |
I think the problem can be checked using this script:
Where: |
Or this automation that writes to the log:
|
Hi. So it's work in progress to get to the root cause of the issue and get a permanent fix in order to resolve it. No need to get more posts about reproducing the issue unless there is constructive proposals on how to fix the issue. Thanks |
So long story short A fix is coming (PR has been linked) which I hope can be managed and implemented shortly. |
Do I understand correctly that the fix was not included in the 2024.2.3 release?
|
As 2024.2.3 was released yesterday and this was fixed like an hour ago then yes, it was n't included. |
Thanks for fixing, now just wait for 24.3 |
@gjohansson-ST , I do believe the issues are gone! the 0% was already taken out but replaced with unknown. the latest pr was in Dev, which I just installed and have a look: the 100% peaks at startup are gone now too. (regular processor % also went down significantly, but that has to do with improvements elsewhere...) nice. |
The fix isn't coming until 2024.3 so at this point either turn the sensor off or ignore it. Nothing to do until next release to have this fixed. |
The problem
since release 2023.11 processor use is suddenly showing 0% and 100% limits, still trying to figure out if this is only in restarts, or also during runtime.
in my system this never happened before, and the card below was always showing the limits displaying an actual percentage.
If anything, this is really annoying when trying to show a card like
rendering that useless really.
Its seems a bug, because how can usage ever be 0%? The 100% is also unexplained, even upon restart.
What version of Home Assistant Core has the issue?
2023.11
What was the last working version of Home Assistant Core?
2023.10
What type of installation are you running?
Home Assistant OS
Integration causing the issue
system monitor
Link to integration documentation on our website
https://www.home-assistant.io/integrations/systemmonitor/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
https://community.home-assistant.io/t/2023-11-to-do-add-release-title/634647/168?u=mariusthvdb
https://community.home-assistant.io/t/2023-11-to-do-add-release-title/634647/90
The text was updated successfully, but these errors were encountered: