Is new system backup forgetting to backup local addons?

Configuration
1

Seems the new backup system isn’t including addons_local.tar.gz for me. Do your backups include it?

Here’s a backup from Jun 12th, 2025:

 $ tar -vtf 24f64650.tar | grep addons
 -rw-r--r-- 0/0           25650 2025-06-12 03:01 addons_local.tar.gz

addons_local.tar.gz contains the /addons directory, used for local add-ons.

That is no longer in my automatic backups. I just created another backup turning everything on:

image
image1120×992 54.7 KB

Which generated this:

  /backup ls -lt *.tar | head -1
-rw-r--r--    1 root     root     697507840 Jan  2 17:48 test2_2026-01-02_17.48_44073828.tar

➜  /backup tar -vtf test2_2026-01-02_17.48_44073828.tar | grep local
-rw-r--r-- 0/0   3830252 2026-01-02 17:48:47 local_zwavejs2mqttlr.tar.gz

That’s the add-on created by the local addons config. But the actual config to generate that addon is not backed up.

There are other posts where you can see that local_addons.tar.gz file used to be included.

2

By the way, this is what clued me in on the issue. After restoring on a different machine I got this repair:

image
image1468×886 84 KB

I don’t want to uninstall the add-on. The I manually restored the local add-on config to the /addons directory and restarted.

How do I remove the repair issue? Is there someplace they are stored I can modify?

3

I just started programming few custom addons and wanted to check if the addons folder is included in backup process or whether I should make the “addons” folder a repository and keep pushing the changes offsite.
Thanks for this report - I now see they are supposed to be backed up but they are not… I hope this bug will be resolved quickly.

4

The automatic backup system only creates one file. It does not create mutliple separate backup files. I.e. The single file that is created will have your addon backups in it.

5

Have you checked the UI? My local add-ons are included in the “Select what to restore” list, so they’re there somewhere… :grin:

6

This is about the /addons directory, which is the config for building custom addons/apps.

@petro , yes it creates a single tar file – which includes a number of gzipped files. The issue is the /addons folder is no longer being backed up. That folder contains the config for the local addons and used to be part of the stanard backups (see my first post). @RedKing , see the image above where Addons were selected in the backup.

There’s more details in the github issue.

In my post above I didn’t show the full contents. Notice here that besides the individual local addons there’s the addons_local.tar.gz file:

$ tar -vtf 24f64650.tar
-rw-r--r-- 0/0       702418444 2025-06-12 03:00 homeassistant.tar.gz
-rw-r--r-- 0/0            2465 2025-06-12 03:00 5c53de3b_esphome.tar.gz
-rw-r--r-- 0/0           14389 2025-06-12 03:00 cebe7a76_hassio_google_drive_backup.tar.gz
-rw-r--r-- 0/0           11859 2025-06-12 03:00 a0d7b954_ssh.tar.gz
-rw-r--r-- 0/0            2674 2025-06-12 03:00 core_mosquitto.tar.gz
-rw-r--r-- 0/0            5211 2025-06-12 03:00 03cabcc9_ring_mqtt.tar.gz
-rw-r--r-- 0/0        21558070 2025-06-12 03:00 a0d7b954_zwavejs2mqtt.tar.gz
-rw-r--r-- 0/0        36445587 2025-06-12 03:00 local_hello_world.tar.gz <= addon
-rw-r--r-- 0/0         3001301 2025-06-12 03:00 local_zwavejs2mqttlr.tar.gz <= addon
-rw-r--r-- 0/0             229 2025-06-12 03:01 ssl.tar.gz
-rw-r--r-- 0/0         1498345 2025-06-12 03:01 share.tar.gz
-rw-r--r-- 0/0           25650 2025-06-12 03:01 addons_local.tar.gz <= the /addons directory
-rw-r--r-- 0/0            1429 2025-06-12 03:01 ./backup.json

I moved my custom addon onto another machine, and using a different approach to bring that addon’s data into HAOS to be included in my scheduled backups.