Home Assistant users cannot tailor backup policies per destination
Home Assistant users with multiple backup locations want different schedules, retention counts, and backup contents for each one. When the built-in controls apply policies uniformly, users report manually deleting files, adjusting schedules around unavailable NAS devices, and waiting for the next backup to see whether a failure has cleared. The strongest evidence is for Home Assistant; other signals describe separate backup-tool needs.
For home Assistant self-hosters with multiple backup destinations. Mentioned from Oct 2023 to Jan 2026 on Bluesky, product forums and Stack Exchange.
17 different people described this problem in 13 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.5/10
- Frequency
- 10.0/10
- Willingness to pay
- 2.2/10
- Momentum
- 5.0/10
- Who pays
- Consumers
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I now have to manually delete OneDrive backups in order for Home Assistant to be able to write new ones if quota is reached. It has no way of organizing itself around quota limits
My problem: the full backup is ~4.x GB (because of InfluxDB → 3.7 GB) Additionally I would appreciate a solution to be able to do dayly a backup WITHOUT influxDB , and weekly a backup WITH influxDB and somehow be able to make use of the backup retention by keeping last few days but also last weekly full backup
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 18 more quotes from people who have this problem
- Current workarounds, existing solutions and risks