From dd622430ce0c9a44949abf2ad531fef97ea4fc1e Mon Sep 17 00:00:00 2001 From: J <49540618+Tediore@users.noreply.github.com> Date: Fri, 16 Aug 2019 12:09:51 -0500 Subject: [PATCH] Add note about purge_keep_days (#10152) The purge_keep_days variable in the recorder component limits the max duration of a history stats sensor. This might not be clear to some users. --- source/_components/history_stats.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_components/history_stats.markdown b/source/_components/history_stats.markdown index fa23b01dd0f..68b05276c75 100644 --- a/source/_components/history_stats.markdown +++ b/source/_components/history_stats.markdown @@ -119,6 +119,12 @@ duration: minutes: 30 ``` +
+ + If the duration exceeds the number of days of history stored by the `recorder` component (`purge_keep_days`), the history statistics sensor will not have all the information it needs to look at the entire duration. For example, if `purge_keep_days` is set to 7, a history statistics sensor with a duration of 30 days will only report a value based on the last 7 days of history. + +
+ ### Examples Here are some examples of periods you could work with, and what to write in your `configuration.yaml`: