Sensor systemmonitor with cpu usage in percentage

Configuration
1

This is what I have in configuration.yaml

Sensor:
- platform: systemmonitor
resources:
- type: memory_use
- type: memory_use_percent
- type: memory_free
- type: load_1m
- type: load_5m
- type: load_15m
- type: last_boot

  - platform: template
    sensors:
      cpu_usage:
        friendly_name: "CPU Usage"
        unit_of_measurement: '%'
    value_template: "{{ states('sensor.load_1m') * 100 }}"

In lovelace, I have this card with the following codes:

entity: sensor.cpu_usage
name: CPU Usage
type: sensor
unit: '%'

It is giving me an “Unknown” value. Choosing the load_1m on its own without going thru the template I am getting the correct value, just not in the percentage value that I wanted.

Any ideas what I am doing wrong here?

Thanks much

2

Try it with

value_template: "{{ states('sensor.load_1m') | int * 100 }}"

The sensor returns the number as string.

3

I don’t think you want to multiply these values by 100 to get a percentage, its just not how they work. They can definitely go over a value of 1. See below for some basic info on what the values are reporting.

https://www.tecmint.com/understand-linux-load-averages-and-monitor-performance/

I think the value you are looking for is processor_use:

2 Likes
4

Aaaahhhh that’s why it shows an error there. Thanks for the tip. The value now return a value.

Thanks for that too. I looked up the link you indicated and yes it is not the right way to multiply this to get a percentage given the value may exceed 1.

I have now used the sensor processor_use as suggested. Works great for now.

Thanks again!

5

Why is this not working. It give me wrong values:
Hassio: https://n8970q34vnvidunh897qfc5wenh87v.tk/s/NCYJgdt5NxQyxjz/preview, https://n8970q34vnvidunh897qfc5wenh87v.tk/s/deAjTzj5y5LNd9f/preview
Proxmox: https://n8970q34vnvidunh897qfc5wenh87v.tk/s/ReYjDSnkZJHYYcD/preview
Thanks for help

6

Does anybody else have some strange peaks in their Processor Usage Graph?

grafik

But it seems to me it’s not the real value, because for the same minute there is another value which fits the average:

grafik

The check interval is one minute if not set to a different check interval I guess?

PS: I also have this behaviour in a custom_component and have addressed it there. But this is a direct integration, so maybe it has the same cause.