From cf259596d1161d09a3fc4215683dded03399b1fd Mon Sep 17 00:00:00 2001 From: Karim Geiger Date: Sun, 16 Dec 2018 22:39:11 +0100 Subject: [PATCH] Add note for purge service to explain behaviour (#7874) I recently thought my purge service did not work since there still were some entries in my database having a younger date than specified by the purge. It took me quite a while to find an answer as to why that is, so I thought adding a note to the documentation wouldn't hurt. Source: https://community.home-assistant.io/t/recorder-does-not-purge/70077/2 --- source/_components/recorder.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_components/recorder.markdown b/source/_components/recorder.markdown index c9ba56e1b97..4a20ef3f296 100644 --- a/source/_components/recorder.markdown +++ b/source/_components/recorder.markdown @@ -131,6 +131,10 @@ Call the service `recorder.purge` to start a purge task which deletes events and | `keep_days` | yes | The number of history days to keep in recorder database (defaults to the component `purge_keep_days` configuration) | `repack` | yes | Rewrite the entire database, possibly saving some disk space. Only supported for SQLite and requires at least as much disk space free as the database currently uses. +

+Purging does not necessarily remove all entries before a given date. For example, to be able to recover after startup, the last known state for each entry is never purged. This is true even if the entry is already removed from your configuration. +

+ ## {% linkable_title Custom database engines %} | Database engine | `db_url` |