-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AutoBackup not working on HA Core since HA 2025.1 #178
Comments
Additional Information: AutoBackup Failing on HA 2025.1I am experiencing the same issue as described in this thread after updating Home Assistant to version 2025.1.0. Below are the details of my setup and relevant error logs: System Information:
Error Details:During the backup process, the following error appears in the logs:
Additionally, the tracebacks indicate the following errors:
Full traceback details:
Steps to Reproduce:
Observations:
Request:Could you please investigate compatibility between the AutoBackup integration and the updated Home Assistant backup backend? Let me know if additional logs or configurations would help! Thank you for your support! |
I'd honestly question if we still need this custom integration with the overhaul of built-in backups. I have disabled it for now to experiment with what HA offers out of the box. |
What I miss tbh are events, that I use to send a command to shell to upload backups to the cloud. I suppose that until there's no alternatives, I would appreciate to have this custom integration working |
I think the generational controls offered by this addon are essential. |
The implementation for HA core is a bit hacky (uses a monkey patch) so it can break with updates, but shouldn't be too hard to get working again (hopefully). The HA OS or supervised implementation is still working. As for if this is still needed, depends on the use case, Auto Backup is still more powerful and, importantly for me at least, supports generational backup schemes. I think for some the internal support will be enough, and hopefully they'll continue to add more features like multiple automatic backup configurations, to support generational backups. |
So, the fix was a bit more complex this time as they completely changed the backup logic in HA Core, but the new logic is much better and we no longer need any monkey patches which means the implemenation should be much more stable this time. I've still got a few more things to sort out and test but hopefully should release the fix tonight |
* fixes backups not working for HA Core users on 2025.1.0 * adds native support for backup name * adds support for backup password Fixes: #178
* fixes backups not working for HA Core users on 2025.1.0 * adds native support for backup name * adds support for backup password Fixes: #178
Thank you so much for your effort |
Hi, was the fix already implemented ? I have reloaded the integration but the isuue remains: Logger: custom_components.auto_backup Error during backup. Unable to patch '_generate_backup_contents' function. |
🎉 This issue has been resolved in version 1.6.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Hahah you were just too fast 😄, I wanted to write a bit of an update in the release notes (also update the docs which is why I didn't release this afternoon), so I created a draft release first, but it's published now, do let me know if the fix is working, seemed to work great in my tests. Additionally |
Fantastic, thanks! |
Lovely, thank you very much |
Thank you so much for the quick upgrade—fantastic job! |
The problem
Every backup fails with HA 2025.1, since backup back-end has been changed from scratch
What version of Auto Backup has the issue?
1.5.3
What version of Home Assistant are you running?
Home Assistant 2025.1.0
What type of installation are you running?
Home Assistant Core
If you're running HA OS/Supervised, what version of the Supervisor are you running?
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: