From 7e81bd430ea317e4431180549bbbeccdd0fd7518 Mon Sep 17 00:00:00 2001 From: Eddy G Date: Mon, 29 Nov 2021 09:01:43 -0500 Subject: [PATCH] Docs for "delta_values" option in utility_meter (#19018) --- source/_integrations/utility_meter.markdown | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/source/_integrations/utility_meter.markdown b/source/_integrations/utility_meter.markdown index 67575f28ab6..5028bc04454 100644 --- a/source/_integrations/utility_meter.markdown +++ b/source/_integrations/utility_meter.markdown @@ -58,6 +58,11 @@ cron: description: This option is *mutually exclusive* of `cycle` and `offset`. It provides an advanced method of defining when should the counter be reset. It follows common [crontab syntax](https://crontab.guru) but extended to support more advanced scheduling. See the [croniter](https://github.com/kiorky/croniter) library. required: true type: string +delta_values: + description: Set this to True if the source values are delta values since the last reading instead of absolute values. When this option is enabled, each new value received will be added as-is to the utility meter instead of adding the _difference_ between the new value and previous value. For example, you should enable this when the source sensor returns readings like "1", "0.5", "0.75" versus "1", "1.5", "2.25". + required: false + default: false + type: boolean net_consumption: description: Set this to True if you would like to treat the source as a net meter. This will allow your counter to go both positive and negative. required: false