Feature request: Support for HA's new third party backup location integration

[RubenKelevra]

I love your custom_component and have been using it for years now. I would really enjoy if you could create an integration for the new backup method provided by Home Assistant 2025.1, so we can sync our backups in the future to Google Drive directly within Home Assistant:

https://rc.home-assistant.io/blog/2024/12/23/release-20251/#backup-locations-are-extendable-by-design-

[Mariusthvdb]

there is something odd going on:

Google Drive:

the new Automatic HA backups appear in the Google drive, and in the Add-on interface, the new automatic network storage backups show up:

somehow the add-on confuses the HA system.

[Mariusthvdb]

sorry if I misunderstand your FR, but, in the current state of HA/Add-on, if you use the default location for both of the integrations, this is exactly what is happening.

HA stores the backup in the default location, as does the add-on.... next, the add-on uploads it to GD. be it the automatic backup, or a backup by the add-on

take care, this also happens when deleting backups.....

for now, I made a separate/dedicated network share on my system for the GD add-on, hoping this will keep the 2 apart.

if this is not at al what you need/request, please except my apologies for polluting your FR, and Ill delete the comments

[RubenKelevra]

@Mariusthvdb yes you misunderstood my FR. No worries, everything is fine.

[dougmaitelli]

I assume the FR is to change this addon to be a provider for GD to be used in the new automatic backups instead. There is probably no reason to have a separate automatic backup logic in an add-on anymore.

[RubenKelevra]

I assume the FR is to change this addon to be a provider for GD to be used in the new automatic backups instead. There is probably no reason to have a separate automatic backup logic in an add-on anymore.

Yeah, I thought that's obvious?

[dougmaitelli]

I assume the FR is to change this addon to be a provider for GD to be used in the new automatic backups instead. There is probably no reason to have a separate automatic backup logic in an add-on anymore.

Yeah, I thought that's obvious?

My comment was for @Mariusthvdb since he did misunderstood the original request.

[pantherale0]

I've built a backup provider for Google Drive here, its currently built to use Google Drives app data storage space so the only way to access the backups is via a Home Assistant instance.

https://github.com/pantherale0/ha-googledrive-backup

[dougmaitelli]

I've built a backup provider for Google Drive here, its currently built to use Google Drives app data storage space so the only way to access the backups is via a Home Assistant instance.

https://github.com/pantherale0/ha-googledrive-backup

So, this means it is not possible to download the compressed zip backup from GD in order to restore an instance, you need to setup the integration first in order to restore, correct?

[pantherale0]

So, this means it is not possible to download the compressed zip backup from GD in order to restore an instance, you need to setup the integration first in order to restore, correct?

Correct.

This is just how I've implemented it based on the scopes recommendations documented by Google. Plus the backups aren't actually named anything pretty anyway (simply their backup ID which is a 8 character hex string). There is also more metadata that is stored separately in this new backups mechanism in HA. I did try Google Drive's own metadata fields, but they don't support the complex types needed for the backups in HA.

Almost like you need a "database" of sorts alongside the backup files themselves. Want to see how this backup feature progresses though first before changing anything further, there is a lot of upset in the community by the forced encryption.

[rononline]

I've built a backup provider for Google Drive here, its currently built to use Google Drives app data storage space so the only way to access the backups is via a Home Assistant instance.

https://github.com/pantherale0/ha-googledrive-backup

Not working for me, when I try to add the integration:

Error occurred loading flow for integration google_drive: No module named 'aiogoogle'

[pantherale0]

Ohhhh gutted, left some old refs in there then. Will fix now. 2 secs

[rononline]

That was quick! :-) And it worked now!

[dougmaitelli]

So, this means it is not possible to download the compressed zip backup from GD in order to restore an instance, you need to setup the integration first in order to restore, correct?

Correct.

This is just how I've implemented it based on the scopes recommendations documented by Google. Plus the backups aren't actually named anything pretty anyway (simply their backup ID which is a 8 character hex string). There is also more metadata that is stored separately in this new backups mechanism in HA. I did try Google Drive's own metadata fields, but they don't support the complex types needed for the backups in HA.

Almost like you need a "database" of sorts alongside the backup files themselves. Want to see how this backup feature progresses though first before changing anything further, there is a lot of upset in the community by the forced encryption.

I did not know they were forcing encryption.
I love HA, but they have some weird decisions sometimes, like the resistance on adopting support to external authentication layers like OpenID and other things.

Definitely makes sense to wait a while then and see how this evolves.

[pantherale0]

Someone is working on this to be added into core, perhaps for release 2024.2.0

[mgriffin13]

Someone is working on this to be added into core, perhaps for release 2024.2.0

Do you have an issue that I could watch? I tried searching the open issues but I wasn't able to find anything

[pantherale0]

Nope, it was mentioned in the beta channel of the discord server.

[ShonP40]

I've built a backup provider for Google Drive here, its currently built to use Google Drives app data storage space so the only way to access the backups is via a Home Assistant instance.

https://github.com/pantherale0/ha-googledrive-backup

Kinda impossible to install it since you archived the repo…

[pdecat]

The HA core PR is at home-assistant/core#134576

[Mariusthvdb]

we should probably keep the FR in this Repo about the add-on and not discuss the aspects of the new PR's for HA here.
Great that is being developed btw. but no subject in here, if only to keep things tidy.

the add-on has so much to offer that probably will never get accepted in HA core, so FR ing this add-on is very valuable as it stands.

[gfn256]

Following this thread with interest, however it appears that sabeechen has gone AWOL/lost interest in this project.
Possibly because he is aware of the newly (2025.1) implemented core backup feature set?

[RubenKelevra]

Following this thread with interest, however it appears that sabeechen has gone AWOL/lost interest in this project.
Possibly because he is aware of the newly (2025.1) implemented core backup feature set?

To be fair it's holiday time. So I wouldn't interpret too much into that. :)

[gfn256]

To be fair it's holiday time. So I wouldn't interpret too much into that. :)

Search his activity on this thread - has not been seen for months.

[sergeykad]

He made 14 contributions already in 2025 according to Github :)
https://github.com/sabeechen?tab=overview&from=2025-01-01&to=2025-01-05

[gfn256]

He made 14 contributions already in 2025 according to Github :)

I said on this thread - HA GDB

[gfn256]

The fact that @sabeechen has not responded to this thread & others of GDB; I think shows that this repo as we know it is being deprecated. (I'm not even sure if he is even following it).

This is a very sad day. I've come to rely on it over the years - and in my opinion was the best ever add-on. It just worked & got the job done. sabeechen got through the hurdles of accessing Google's ecosystem with ease, worked through the kinks when Google Co. made changes along the way, eased us through HA updates when necessary, and in general provided a top-notch helping hand, with a simple, robust & invaluable service. Kudos to him.

I imagine something similar will eventually (when?) be incorporated into the new core backup system - but I have my doubts if it will at all match this top-notch add-on as we know it.

I really would appreciate renewed interest in this repo.