Recorder: separate purge_keep_days #4789
Unanswered
ewonais
asked this question in
Integration enhancements
Replies: 1 comment
|
🏷️ I've automatically added the |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Integration name
Recorder
Link to integration documentation on our website
https://www.home-assistant.io/integrations/recorder/
Describe the enhancement
Currently you can only set one purge_keep_days for everything, i would like separate options for entities with statistics (for there raw data not the statistics itself) and for those without. A minimum number of state changes to keep is an other solution, preferably both.
Use cases
In order to keep data for ententes without statistics for longer you are forced to keep raw data for everything for longer, this makes the database huge and also backups unmanageable big. Sins most entities without statistics changes less frequently, keeping a minimum number of changes (preferably in combination with separate purge_keep_days) lets you keep the data longer without making the database huge.
Anything else?
Increasing purge_keep_days and making an automation that runs recorder.purge_entities is almost a solution but currently not a practical one. The problem is that the sensor domain is huge and i want to purge all except a few. Currently i haw to list every entity i want to purge, using globs make it a little bit easier. Adding the ability to exclude entities/globs could make this a feasible solution.
All reactions