-
Notifications
You must be signed in to change notification settings - Fork 0
Files and quarantine
Examples may include:
- inactive old log files;
- temporary Python bytecode;
- known rebuildable Home Assistant icon cache;
- recognised editor or operating-system remnants.
A safe classification is not the only protection. Every file is checked again immediately before execution.
These items need a decision from the user.
Examples may include:
- unknown cache directories;
- integration-specific temporary data;
- files produced by custom integrations;
- recordings, snapshots or personal media.
Hass-Cleaner provides advice but cannot determine the functional importance of every integration-specific file.
Protected items cannot be selected through Hass-Cleaner.
Examples include:
-
configuration.yaml; -
secrets.yaml; - Home Assistant databases;
-
.storage; - dashboards;
- automations, scripts and scenes;
- custom component source code;
- HACS and frontend files.
For supported JSON, YAML, text and code files, Hass-Cleaner can show a limited structural preview.
It may show:
- key names;
- counts;
- file type;
- general structure.
Passwords, tokens, API keys and raw secret values are not included.
Immediately before quarantine, Hass-Cleaner rechecks:
- exact path;
- current file type;
- current policy classification;
- protected scopes;
- file size;
- modification time;
- SHA-256 checksum.
If one item no longer matches the scan, the complete batch stops before the first file is moved.
Quarantine records:
- original path;
- file size;
- SHA-256 checksum;
- execution time;
- user;
- backup choice;
- expiry time.
Retention can be configured from 1 to 10 days.
Nothing is deleted automatically when retention expires. Permanent deletion remains a separate manual action.
The restore test verifies:
- that the quarantined file still exists;
- that it remains readable;
- that its checksum still matches;
- that its original path is considered safe.
The test does not restore the file.
To restore a file:
- Open Quarantine.
- Select Restore.
- Review the original path.
- Enter the requested confirmation.
- Confirm recovery.
Hass-Cleaner never overwrites an existing file. Recovery is blocked if a new file already exists at the original location.
Permanent deletion is available only after retention expires.
The checksum is verified again and the exact confirmation DELETE is required.
Permanent deletion cannot be undone.