Open SpartaTom opened 11 months ago
Possible duplicate of https://github.com/LAB02-Research/HASS.Agent.Staging/pull/16 as I cannot replicate this on build with https://github.com/LAB02-Research/HASS.Agent.Staging/pull/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)?
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?
HASS.agent Sensor:
HomeSeer:
Windows Task Manager:
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.