From cbfb5675644a7728205898fff924f0013519dfa8 Mon Sep 17 00:00:00 2001 From: pailloM <56462552+pailloM@users.noreply.github.com> Date: Mon, 10 Jan 2022 05:27:15 -0500 Subject: [PATCH] Add example for multiple disks usage (#21095) Co-authored-by: Franck Nijhof --- source/_integrations/systemmonitor.markdown | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/source/_integrations/systemmonitor.markdown b/source/_integrations/systemmonitor.markdown index 2282562a667..cf9602d24ce 100644 --- a/source/_integrations/systemmonitor.markdown +++ b/source/_integrations/systemmonitor.markdown @@ -90,6 +90,17 @@ tmpfs 934M 0 934M 0% /dev/shm 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. +```yaml +# Example configuration.yaml entry +sensor: + - platform: systemmonitor + resources: + - type: disk_use + arg: /dev + - type: disk_use + arg: /dev/shm +``` + ## 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.