Add-on: Home Assistant Google Drive Backup

Trying to install via HACS, get the following error: Repostitory structure for v0.98.1 is not compliant

What version of HA are you running ? If 0.98.1 then maybe you need to update HA first.

Is there a chance to have more than one snapshot settings?
eg. Full snapshot every week, Partial daily

1 Like

On 2 systems: 1.9.0 both giving the same error, one system is a clean install from today

This isn’t a HACS plugin. You have to install it through the Home Assistant addon store.

1 Like

Got it… to much places :slight_smile:
Navigate in your Home Assistant frontend to Supervisor -> Add-on Store .

@sabeechen have you had the chance to review this? thanks!!

As others have noted you can only exclude entire folders, and only those the supervisor recognizes (share, ssl, media, HA config). This isn’t an inconsistency, it is a supervisor limitation.

I understand why this functionality is so widely desired, but my hands are tied by what the supervisor permits the addon to do. To be completely clear:

  • There is no way to exclude subfolders of one of the main folders (share, ssl, media, HA Config) from a backup.
  • There is no way to exclude specific files or types of files from a backup.
  • This is because of a supervisor limitation. There is no way for me to add support for this in the addon.

If you’re able to partition just the files you want to exclude into one of those folders, then you can exclude that. If you aren’t able to do that cleanly with zigbee2mqtt addon (I’m not familiar with its configuration) then there is no to do it. Maybe you could put the motioneye recordings in ssl or media if you’re otherwise not using the folders?

Hi there,

thanks for your answer. When I referred to that inconsistency I was referring to this portion of the README file:

there you can see a reference to: “home assistant configuration, share, SSL, local addons”

however, in the configuration parameters this is what I see listed as options: “homeassistant,ssl,share,addons/local,media”

In the latter I see 5 options whereas in the documentations there are 4. Sorry if I’m overlooking something very obvious. :pray: :pray:

So the docs need to be updated to include ‘media’ which was only recently added to the Home Assistant architecture.

I had the same problem:

404 Client Error: Not Found ("no such image: sabeechen/hassio-google-drive-backup-armv7:0.103.0: No such image: sabeechen/hassio-google-drive-backup-armv7:0.103.0")

My HA is running with a raspberry Pi 3b. I tried to make a docker image pull but the problem was still happening.

The only option that has worked for me has been to reinstall (uninstall before and copy your configurations) and re-authenticate with Google. The addon detects a previous existing folder and allows you to select the same location to take snapshots

If any logs/data persist and you want to investigate/trace this possible issue I will try to provide it without problem

Greet addon! And thanks for your job!

Cheers, Alex.

FYI: the installation of the newest version suddenly worked for me.
I don’t know if I have changed anything in my environment in the past or home assistant did, but now it’s running fine.

EDIT:
I’ll answer myself - just wait. Supervisor did it’s job and addon did the upload later that day.

I had an hardware-related issue today and during snapshot (or upload) my machine stalled.

After recovering everything works fine, except:

  1. I don’t see today’s snapshot
  2. addon sees it like that:



    image
    although CPU/RAM usage suggests nothing is happening in background.

How do I get addon back-on-track?

Thanks for an excellent add-on Stephen :grin:

1 Like

@sparkydave and @kitus You’re right that its missing, I just added the media folder to that section to the FAQ.

@andriej restart the addon if it still thinks a snapshot in in progress, and if that doesn’t work also restart the supervisor. If that doesn’t solve it, could you go to “ACTIONS” > “Report a Bug” in the addon’s web-ui and post the details from it in a new issue on GitHub?

Thank you for the reply.
As I’ve added in the edit - Supervisor (and so the add-on) finished the job later that day and addon did backup the snapshot way after it’s standard scheduled time, but still - with success.

Thanks for the addon and work you put into it. :slight_smile:
I’d love to see Dropbox support later time, as Google space will be valuable after June. :wink:

I’ve just made a new release, v0.103.1. If you don’t see the update right away, go to “Add-on Store” > Dots in the top right > Reload.
I don’t usually post here for bug-fix-only-releases, but this one includes two noticeable fixes. Specifically:

  • #166 Which prevented many from having snapshots start at a specified time of day. This has been a problem for over a year (maybe always) and I’d given up hope on tracking it down. Thankfully @jhampson-dbre was able to step in and find it instead.
  • #328 Which prevented old versions of the addon from getting cleaned up when updating. If you’ve been using the addon for a long time, you may notice several GB of space free-up after installing the latest version. The addon’s docker image is also much smaller now.

Thanks for everyone’s support! If you run into trouble file a bug on GitHub, post a question here, or rage about it silently in your head until the feeling fades into a deep, quite place.

If you:

  • Like this or what I do.
  • Don’t like this or what I do but like clicking colorful buttons

Then you can

4 Likes

I had some issues with my supervisor after a hard shut down due to power loss. After a lot of restoring from this morning snapshot and manual reconfiguration I’m mostly back to working - but for some reason I cannot get this add on to start. It’s installed, and I’ve been using it for over a year, but now when it attempts to call to docker to start the add on I get the error below. HA is running on my Synology (which was the root of my issues with supervisor)… Any thoughts on how to resolve this?

500 Server Error for http+docker://localhost/v1.39/containers/0c2451927202956a5c5c4bcbd4fb94883041821ea4e46bab2709e74e2d84f0e7/start: Internal Server Error ("OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown")

1 Like

Thanks for this add-on!

1 Like