Add-on: Home Assistant Google Drive Backup

sabeechen · October 27, 2020, 2:23am

Heh, thanks Jeff. I get a response like this every once in a while and it really keeps me going. I also attempted to get all those other things working, which in a fit of rage was exactly my motivation for making this addon. This addon was made for you <3

I have my own beefs with Google and empathize with the resistance about giving them money or information. I choose them as the provider for this addon because their “free” tier is relatively generous and their infrastructure is as good as it gets.

If you don’t want to support Google and still want to use this addon. Here is what I’d do:

Create a Dummy account on Google Drive just for this addon.
Use a password on your snapshots (that encypts them).
Keep your snapshots under the free size limit.
Only log into the Drive account through a VPN or at least an isolated browser session.
Don’t get suckered into using that login for anything else.

This will eliminate (or at least make almost useless) Google’s ability to make any marketing profile information off of what you’ve given them, and then they will be storing your bytes. Suck it, attention economy.

jazzmonger · October 27, 2020, 4:49am

Right on Stephen, Good solution!

Again I hope other devs look at your work and take notes. I get it that it takes time to achieve the polish you have in this addon, but hopefully you can publish a guide doc for others to reference so they can aspire to do this high level of work. It would really take The home assistant Platform to a whole new level.

I for one Make it a point to contribute to the authors of many well written apps I find especially useful.

Jeff

Matt_Barnes · October 27, 2020, 9:16am

Thank you!

I guess I was confused by my lovelace card that shows this:

which comes from this:

    - type: conditional  
      conditions:
        - entity: binary_sensor.snapshots_stale
          state_not: 'False'
      card:
        type: markdown
        content: >-
           Snapshots are stale! Please visit the "Hass.io Google Drive Backup" add-on
           status page for details.
        title: Stale Snapshots!`

so looks like I need to change state_not: false to “off” ?

Matt_Barnes · October 27, 2020, 9:47am

hmm, or not. that doesnt make it go away either.

thebogeyman · October 29, 2020, 8:17pm

Raspberry Pi 4, Home Assistant Supervised in Docker.
I cannot install this addon. The following error occurs:

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

Any ideas why?

sabeechen · October 30, 2020, 2:20am

Well, that image is definitely there (link).

I just released a new version (v0.102.0), maybe it’ll like the new one?

thebogeyman · October 30, 2020, 5:26am

Same problem

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

It’s the only addon so far that could not be installed via the supervisor.
It works on two other devices I’ve tested, one Raspberry Pi 3b with same setup, and even one Raspberry Pi 2.

snosig · October 30, 2020, 9:32am

I get the same error with the sabeechen/hassio-google-drive-backup-amd64 version:

404 Client Error: Not Found (“no such image: sabeechen/hassio-google-drive-backup-amd64:0.102.0: No such image: sabeechen/hassio-google-drive-backup-amd64:0.102.0”)

sabeechen · October 30, 2020, 3:20pm

I just tried updating and installing again on the 3 platforms I have access to (amd64, armv7, aarch64) and didn’t run into trouble. I don’t think this is a problem on my end, all of the images you guys are getting 404 errors for are present on Dockerhub where the supervisor looks for them:
sabeechen/hassio-google-drive-backup-amd64:0.102.0
sabeechen/hassio-google-drive-backup-armv7:0.102.0

Where is this error showing up, in the supervisor logs?

thebogeyman · November 2, 2020, 7:00am

Yes, it’s in the supervisor log and in the GUI:

olddawgpowers · November 2, 2020, 10:14pm

For some reason I had to Reauthorize Google Drive backup. When I first installed probably over a year ago I did my own credentials and it was working fine. When I was looking at backups I noticed no backup had been performed since October 20. Two questions. Do credentials expire and is there a warning to tell you a backup was not made. If I hadn’t checked, I would not have know backups were failing.

ASNNetworks · November 2, 2020, 10:42pm

There is a sensor you can use with automations. Look at your dev control and look for snapshot sensor. It shows state and a lot of attribute info. You can use that with automations/templates and give send notifications.

olddawgpowers · November 2, 2020, 11:41pm

Thanks. I will check that out. I thought it use to send notifications automatically, but I didn’t get any when it broke on October 20.

sabeechen · November 4, 2020, 5:32pm

The credentials generally never expire, but there are a few cases where you can expect them to stop working:

If you revoke it in your Google Account Permissions
If the addon doesn’t talk to Google Drive for 6+ months
If you have too many other apps authenticated with an account (not clear what the limit is there).

(source)
If the addon isn’t able to back up or take new snapshots on its schedule you should see an error in web-UI. If that persists for a few hours you should see:

A persistant notification show up in the Home Assistant web-UI saying the addon has trouble. This is the same place you see failed login attempts, the new integration notification, etc. If the problem goes away then the notification gets dismissed automatically.
The binary_sensor.snapshots_stale sensor’s state will be ‘on’. If you want to have more aggressive notifications, I’d trigger off that sensor’s state.

Note that both of these can be turned off in the settings if you choose.

olddawgpowers · November 4, 2020, 8:40pm

Thank you for your help. I could have possibly did something when I was integrating Google Calendar as I remember going in to Google projects. All is working now.

thebogeyman · November 4, 2020, 9:06pm

Not sure if I’m doing this correctly since I have never used Docker before, but when trying to pull the image via Portainer I get the same error:

duceduc · November 4, 2020, 10:38pm

Anyone knows how I can fix these huge fonts appearing when opening Open Web UI. As far as I can see, it has been like this when first installing Hass.io Google Drive Backup. Only this add-on, the fonts are huge. Other add-on display the font size as normal.

sabeechen · November 4, 2020, 10:54pm

This is a webserver problem, those large blocks of text are showing up because the page is unable to load all of its assets.

If you’re using a reverse proxy to serve Home Assistant, make sure it is configured properly as I’ve described in this bug thread.

Off not, you can open an issue on github and we can dig into it more.

sabeechen · November 4, 2020, 11:05pm

@thebogeyman
If it fails in portainer then it isn’t a problem with the addon or the supervisor. I tried doing the same on my test machines and was unable to reproduce the 404 error. I’m not sure what would make docker unable to find that addon’s image, its definitely there with that specific name and tag.

DockerHub has recently change its policies about how anonymous requests are served (which is how Home Assistant pulls from DockerHub) but none of the announced changes should cause this.

duceduc · November 4, 2020, 11:54pm

The second method works.
That also explains why it took close to a minute to load the page only to see huge text blocks.