Why wasn't that encrypted backup thing a red letter warning?

1

I never would have installed the update if I read this breaking change. Super-bad mistake, please undo it. I already stored my backups as securely as I wished to.

2

until you have a proper solution, I suggest you to take a look at Home Assistant Google Drive Backup, it is still using old method, unencrypted backups. Maybe you can evade uploading it to the drive

2 Likes
3

Or wait until next week.

2 Likes
4

If I uploaded it to a free cloud service, I probably would want to encrypt my backups. For now I’ll just live dangerously, I guess.

5

Why living dangerous? Backup in Automations using action “hassio.backup_full” is still unencrypted, same for action “hassio.backup_full” in core installations.
And release 2025.2 next week addresses this too, check the beta release notes.

1 Like
6

Didn’t even know that existed. I’ve only been doing manual backups. And odds are, knowing myself, I won’t research how to use it and will just wait if a fix is coming.

7

As already stated., don’t use the new stuff id you don’t know what it does, or wait…
2025.2 Beta Backup changes.
But there is this available as well.
Alternatives to Automatic Backups. Ways to do it yourself

8

That’s really only about one step removed from “Told you so.”

Also, I hadn’t been used to the core team breaking (non-beta) stuff recently. Serves me right for being too trusting. I suppose it’s wise to go back to waiting a month for so after a new release comes out before installing.

But again, no excuse for no big warning.

9

I think it was mentioned here somewhere.

10

We have very different definitions of by default.

11

In addition to an omission in the release notes, there’s another bug introduced in the backup in terminal.

I had to resort to backing up in the CLI from the terminal on my RPi to save my HA from failing SD, and I found that ha backups info doesn’t work anymore without an argument. It used to list the backups it found with their relevant info, but now only works if you give it a valid slug. So listing existing backups requires going into the directory where they’re stored in terminal or a file manager.

[core-ssh ~]$ ha backups info
Error: accepts 1 arg(s), received 0
Usage:
  ha backups info [slug] [flags]

Aliases:
  info, in, inf

Examples:

  ha backups info c1a07617

Flags:
  -h, --help   help for info

Global Flags:
      --api-token string   Home Assistant Supervisor API token
      --config string      Optional config file (default is $HOME/.homeassistant.yaml)
      --endpoint string    Endpoint for Home Assistant Supervisor (default is 'supervisor')
      --log-level string   Log level (defaults to Warn)
      --no-progress        Disable the progress spinner
      --raw-json           Output raw JSON from the API

FATA[0000] Error while executing rootCmd: accepts 1 arg(s), received 0 
[core-ssh ~]$

I get this error in CLI on the RPi itself or SSH-ing into it. The --help option still says that the arguments are optional, and it worked as described in the help in the previous version.

[core-ssh ~]$ ha backups info --help

When a Home Assistant backup is created, it will be available for restore.
This command gives you information about a specific backup.

Usage:
  ha backups info [slug] [flags]

Aliases:
  info, in, inf

Examples:

  ha backups info c1a07617

Flags:
  -h, --help   help for info

Global Flags:
      --api-token string   Home Assistant Supervisor API token
      --config string      Optional config file (default is $HOME/.homeassistant.yaml)
      --endpoint string    Endpoint for Home Assistant Supervisor (default is 'supervisor')
      --log-level string   Log level (defaults to Warn)
      --no-progress        Disable the progress spinner
      --raw-json           Output raw JSON from the API
[core-ssh ~]$