-
Notifications
You must be signed in to change notification settings - Fork 0
Recorder and backups
Hass-Cleaner uses Home Assistant's official recorder.purge action.
Recorder stores historical states and events. The cleanup settings determine how much history remains available.
keep_days specifies how many days of Recorder history should remain.
For example, a value of 10 keeps the most recent ten days and makes older Recorder data eligible for removal.
Consider the history required by:
- dashboards;
- statistics;
- energy monitoring;
- long-term analysis;
- automations using recent history.
Repack attempts to rewrite the database to reclaim disk space.
It may:
- take a long time;
- temporarily require additional disk space;
- create additional database load.
Repack is disabled by default.
This option applies configured Recorder filters while performing the purge.
- Preferably create a full Home Assistant backup.
- Choose a suitable retention period.
- Leave repack disabled if uncertain.
- Review the summary.
- Enter the exact confirmation
PURGE. - Start the action.
- Check history, statistics and dashboards afterwards.
Recorder cleanup is separate from file quarantine and registry cleanup.
A scan does not require a backup.
Before a modifying action, Hass-Cleaner can offer:
- a Supervisor-verified full backup;
- confirmation of a recent backup checked by the user;
- consciously proceeding without a backup.
The chosen option is written to the audit log.
Hass-Cleaner starts and checks backups through the permitted Supervisor backup API.
Recent verified backup evidence can be reused for up to 24 hours.
A verified backup is strongly recommended but is not an absolute requirement. Continuing without one requires additional acknowledgement.