Recorder.purge_entities all except of

Configuration
1

I want to make an automation to purge all entities except a few specific ones.
Is it possible to do it like this?

alias: Recorder bereinigen
description: ""
trigger:
  - platform: time
    at: "04:00:00"
condition: []
action:
  - action: recorder.purge_entities
    metadata: {}
    data:
      keep_days: 10
      domains: !sensor.pv_sensor_leistung_gesamt !sensor.battery_power_charging !sensor.battery_power_discharging
mode: single

I think with this example I have to specify every entity I want to purge.
Or is there a way to purge everything after 10 days and purge some specific after 265 days?

2

I have build this:

alias: Recorder bereinigen
description: ""
trigger:
  - platform: time
    at: "04:00:00"
condition: []
action:
  - action: recorder.purge_entities
    metadata: {}
    data:
      keep_days: 10
      domains: >-
        light switch cover climate number lock weather update fan script camera
        binary_sensor button media_player calendar automation update
      entity_globs: >-
        input_* sensor.sun_* *battery_level* *battery_state* *charger_type*
        *do_not_disturb_sensor* *high_accuracy_update_interval*
        *high_accuracy_mode* *audio_mode* *volume_level_ringer*
        sensor.knx_interface* sensor.watchman* sensor.picnic* todo.picnic*
        *browser*
mode: single

But it said : running_script: false

3

Is there a reason the existing long term statistics are not good enough for your use case? Thiose are a little less detailed, but should be sufficient for pretty much all regular uses.

4

Yes. For example I have to store person.mark for 1 Year. Is there another way to store this kind of entilies?

5

In other words… I have to understand where was Mark lets say at the 2.4.2024? Was he in the zone “work” or “home” and how many hours was he working at that day.

6

How many hours at some place is something that you can keep long term statistics of. If you crete a sensor to keep that count with state _class measurement, it would start creating long term stats.

A string with zone names is not possible afaik. A workaround could be to create a numerical sensor with 1 for home and 0 for not home, but that would be somewhat hacky.

7

OK, thank you.
I’ll give it a try. At the moment it is very handy to look for a specific day and have the exact time of joining and leaving. Also the visual presentation (Bar display) for searching is nice…

8

So, that was not as good as leaving the statistics in place.
Ill back at deleting unwanted entities, but failed.
Can someone tell me what’s wrong with this automation? It doesn’t delete anything.

alias: Recorder bereinigen
description: ""
triggers:
  - at: "04:00:00"
    trigger: time
conditions: []
actions:
  - action: recorder.purge_entities
    data:
      domains:
        - light
        - switch
        - cover
        - climate
        - number
        - lock
        - weather
        - update
        - fan
        - script
        - camera
        - binary_sensor
        - button
        - media_player
        - calendar
        - automation
        - update
      entity_globs:
        - input_*
        - sensor.sun_*
        - sensor.*battery_level*
        - sensor.*battery_state*
        - sensor.*charger_type*
        - sensor.*do_not_disturb_sensor*
        - sensor.*high_accuracy_update_interval*
        - sensor.*high_accuracy_mode*
        - sensor.*audio_mode*
        - sensor.*volume_level_ringer*
        - sensor.knx_interface*
        - sensor.watchman*
        - sensor.picnic*
        - todo.picnic*
        - sensor.name1*
        - sensor.name2*
        - sensor.*browser*
        - sensor.comfoairq_*
      keep_days: 10
mode: single