2025.2: Iterating on backups

I did exactly this.

It’s showing up for me, maybe wait a bit for it to appear. Otherwise you can update via CLI if you like. It was not pulled and it’s still listed in stable

1 Like

My Google Calendar integration also seems to have broken with this release. Were you able to find any solution for your issue? I just rolled back to 2025.2.1 in the meantime since it was a pervasive issue affecting a large number of my automations, but if we need help diagnosing the issue, I can reapply the change and see what additional details I can dig up.

I am also having the Google Calendar issue. I saw that it might have something to do with an incompatibility between it and the custom Roborock integration (which I use), but I haven’t tested it yet on my side.

Interestingly, sometimes if I restart HomeAssistant, the Google Calendar integration will load, and sometimes it won’t.

something is definitely going on with the DB since january update.

mine was stable around 50ish MB in december, slowly (very slowly) growing because LTS, gained maybe 7-10MB since january 2024 (to give you the growth rate), didn’t changed a thing to my recorder (configured in “include” mode) config nor added devices.

suddenly it’s almost 100MB. almost double size in 2 weeks !!

haven’t dived into sql to investigate WHAT is inflating as i don’t have time at the moment.

Anyone experiencing slowness with 2025.2.2?

After updating it’s been extremely sluggish in general.

Struggling to pinpoint why

1 Like

The flow you are hoping for is a Home Assistant Cloud Account Linking flow. Despite the name, that does not require subscription, and is a free service used by a number of integrations. That approach maintains global clients, rather than requiring users to set up their own. The net result is the normal redirect-based authorization flow for granting access to some aspect of your account.

It is not immediately clear why they have not set this up for Google services. My guess would be because some of the Google integrations (like the Google Sheets integration) use scopes considered “sensitive” or “restricted”. Apps that use these scopes cannot have more than 100 users unless they jump though a bunch of hoops, including a yearly CASA Tier 2 security assessment which has some not insignificant costs. This does not apply for a project whose clients only need non-sensitive scopes, like these backups, but they would probably want to be able to support all the Google APIs in the same way, and that has costs and a bunch more work.