System Monitor

The systemmonitor sensor platform allows you to monitor disk usage, memory usage, CPU usage, and running processes.

To add this platform to your installation, add the following to your configuration.yaml file:

# Example configuration.yaml entry
  - platform: systemmonitor
      - type: disk_use_percent
        arg: /config
      - type: memory_free

Configuration Variables

resources list Required

Contains all entries to display.

type Required

The type of the information to display, please check the table below for details.

arg (Optional)

Argument to use, please check the table below for details.

The table contains types and their argument to use in your configuration.yaml file.

Type (type:) Argument (arg:) Argument mandatory
disk_use_percent Path, e.g., / no
disk_use Path, e.g., / no
disk_free Path, e.g., / no
network_in Interface, e.g., eth0 yes
network_out Interface, e.g., eth0 yes
throughput_network_in Interface, e.g., eth0 yes
throughput_network_out Interface, e.g., eth0 yes
packets_in Interface, e.g., eth0 yes
packets_out Interface, e.g., eth0 yes
ipv4_address Interface, e.g., eth0 yes
ipv6_address Interface, e.g., eth0 yes
process Binary, e.g., octave-cli yes

Disk usage

If no path is provided via the optional argument, the integration defaults to ‘/’ (root).

Note: The disk usage sensors do not support monitoring folder/directory sizes. Instead, it is only concerned with “disks” (more specifically mount points on Linux).

$ df -H
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        29G   12G   16G  42% /
devtmpfs        805M     0  805M   0% /dev
tmpfs           934M     0  934M   0% /dev/shm
/dev/mmcblk0p1  253M   54M  199M  22% /boot

Defining a disk_use sensor for / and /home/pi is redundant and will return the same values, since they both belong to the same “disk”. However, defining separate sensors for /dev and dev/shm is possible and provides different values, since those are treated as separate “disks” by the integration.

Processor temperature

  • If no hardware sensor data is available (e.g., because the integration runs in a virtualized environment), the sensor entity will not be created.
  • The unit of measurement (Celsius vs. Fahrenheit) will be chosen based on the system configuration.
  • Only the very first processor related hardware sensor is read, i.e., no individual core temperatures (even if the hardware sensor could provide that level of detail).

Linux specific

To retrieve all available network interfaces on a Linux System, execute the ifconfig command.

ifconfig -a | sed 's/[ \t].*//;/^$/d'

Windows specific

When running this platform on Microsoft Windows, Typically, the default interface would be called Local Area Connection, so your configuration might look like:

  - platform: systemmonitor
      - type: network_in
        arg: "Local Area Connection"

If you need to use some other interface, open a command line prompt and type ipconfig to list all interface names. For example a wireless connection output from ipconfig might look like:

Wireless LAN adapter Wireless Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Where the name is Wireless Network Connection.