-
-
Notifications
You must be signed in to change notification settings - Fork 75
Bug: CPU usage percentage between HA and Windows don't match #368
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
Comments
Possible duplicate of LAB02-Research/HASS.Agent.Staging#16 as I cannot replicate this on build with LAB02-Research/HASS.Agent.Staging#16 |
If you can, please check the unofficial build release and try to replicate the issue https://github.com/amadeo-alex/HASS.Agent |
@SpartaTom @amadeo-alex were there any further findings on this? I have the exact same issue, as does a friend of mine. |
Does it happen on the original or the fork (https://github.com/hass-agent)? |
Happens on both |
I've recently installed hass.agent, and have the same issue. However, I had previously noticed that a HomeSeer script I have to monitor the same PC is showing the same values as I now see in hass.agent. Both hass.agent and the HS script show CPU usage values that are consistently about 1/6 of what Windows task manager shows. Coincidentally, it is a 6-core i7-8700 CPU. Related? |
I'm on the fork and I am seeing the same thing - HASS.Agent reporting CPU usage between 1-4% percent while Windows shows 20-25%. |
Describe the bug
The CPU usage percentage in Home Assistant doesn't match the CPU usage the windows taskmanager performance tab.
Home assistant gives me a value of 1-4%. Windows performance tells me it floats between 15-50%
To Reproduce
Expected behavior
I would expect the values to match.
At least more closely due to the 5 second refresh time.
Screenshots

Misc info (please complete the following information):
Please check what's applicable (multiple answers possible):
Additional context
MQTT broker is the mosquitto broker.
Multiple other sensors do match.
The text was updated successfully, but these errors were encountered: