Home Assistant Google Drive Backup

About

A complete and easy way to back up Home Assistant to Google Drive.

This is for you if you want to quickly set up a backup strategy without much fuss. It doesn't require much familiarity with Home Assistant, its architecture, or Google Drive. Detailed install instructions are provided below but you can just add this repo, click install and open the Web UI. It will tell you what to do and only takes a few simple clicks. Detailed install instructions are below if that doesn't seem clear.

Features Overview

• Creates backups on a configurable schedule.
• Uploads backups to Drive, even the ones it didn't create.
• Clean up old backups in Home Assistant and Google Drive, so you don't run out of space.
• Lots of options for customization, but never requires you to write a yaml file.
• Restore from a fresh install or recover quickly from disaster by uploading your backups directly from Google Drive.
• Integrates with Home Assistant Notifications and provides sensors you can trigger off of.
• Notifies you when something goes wrong with your backups.
• Super easy installation and configuration.
• Privacy-centric design philosophy.
• Comprehensive documentation.
• Most certainly doesn't mine bitcoin on your home automation server. Definitely no. Or does it?

The Upsell

This addon has been featured by %YOUR_FAVORITE_HA_YOUTUBER% and is often listed as an essential addon when starting with Home Assistant. Here are some videos about it from others if you'd like to get an idea of what using it looks like or what the community thinks:

This project requires financial support to make the Google Drive integration work, but it is free for you to use. You can join those helping to keep the lights on at:

Detailed Install Instructions

1. Navigate in your Home Assistant frontend to Settings -> Add-ons -> Add-on Store (Bottom Right).

2. Click the 3-dots menu at upper right ... > Repositories and add this repository's URL: https://github.com/sabeechen/hassio-google-drive-backup

   

3. Reload the page , scroll to the bottom to find the new repository, and click the new add-on named "Home Assistant Google Drive Backup":

   

   Note: Home Assistant loads the repository in the background and the new item won't always show up automatically. You might need to wait a few seconds and then "hard refesh" the page for it to show up. On most browser the keyboard shortcut for this is CTRL+F5. If it still doesn't show up, clear your browser's cache and it should then.

4. Click Install and give it a few minutes to finish downloading.

5. Click Start, give it a few seconds to spin up, and then click the Open Web UI button that appears.

6. The "Getting Started" page will tell you how many backups you have and what it will do with them once you connect it to Google Drive. You can click Settings to change those options through the add-on (which is the recommended way, they take effect immediately), or update them from the page where you installed the add-on as described below (also works, restart for them to take effect).

7. Click the Authenticate with Drive button to link the add-on with your Google Drive account. Alternatively, you can generate your own Google API credentials, though the process is not simple.

8. You should be redirected automatically to the backup status page. Here you can make a new backups, see the progress of uploading to Google Drive, etc. You're done!

Configuration

After you start the addon you have an opportunity to review your settings within the addon's Web-UI before you connect it to Google Drive. It is recommended to modify the setting this way because the UI makes it easy and explains what each option does.

If you'd still prefer use edit your setting in yaml or through the supervisor, the list of configurable options with explanations is available here.

FAQ

Is this for me?

Most likely, yes. This addon is focused on making backup simple, reliable, easy to understand, and well supported. It provides clear error messages when things go wrong and explains how you fix it. It has a fancy-pants web interface you can look at to see how things are going. To do that it sacrafices customizability. It can't:

• Create backups more than once a day.
• Create backups only when your configuration changes.
• Upload somewhere other than Google Drive.
• Be customized outside of what the settings allow.

If you want a backup strategy highly customized to your needs, you might be better off hacking something together with automations and the samba addon, for example. This project started out as me doing exactly that for myself, and now its grown into a mature project with ~100k people using it all over the world. Weird. I never thought I'd be getting community pressure to translate the UI into portugese, but here I am dealing with those kinds of problems now.

How will I know this will be there when I need it?

Home Assistant is notorious for failing silently, and your backups aren't something you want to find is broken after an erroneous comma makes you unable to turn on any of the lights in your house. That's why I've added some functionality to keep you informed if things start to break. If the add-on runs into trouble and gets more than 12 hours behind its schedule, you'll know in two ways:

• Notifications in Home Assistant UI

  

• A binary_sensor you can use to trigger additional actions.

  

Redundancy is the foundation of reliability. With local backups, Google Drive's backups, and two flavors of notification I think you're covered.

How do I restore a backup?

The backups this addon creates are the same backups that Home Assistant makes by itself and can be restored using any of the methods documented elsewhere. Here are few pointers to get you started.

• If you can still get to the addon's web-UI then select the backup and click "Load into Home Assistant" have it copied back into Home Assistant.
• If not (eg, maybe your hard drive died and you're starting over):
  • Download one of the backups you've previously created from Google Drive.
  • On whatever hardware you're using to run Home Assistant now, follow the normal instructions to install Home Assistant.
  • Once it's running (but before you create a user), click the link on the Home Assistant setup page that says "Alternatively you can restore from a previous backup" and upload the backup you downloaded from Google Drive.
• If you've got a backup that you'd like to restore to an already set up Home Assistant instance that doesn't already have this addon installed, you'll need to use something like the Samba Addon to copy a backup downloaded from Google Drive into the /backup folder.

I never look at HA notifications. Can I show information about backups in my Home Assistant Interface?

The add-on creates a few sensors that show the status of backups that you could trigger automations off of. binary_sensor.backups_stale becomes true when the add-on has trouble backing up or creating backups. For example, the Lovelace card below only shows up in the UI when backups go stale:

Lovelace Card

type: conditional
conditions:
  - entity: binary_sensor.backups_stale
    state_not: "off"
card:
  type: markdown
  content: >-
    Backups are stale! Please visit the "Home Assistant Google Drive Backup" add-on
    status page for details.
  title: Stale Backups!`

Mobile Notifications

If you have android or iOS, other notifications set up, this automation would let you know if things go stale:

    - alias: Backups went stale
      id: 'backups_went_stale'
      trigger:
      - platform: state
        entity_id: binary_sensor.backups_stale
        from: 'off'
        to: 'on'
      condition: []
      action:
      - service: notify.android
        data:
          title: Backups are Stale
          message: Please visit the 'Home Assistant Google Drive Backup ' add-on status page
            for details.

You could automate anything off of this binary sensor. The add-on also exposes a sensor sensor.backup_state that exposes the details of each backup. I'm working on a custom Lovelace component to expose that information.

Can I specify what time of day backups should be created?

You can add "backup_time_of_day": "13:00" to your add-on configuration to make backups always happen at 1 pm. Specify the time in the 24-hour format of "HH:MM". When unspecified, the next backup will be created (roughly) at the same time of day as the last one.

Can I keep older backups for longer?

This is just an overview of how to keep older backups longer. See here for a more in-depth explanation.

The add-on can be configured to keep generational backups on daily, weekly, monthly, and yearly intervals instead of just deleting the oldest backup. This can be useful if, for example, you've made an erroneous change but haven't noticed for several days and all the backups before the change are gone. With a configuration setting like this...

generational_days: 3
generational_weeks: 4
generational_months: 12
generational_years: 5

... a backup will be kept for the last 3 days, the last 4 weeks, the last 12 months, and the last 5 years. Additionally, you may configure the day of the week, day of the month, and day of the year that weekly, monthly, and yearly backups are maintained.

generational_days: 3

generational_weeks: 4
generational_day_of_week: "mon" # Can be 'mon', 'tue', 'wed', 'thu', 'fri', 'sat' or 'sun' (defaults to 'mon')

generational_months: 12
generational_day_of_month: 1 # Can be 1 through 31 (defaults to 1)

generational_years: 5
generational_day_of_year: 1 # can be 1 through 365 (defaults to 1)

• Any combination of days, weeks, months, and years can be used. They all default to 0.
• It's highly recommended to set 'days_between_backups: 1' to ensure a backup is available for each day.
• Ensure you've set max_backups_in_drive appropriately high to keep enough backups (24 in the example above).
• Once this option is enabled, it may take several days or weeks to see older backups get cleaned up. Old backups will only get deleted when the number present exceeds max_backups_in_drive or max_backups_in_ha

I already have something that creates backups on a schedule. Can I use this just to backup to Google Drive?

If you set 'days_between_backups: 0', then the add-on won't try to create new backups but will still upload up any it finds to Google Drive and clean up old backups in both Home Assistant and Google Drive. This can be useful if you already have for example an automation that creates backups on a schedule.

Can I give backups a different name?

The config option backup_name can be changed to give backups a different name or with a date format of your choosing. The default is {type} Backup {year}-{month}-{day} {hr24}:{min}:{sec}, which makes backups with a name like Full Backup 2021-10-31 14:00:00. Using the settings menu in the Web UI, you can see a preview of what a backup name will look like but you can also set it in the add-on's options. Below is the list of variables you can add to modify the name to your liking.

• {type}: The type of backup, either 'Full' or 'Partial'
• {year}: Year in 4 digit format (eg 2)
• {year_short}: Year in 2 digit format (eg 19)
• {weekday}: Long day of the week (eg Monday, ..., Sunday)
• {weekday_short}: Short day of week (eg Mon, ... Sun)
• {month}: 2 digit month (eg 01, ... 12)
• {month_long}: Month long name (January, ... , December)
• {month_short}: Month long name (Jan, ... , Dec)
• {ms}: Milliseconds (001, ..., 999)
• {day}: Day of the month (01, ..., 31)
• {hr24}: 2 digit hour of the day (0, ..., 24)
• {hr12}: 2 digit hour of the day (0, ..., 12)
• {min}: 2 digit minute of the hour (0, ..., 59)
• {sec}: 2 digit second of the minute (0, ..., 59)
• {ampm}: am or pm, depending on the time of day
• {version_ha}, Home Assistant version string (eg 0.91.3)
• {version_hassos}: HassOS version string (eg 0.2.15)
• {version_super}: , Supervisor version string (eg 1.2.19)
• {date}: Locale aware date (eg 2022/01/01).
• {time}: Locale aware time (eg 02:03:04 am)
• {datetime}: Locale-aware datetime string
• {isotime}: Date and time in ISO format
• {hostname}: The Home Assistant machine's hostname

Will this ever upload to Dropbox/OnDrive/FTP/SMB/MyFavoriteProtocol?

Most likely no. I started this project to solve a specific problem I had, storing backups in a redundant cloud provider without having to write a bunch of buggy logic and automations. It might seem like a small change to make this work with another cloud provider, but trust me. I wrote this version of it, and it's not a simple change. I don't have the time to do it.

But Google reads my emails!

Maybe. You can encrypt your backups by giving a password in the add-on's options.

Does this store any personal information?

On a matter of principle, I only keep track of and store information necessary for the add-on to function. To the best of my knowledge the scope of this is:

• You can opt-in to sending error reports from the add-on sent to a database maintained by me. This includes the full text of the error's stack trace, the error message, and the version of the add-on you're running. This helps notice problems with new releases but leaving it off (the default unless you turn it on) doesn't affect the functionality of the add-on in any way.
• Once authenticated with Google, your Google credentials are only stored locally on your Home Assistant instance. This isn't your actual username and password, only an opaque token returned from Google used to verify that you previously gave the Add-on permission to access your Google Drive. Your password is never seen by me or the add-on. You can read more about how authentication with Google is accomplished here.
• The add-on has access to the files in Google Drive it created, which is the 'Home Assistant Backups' folder and any backups it uploads. See the https://www.googleapis.com/auth/drive.file scope in the Drive REST API v3 Documentation for details, this is the only scope the add-on requests for your account.
• Google stores a history of information about the number of requests, number of errors, and latency of requests made by this Add-on and makes a graph of that visible to me. This is needed because Google only gives me a certain quota for requests shared between all users of the add-on, so I need to be aware if someone is abusing it.
• The Add-on is distributed as a Docker container hosted on Docker Hub, which is how almost all add-ons work. Docker keeps track of how many people have requested an image and makes that information publicly visible.

This invariably means that I have a very limited ability to see how many people are using the add-on or if it is functioning well. If you do like it, feel free to shoot me an email at [email protected] or star this repo on GitHub, it helps keep me motivated. If you run into problems or think a new feature would be nice, file an issue on GitHub.

Can I use my own Google API information to authenticate instead of yours?

On the first "Getting Started" page of the add-on underneath the "Authenticate with Google Drive" button is a link that lets you enter your own Client Id and Client Sercet to authenticate with Google Drive. You can get back to that page by going to "Actions" -> "Reauthorize Google Drive" from the add-on's web UI if you've already connected it previously. Instructions are also provided for those who are unfamiliar with the process, it's tedious to complete but ensures the add-on's communication is only between you and Google Drive.

Can I permanently save a backup so it doesn't get cleaned up?

Select "Never Delete" from the menu next to a backup in the add-on's Web UI. You can choose to keep it from being deleted in Home Assistant or Google Drive. When you do this, the backups will no longer count against the maximum number of backups allowed in Google Drive or Home Assistant. Alternatively, you can move a backup in Google Drive out of the backup folder. the add-on will ignore any files that aren't in the backup folder. Just don't move them back in accidentally since they'll get "cleaned up" like any old backup after a while :)

What do I do if I've found an error?

If the add-on runs into trouble and can't back up, you should see a big red box with the text of the error on the status webpage. This should include a link to pre-populate a new issue in GitHub, which I'd encourage you to do. Additionally, you can set the add-on config option "verbose": true to get information from the add-on's logs to help me with debugging.

Will this fill up my Google Drive? Why are my backups so big?

You'll need to take care to ensure you don't configure this to blow up your Google Drive. You might want to consider:

• If your backups are HUGE, it's probably because Home Assistant by default keeps a long sensor history. Consider setting purge_keep_days: N in your recorder configuration to trim it down to something more manageable, like 1 day of history.
• Some other add-ons are designed to manage large amounts of media. For example, add-ons like the Plex Media Server are designed to store media in the /share folder, and Mobile Upload folders default to a sub-folder in the addons folder. If you migrate all of your media to the Home Assistant folder structure and you don't exclude it from the backup, you could easily chew up your entire Google Drive space in a single backup.
• If you use the Google Drive Desktop sync client, you'll probably want to tell it not to sync this folder (it's available in the options).

I want my backups to sync to my Desktop computer too

That's not a question but you can use Google Drive Backup & Sync to download anything in your Google Drive to your desktop/laptop automatically.

I configured this to only keep 4 backups in Drive and Home Assistant, but sometimes I can see there are 5?

The add-on will only delete an old backup if a new one exists to replace it, so it will create a 5th one before deleting the first. This is a reliability/disk usage compromise that favors reliability because otherwise, it would have to delete an old backup (leaving only 3) before it could guarantee the 4th one exists.

Can I exclude specific sub-folders from my backup?

The add-on uses the supervisor to create backups, and the supervisor only permits you to include or exclude the 5 main folders (home assistant configuration, share, SSL, media, and local add-ons). Excluding specific subfolders, or only including specific subfolders from a backup isn't possible today.