Cpuspeed and systemmonitor sensors

Great! Can you share your config? Are you running Hassio?

yes, running hassio (followed your instructions to install :wink: config is pretty much as per the component as per here: https://www.home-assistant.io/components/sensor.systemmonitor/

- platform: systemmonitor
  resources:
  - type: processor_use
  - type: disk_use_percent
    arg: "/"
  - type: since_last_boot
  - type: memory_use_percent
  - type: network_in
    arg: eth0
  - type: network_out
    arg: eth0

image

1 Like

is the ifconfig command available in Hass.io commandline?

If so, that will tell you what the interfaces are, its likely eth0 isn’t correct.

yes it is and it confirmed eth0… but the values are still “unavailable” in the UI as per screenshot…

How did you install? Hass.io on top of what OS?

followed these steps: My steps to success for Hass.io on Intel NUC

Brilliant, working now with native Hassio on NUC. Thanks for the heads up. For network (LAN) data, use the following:

  - type: network_in
    arg: enp3s0
  - type: network_out
    arg: enp3s0
1 Like

Hi,

enp3s0 does not work for me either

running ip a i get:

13: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP

which is why I had eth0 initially, but that alsi did not work…

if you are running a Debian based distribution install the net-tools package then run ifconfig.

core-ssh:~# ifconfig
eth0      Link encap:Ethernet  HWaddr [redacted]
          inet addr:[redacted]  Bcast:0.0.0.0  Mask:255.255.254.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5042 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1553 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:609761 (595.4 KiB)  TX bytes:103004 (100.5 KiB)

This should work on your system:

- platform: systemmonitor
  resources: 
  - type: disk_free
    arg: /
  - type: memory_use_percent
  - type: processor_use
  - type: since_last_boot
  - type: network_in
    arg: eth0
  - type: network_out
    arg: eth0
1 Like

yes it Should but it doesen’t… :frowning:

How did you create that System Status card/panel?

Simply group the entities of the sensors

Sorry, but could you explain further what you mean? A code snipit would definitely help

Have a read through here: https://www.home-assistant.io/components/group/

Necro-post for anyone else looking for this information.

Naming for eth0 on NUCs has changed. On my system it is now:

- platform: systemmonitor
  resources:
  - type: throughput_network_in
    arg: enp2s0
  - type: throughput_network_out
    arg: enp2s0

More info here:

1 Like

Buster right?

Not sure. Hassio NUC image.

I am on a NUC / hassio / ubuntu installation.

For me the ff. config worked for the network part:

- platform: systemmonitor
  resources:
    - type: network_in
      arg: hassio
    - type: network_out
      arg: eno1

so eno1 or hassio is working either

you can check the ethernet adapters on a console of the host

ip a

or

ipconfig -a

the result looks like:

fregatte :grinning: :grinning: :grinning: