-
-
Notifications
You must be signed in to change notification settings - Fork 4
Getting Started: Backup Restore
ChoreOps includes a sophisticated custom backup and recovery system that protects your data and makes recovery from mistakes simple and fast. This guide explains how to use these built-in data protection features.
Warning
Migrating from KidsChores? Start with Migration from KidsChores before using this backup/restore guide.
Tip
Few Home Assistant integrations provide this level of automated backup and one-click restore capability. We want your data to be protected and easy to recover.
ChoreOps stores all configuration and runtime data in a single file:
/config/.storage/choreops/choreops_data
This file contains EVERYTHING about your ChoreOps instance:
- All assignees, approvers/admins, and assignments
- All chores, rewards, badges, achievements, challenges
- All bonuses and penalties
- Current points balances
- Complete chore completion history
- Badge progress and achievement tracking
- System configuration
Because the data file is in the .storage/ directory, your normal Home Assistant backup processes automatically protect it:
- Home Assistant Cloud backups
- Manual Home Assistant backups (Settings → System → Backups)
- Backup add-ons (Google Drive Backup, etc.)
All ChoreOps data is included without any extra configuration needed.
ChoreOps creates automatic backups at critical points to protect against data loss:
| Trigger | When | Backup Tag | Example Filename |
|---|---|---|---|
| Home Assistant Restart | Every time HA restarts | _reset |
choreops_data_2025-12-19_03-51-10_reset |
| Before Upgrade | Before ChoreOps version upgrade | _pre-migration |
choreops_data_2026-01-07_02-58-35_pre-migration |
| Before Restore | Before restoring from backup | _recovery |
choreops_data_2026-01-15_16-56-11_recovery |
| Manual Backup | When you create a backup | _manual |
choreops_data_2025-12-31_00-11-17_manual |
All backup files are stored in /config/.storage/ alongside the main data file.
ChoreOps automatically manages backup files to prevent storage bloat.
Settings → Devices & Services → Integrations → ChoreOps → Configure → General Options
Maximum Backups to Retain: Set the number of backup files to keep (default: 5)
- Older backups are automatically deleted when the limit is reached
- Set to
0to disable automatic backups (not recommended) - Increase the count if you want more restore points
Note
All retained backups are also included in your normal Home Assistant backup processes, providing off-system protection.
Navigation: Settings → Devices & Services → Integrations → ChoreOps → Configure → General Options
- Find "Backup Actions" dropdown (below Maximum Backups to Retain)
- Select "Create backup now"
- Click Submit
A new backup file is created with the _manual tag and current timestamp.
When to create manual backups:
- Before making bulk changes (restructuring chores, changing point values)
- Before experimenting with new automation
- Before major system changes
- As a quick safety snapshot
Navigation: Same as above
- Find "Backup Actions" dropdown
- Select "Delete a backup"
- Choose which backup file to delete
- Confirm deletion
Navigation: Same as above
- Find "Backup Actions" dropdown
- Select "Restore from backup"
- Choose which backup file to restore from
- Confirm restore
The integration will:
- Create a
_recoverybackup of your current data (before overwriting) - Restore the selected backup
- Reload the integration with restored data
Diagnostics downloads provide a simple one-time backup method.
Settings → Devices & Services → Integrations → ChoreOps → ⋮ (three dots) → Download Diagnostics
This creates a JSON file like: config_entry-choreops-01KF1QESK1PATGSY0HJMJEJG61.json
The diagnostics file contains:
- Your complete ChoreOps data file
- System information
- Configuration details
Tip
Quick backup strategy: Download diagnostics whenever you want a snapshot. Store it somewhere safe (email it to yourself, save to cloud storage, etc.). You can restore from this file anytime.
You can restore directly from a diagnostics download file using the Paste JSON method (see below).
ChoreOps provides multiple ways to restore your data.
Best for: Quick recovery from recent changes
Steps: See Restore from Backup above
Best for: Restoring from diagnostics downloads or copied data files
When to use:
- Restoring from a diagnostics download
- Restoring from a backup file you copied elsewhere
- Migrating between Home Assistant instances
Steps:
-
Delete the ChoreOps integration (if currently installed)
- Settings → Devices & Services → Integrations → ChoreOps → Delete
- This is safe because you have the backup data
-
Re-add the integration
- Settings → Devices & Services → Add Integration → ChoreOps
-
Data Recovery Options dialog appears
-
Select "Paste JSON from data file or diagnostics"
-
Paste the JSON content:
- Copy entire contents from
choreops_databackup file, OR - Copy entire contents from diagnostics download file
- ChoreOps automatically detects which format and processes it correctly
- Copy entire contents from
-
Submit - Your complete ChoreOps instance is restored
Note
The paste JSON process automatically removes the diagnostics wrapper if present. You don't need to extract anything - just paste the entire file contents.
Best for: Recovering after deleting the integration
Steps:
-
Re-add the integration Settings → Devices & Services → Add Integration → ChoreOps
-
Data Recovery Options dialog appears
ChoreOps automatically detects existing data in
/config/.storage/:- If
choreops_datafile exists (your current/last production data), it appears as an option - All backup files (
choreops_data_YYYY-MM-DD_HH-MM-SS_*) appear in the dropdown
- If
-
Select which data to restore from:
- Choose the main
choreops_datafile to continue where you left off - Or choose a dated backup to restore from a specific point in time
- Choose the main
-
Submit - Integration restores from selected file
Understanding backup file naming helps you identify the right restore point:
choreops_data_YYYY-MM-DD_HH-MM-SS_TAG
Examples:
-
choreops_data_2025-12-31_00-11-17_manual- Manual backup created on Dec 31 at 12:11 AM -
choreops_data_2026-01-07_02-58-35_pre-migration- Automatic backup before v0.5.0 upgrade -
choreops_data_2026-01-15_16-56-11_recovery- Backup before restoring another backup
Tags:
-
_reset- Created on Home Assistant restart -
_pre-migration- Created before ChoreOps version upgrade -
_recovery- Created before restore operation -
_manual- Created by user via "Create backup now"
Check:
- Verify files exist:
/config/.storage/choreops_data_* - Ensure files follow naming pattern with date/time stamp
- Try refreshing the configuration page
Try:
- Check Home Assistant logs: Settings → System → Logs (search "choreops")
- Verify backup file is valid JSON (open in text editor, check structure)
- Try the Paste JSON method as alternative
- Report issue with log details if problem persists
If you have:
-
Home Assistant backup: Restore the full HA backup to recover
/config/.storage/ - Diagnostics download: Use Paste JSON method to restore
- No backups: You'll need to reconfigure ChoreOps from scratch
ChoreOps-specific recommendations:
- Adjust retention count based on your needs (General Options → Maximum Backups to Retain)
- Download diagnostics before major ChoreOps changes (bulk edits, point restructuring, testing automation)
- Create manual backups before experimenting (General Options → Backup Actions → Create backup now)
For overall backup strategy, follow standard Home Assistant best practices. ChoreOps data is automatically included in all normal backup methods.
Early versions had implementation issues that could corrupt data. Recovery was extremely difficult because there was no automated backup system.
The custom backup system ensures:
- ✅ Automatic protection at every critical point
- ✅ One-click restore from any backup
- ✅ Multiple restore methods for different scenarios
- ✅ Diagnostics-as-backup for portability
- ✅ No configuration needed - it just works
This level of data protection is rare in Home Assistant integrations and provides peace of mind that your family's chore tracking data is always safe and easily recoverable.
If you experience backup or restore issues:
- GitHub Issues - Report backup system bugs
When reporting issues, include:
- Home Assistant version
- ChoreOps version
- Steps that led to the problem
- Relevant log entries from Settings → System → Logs
🚀 Getting Started
- Home
- Installation
- Migration from KidsChores
- Quick Start
- Quick Start Scenarios
- Dashboard Generation
- Backup & Restore
⚙️ Configuration
- General Options
- Points
- Users
- Chores
- Rewards
- Badges - Overview
- Badges - Cumulative
- Badges - Periodic
- Achievements
- Challenges
- Notifications
🔧 Services
💡 Tips & Tricks
- Template Cookbook for Chores, Rewards, and Approvals
- Auto-Approve Chores
- Calendar Event Due Dates
- NFC Claim Workflow
- Overdue Penalty Automation
- Critical Overdue Alerts
📖 Advanced Topics
- Dashboard Integration
- Access Control
- Chores - Advanced
- Badge Cumulative - Advanced
- Badge Periodic - Advanced
📚 Technical Reference
- Points
- Users
- Entities & States
- Chores
- Badges
- Configuration Detail
- Dashboard Generation
- Notifications
- Weekly Activity Reports
👩🔧 Troubleshooting