Settings, reports and troubleshooting

Settings, reports and troubleshooting

Settings

Minimum temporary-file age

Determines how old a temporary file must be before it can be shown as a candidate.

Default: 30 days

Minimum log-file age

Determines how old a log file must be before it is classified as an old log.

Default: 14 days

Quarantine retention

Determines how long files remain recoverable in quarantine.

Range: 1–10 days
Default: 7 days

Advanced mode

Shows additional technical review information.

Enable this only when you are comfortable assessing file paths, integrations and recovery consequences.

Report retention

Determines how many complete report sets are retained locally.

Range: 1–50
Default: 10

Only files using Hass-Cleaner's own report naming structure are managed.

Interface language

Available options:

• Automatic
• English
• Nederlands

Automatic uses the Home Assistant or browser display language. Unsupported languages fall back to English.

A language selected inside Hass-Cleaner takes precedence over the App configuration.

Report formats

Markdown

Best for reading, manual review and sharing with support or testers.

CSV

Best for filtering and sorting large result sets in Excel or another spreadsheet application.

JSON

Contains the complete technical data for debugging, automation and development.

What to include in a bug report

Include:

• Hass-Cleaner version;
• Home Assistant version;
• system architecture;
• the action you attempted;
• the exact visible error;
• the Markdown report;
• the JSON report when technical detail is required;
• relevant Hass-Cleaner logs.

Always review reports before publishing them.

Common questions

An entity remains temporary

This is expected when it has only recently become unavailable or unknown.

Run additional scans across several days so Hass-Cleaner can build duration and comparison evidence.

A quarantined file no longer appears in scan results

Active quarantine files are excluded from normal scan candidates. After restoration, the file can be evaluated again during a later scan.

A removed entity returns

Many integrations recreate their registry entities while the device or configuration entry still exists.

Where possible, remove or correct the source through the integration's official configuration first.

Backup verification does not complete

Check that:

• Supervisor is available;
• Hass-Cleaner has the backup role;
• the backup has fully completed;
• the App was restarted after an update.

You may also confirm a recent backup yourself or consciously continue without one.

Clean start

The History page can clear local scan, measurement, plan, registry and Recorder logs.

Active quarantine files and required recovery information are not removed.

Report a problem

https://github.com/dkwolf1/Hass-Cleaner/issues