-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
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
2025.2.0b2 One Drive Automatic backup fails #136959
Comments
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) backup documentation |
Just want to chime in that I get the same error. With 2025.2.0b1 I could not connect to OneDrive. With b2 it is possible to link it.
And
Hmm, just checked my OneDrive and the Folders /Apps/Home Assistant/backups_slug/ are created and I even see a .tar file in the folder. The state inside Home Assistant still says the upload failed though. Tried an encrypted and unencrypted OneDrive backup. Both give the same error, and both upload the file just fine. |
Just tried the same thing again; Initiated an automated backup and the upload to One Drive succeeded. |
Hey there @zweckj, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) onedrive documentation |
The problem
Initiated an automatic backup One Drive failed. Local, local network and Google Drive succeeded
Repeated 10 minutes later same failure. I'm able to access One Drive directly on my PC
What version of Home Assistant Core has the issue?
2025.2.0b2
What was the last working version of Home Assistant Core?
2025.2.0b1
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Backup
Link to integration documentation on our website
No response
Diagnostics information
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: