Recorder Retention Period By Entity

True. My bad. Forgot this was a FR… :frowning:

1 Like

I have half a mind to ditch some integrations and then re-add them but I don’t know if that would clear the data…

Removing entities does not delete entity history/statistics data (unless you do it manually)

This seems like a useful feature. There are many sensors that I want to retain for longer periods, like battery status, leak status, temperature, humidity.

I would also suggest the ability to toggle this at the device level, or even integration level. I have 1370 entities currently, and it would be a lot of work enabling them one by one. But of course this depends on the UI - if it allows filters & multiple selection, then it may not be as much of a problem.

Good point. If the UI could group, filter and/or sort them it would make things easier. Of course none of that can happen until the underlying database structure changes to support retention periods per entity.

In the mean time, a lot of people have found it’s easier to use include rather than exclude in their configuration for Recorder. If I knew then what I know now, I might have gone that route when setting up HA. Admittedly it’s still a very blunt instrument, and something like this FR would still be extremely helpful.

A very useful use-case for this functionality is for device_tracker/person entities: it will be possible to see a track on a map for some particular period in the past. Of course if period is defined by some “start” & “end” data, not by “hours_to_show”. Some custom map cards (like this great card) already have this method to define a period implemented.

I’d love to have retention period by entity, and also the ability to downsample it after that.