The add-on got the error below while trying to sync your backups. Some transient errors are expected (e.g. an upload could fail if the internet is down) but if this persist for more than a few minutes your backups won't get uploaded and the information you see on this page may be stale. If you file an issue on GitHub with the link below, it could be helpful to provide the logs downloaded from the "Download Logs" link below
It looks like you're low on disk space. The addon won't attempt to create a backup until you take action or more space becomes available. It looks like your backup folder in Home Assistant is full and only has left so creating another backup runs the risk of exhausting the space available. When Home Assistant runs out of disk space, it can stop responding and become very difficult to fix. This addon can only estimate how big the next backup will be based on your most recent one, it can't know how big the backup will be until its actually created.
To resolve this you can:
Google Drive is full, backups can't continue until space is available. You can go to Google Drive's quota page to see what's using up space in your Google Drive, but because that space is shared between several Google products (e.g. Gmail, Google Photos) one of those products might be using the space instead. You can see your usage across all those products on Google's storage settings page.
To resolve this you can:
Google Drive rejected your credentials. Your backups will not be uploaded until this is resolved.
This can happen if:
To resolve this, you'll need to authenticate this add-on with Google again. If that still doesn't help, you may need to update the add-on
{% endcall %} {% set delete_error_actions %} refreshTry Syncing Again {% endset %} {% call macros.errorMessage("Couldn't delete old backups in Home Assistant", "delete_error", "delete_forever", delete_error_actions) %}The add-on ran into an error (HTTP 400) trying to delete your oldest backup. This can happen sometimes (especially if you just installed the add-on) when Home Assistant's cache of your existing backups is out of sync. The add-on can't continue until this is resolved.
To resolve this, you can try:
The add-on will retry periodically to check if the issue is resolved. To retry now, click "Try Syncing Again" below. If the above doesn't help, please file an issue on GitHub to get more help.
{% endcall %} {% set google_dns_actions %} refreshTry Syncing Again {% endset %} {% call macros.errorMessage("Couldn't Reach Google Drive (DNS error)", "google_dns", "cloud_off", google_dns_actions) %}The add-on couldn't resolve Google Drive's server address. Backups can't be uploaded without being able to reach Google Drive.
Please ensure:
Below is the list of names and IP Addresses Google's API servers resolve to. Next to each is the result from an attempt the add-on has made to ping the address. This may help in determining if something in your network is blocking access to one of Google's API servers, or if Google's API servers are having problems.
You can also try restarting this add-on, the supervisor, or Home Assistant.
{% endcall %} {% set google_timeout_actions %} refreshTry Syncing Again {% endset %} {% call macros.errorMessage("Google Drive Connection Timeout", "google_timeout", "cloud_off", google_timeout_actions) %}The connection timed out or was closed unexpectedly while trying to communicate with Google Drive. Backups can't be uploaded without being able to reach Google Drive reliably. This can happen transiently from time to time and the addon will continue to attempt to sync your backups. This problem almost always resolves itself after some time.
Please ensure:
Below is the list of names and IP Addresses Google's API servers resolve to. Next to each is the result from an attempt the add-on has made to ping the address. This may help in determining if something in your network is blocking access to one of Google's API servers, or if Google's API servers are having problems.
You can also try syncing again or restarting this add-on, the supervisor, or Home Assistant.
{% endcall %} {% set google_cant_connect_actions %} refreshTry Syncing Again {% endset %} {% call macros.errorMessage("Can't Connect to Google Drive", "google_cant_connect", "cloud_off", google_cant_connect_actions) %}Google Drive refused an attempt to connect with it. Backups can't be uploaded without being able to reach Google Drive.
Please ensure:
Below is the list of names and IP Addresses Google's API servers resolve to. Next to each is the result from an attempt the add-on has made to ping the address. This may help in determining if something in your network is blocking access to one of Google's API servers, or if Google's API servers are having problems.
You can also try syncing again or restarting this add-on, the supervisor, or Home Assistant.
{% endcall %} {% set password_key_invalid_actions %} refreshTry Syncing Again {% endset %} {% call macros.errorMessage("Invalid Backup Password", "password_key_invalid", "vpn_key", password_key_invalid_actions) %}The add-on couldn't find your backup password in your secrets.yaml file. Backups can't be created until you either configure a valid password or remove it.
This can happen if:
Please review your settings add-on settings to ensure you've set the backup password you intended, then sync again.
{% endcall %} {% set backup_in_progress_actions %} refreshTry Syncing Again {% endset %} {% call macros.errorMessage("Backup Already in Progress", "backup_in_progress", "settings_backup_restore", backup_in_progress_actions) %}The add-on couldn't create a backup on schedule because one is already in progress. Home Assistant can only create one backup at a time. This can happen if:
Typically you don't need to do anything to resolve this, as the add-on will pick up again once the backup in progress finishes. If you are certain no backup is in progress already or this error sticks around, you can try restarting the addon or Home Assistant's host machine.
{% endcall %} {% set multiple_deletes_actions %} deleteAllow Deletion delete_foreverNever Ask again {% endset %} {% call macros.errorMessage("Attempting to Delete Multiple Backups", "multiple_deletes", "delete_forever", multiple_deletes_actions) %}The add-on attempted to delete (?) backup(s) from Google Drive and (?) backup(s) from Home Assistant. Under normal circumstance, the add-on will only delete one backup at a time (the oldest). This warning is produced to prevent the add-on from accidentally deleting your history of backups. This is normal if you recently lowered the number of backups to keep in Google Drive or Home Assistant.
To resolve this you can:
Google returned a server error (HTTP code 500) while trying to backup your backups.
This happens sometimes for reasons beyond anyone's control and almost always the problem goes away on its own. The add-on will attempt uploading again soon, but you can also click "Try Syncing Again" below to make it retry now.
If this error keeps sticking around, you can try:
Google returned a server error (HTTP code 404) while trying to upload your backups.
In most cases, this indicates that your upload took too long to upload. According to Google's documentation if an upload takes longer than a week then it will be forcibly cancelled and return this error. This can happen if your internet is very slow or your backups are very large, however the developer of this addon suspects this can happen in more common circumstances. If the below options don't help, please file an issue on GitHub with as much detail as you can stomach to help him look into it.
If this error keeps sticking around, you can try:
The add-on found a backup folder named "" in Google Drive that might already have backups in it. This is normal if you've used this addon before, but you'll need to decide where backups should go before this will start backing up again. Click here to see the folder contents in Google Drive.
To resolve this you can:
Note: If you run multiple instance of Home Assistant with this addon using the same Google Drive account, its recommended that you use a different folder for each instance. Otherwise they'll delete each other's backups!
{% endcall %} {% set backup_folder_missing_actions %} settingsOpen settings {% endset %} {% call macros.errorMessage("Please choose a backup folder", "backup_folder_missing", "folder_special", backup_folder_missing_actions) %} {{ chooseFolder(id="choose_folder_folder_missing") }}If you'd rather not specify the folder for uploads, please return to your settings add-on settings and change your preference.
If you run multiple instances of Home Assistant with this addon using the same Google Drive account, its recommended that you use a different folder for each instance. Otherwise they'll delete each other's backups!
The addon couldn't use the folder you chose for storing backups. The addon can't backup your backups until you resolve this. This can happen if:
To resolve this, you can:
Open your settings add-on settings and deselect "Manually specify the backup folder". The addon will automatically create a new folder for you.
If the folder still exists, you can restore access to it by the addon by ensuring that your google account has access to it. The folder should be accessible from this link. After doing so, click "sync now" below to try syncing again.
Sync was cancelled because you requested it. The addon will not resume syncing for another hour unless you take action.
Please note:
A pending backup can't be stopped once its started, because its creation is managed by Home Assistant. Being "Paused" only stops the addon from creating new backups and syncing them with Google Drive.
You can resume by clicking the link below or just waiting.
The addon was unable to refresh your credentials with Google Drive. When it tried, Google said:
(?)
This can happen if:
Usually this problem will resolve on its own, but you can try:
The addon was unable to refresh your credentials with Google Drive. When it tried, https://habackup.io said:
(?)
This can happen if:
Usually this problem will resolve on its own, but you can try:
The addon was unable to connect to the Home Assistant Supervisor. This addon requires the supervisor to be running to create backups, load configuration, etc. Without the supervisor the addon will not be able to do anything useful. Typically this should never happen, and indicates that something is wrong with your Home Assistant installation.
To resolve this you can try:
The addon was unable to communicate with the Supervisor because it said the addon is unauthorized. This addon must communicate with the supervisor to create backups, load configuration, etc. Without the supervisor the addon will not be able to do anything useful. Typically this should never happen, and indicates that something is wrong with your Home Assistant installation.
The addon was unable to communicate with the Supervisor because it timed out. This addon must communicate with the supervisor to create backups, load configuration, etc. Without the supervisor the addon will not be able to do anything useful. This usually resolves itself after the addon retries, but if you see this error stick around for a while you can try
The addon was unable to communicate with the Supervisor because it gave back an unreadable response. This addon must communicate with the supervisor to create backups, load configuration, etc. Without the supervisor the addon will not be able to do anything useful. This usually resolves itself after the addon retries, but if you see this error stick around for a while you can try:
The addon was unable to write to the file system on this machine. Normally this indicates there is a problem with the Home Assistant supervisor, which is responsible for creating the file system this addon needs to function. Here are some reasons this might happen:
The addon was unable to communicate with Google Drive because it gave back an unreadable response. Without being able to communicate with Google Drive, the addon will not be able to transfer backups to the cloud. This usually resolves itself after the addon retries, but if you see this error stick around for a while you can try:
The addon couldn't backup your backups because it looks like it you've never logged in to the Google Drive website before. Doing this at least once is required for applications like this to use Google Drive.
To resolve this, you can:
Visit https://drive.google.com and log-in with the account you used to connect this addon to Google Drive, then click "SYNC NOW" below to start syncing.
Reauthorize the addon with Google Drive using a different account.