I know this could be possible by way of scheduling automations but it would be very difficult to keep the recorder config and automations in sync. i.e when we add new entity in recorder yaml config, easy to forget to add it in respective automation.
Please elaborate why you need to add an entity to some automation right after “add new entity in recorder yaml config”.
Also, what is a meaning of that “add new entity in recorder yaml config” - is it about excluding this entity from Recorder or including?
thanks for your response. my understanding was that you can achieve what I requested (different keep_days for different entities/groups of entities/domains) by way of creating automations and manually creating recorder configuration specifying the includes. one automation for each keep_days along with the respective entities/groups/domains.
This should work but if I want to add a new entity to the recorder yaml config, I have to remember to add it in the respective automation to make sure it gets purged (or not). Over a period of time it gets cumbersome. also we don’t have easy visibility of which entities/groups/domains are in which automation (keep_days schedule).
If we have a way to specify different keep_days for each include (entity/domain/etc) in recorder yaml config, we don’t need manual automations.
I’ve been waiting for this feature for a long time. I hope this is the right time.