#Backup integration no longer working since switching from HA supervised to HA container

1 messages · Page 1 of 1 (latest)

topaz ember
#

Since the 2025.6 update, and the subsequent deprecation of the core and supervised installation methods, I decided to migrate my current home assistant setup from the supervised installation method, to the container installation method. As suggested in https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/#how-to-migrate, I made a backup, downloaded said backup, then restored it during the initialization of the new system.

This has worked great, with the exception of the backup integration. When checking the integration in the Integrations, it shows a yellow warning triangle with an exclamation sign, and text indicating it is not loaded. Clicking the integration and then "ADD SERVICE" will result in the following error message:

This integration cannot be added from the UI
You can add this integration by adding it to your 'configuration.yaml'. See the documentation for more information.

I did as a matter of fact check configuration.yaml, but I don't see any relevant section there and I'm hesitant to just randomly starting to edit the yaml when the documentation indicates this should be possible to edit from the UI.

Home Assistant
Deprecating Core and Supervised installation methods, and 32-bit sy...

This deprecation will help focus support efforts and streamline development.

weak breach
topaz ember
#

Sorry for not specifying, but I am indeed talking about the core backup integration. It is labeled as "Internal integration". And the YAML file does indeed contain the line "default_config:"

weak breach
#

ok awesome, just checking some of the basics.
is there anything in the logs that give a hint?
you could also try restarting home assistant in safe mode which disables some stuff and see if it loads there?

topaz ember
#

Logger: homeassistant.setup
Source: setup.py:256
First occurred: June 15, 2025 at 12:34:05 (3 occurrences)
Last logged: June 15, 2025 at 12:34:08

Unable to set up dependencies of 'backup'. Setup failed for dependencies: ['hassio']
Unable to set up dependencies of 'cloud'. Setup failed for dependencies: ['backup']
Unable to set up dependencies of 'default_config'. Setup failed for dependencies: ['cloud']

weak breach
#

how did you set up container?
if with docker? can I see your compose file?

topaz ember
#

I used docker indeed and ran the command listed in the installation instructions, that is to say

docker run -d
--name homeassistant
--privileged
--restart=unless-stopped
-e TZ=Europe/Lissabon
-v /opt/homeassistant/config
-v /run/dbus:/run/dbus:ro
--network=host
ghcr.io/home-assistant/home-assistant:stable

#

But I suppose it might be good to switch to docker compose, let me try that

weak breach
#

i feel like something is up with the container setup

topaz ember
#

Could be. I just created an empty folder for it in /opt, then ran the command as listed in the installation manual

weak breach
#

your command is not right

topaz ember
#

Oh?

weak breach
#

-v /opt/homeassistant/config \
-v /opt/homeassistant:/config \

topaz ember
#

Ah

#

Sorry I just copied pasted from the site, not my actual command history

#

It is correct there

#

To be specific

weak breach
#

I recommend switching to a compose setup instead anyway

topaz ember
#

Yes, just finished the switchover

#

Which actually fixed the issue

#

Interesting

#

I wonder if the option is not available when not using docker compose and the documentation just fails to mention this? It somewhat makes sense, because not using docker compose means it is a bit more... temporary in terms of how it is setup

#

Now I'm not sure whether this is a bug, or a documentation issue

#

Or maybe a config error on my end

weak breach
#

i feel using compose should be the recomended thing tbh, the command version can be a bit of a pain at times

#

was probably some config issue somewhere on your end but something not obvious

topaz ember
#

Mmm yeah, agree with you on that, as it does automatic restart on failure or system boot, so docker compose definitely is the way to go

#

Guess I'll contact the documentation team anyway, alert them to this issue, and discuss whether the documentation should be changed to have compose as first instructions instead of the way it's handled currently

#

Guess I could also give it a go on another system to see if this is reproducable

weak breach
#

ill mention it to people

topaz ember
#

Ah, I see you're a dev

#

Want me to still try to reproduce on a clean system?

weak breach
#

dev is a strong term for me but yeah i can easily mention to people

#

you can if you want to. and document everything. if same issue and we cant get to the bottom of it can open an issue with all the notes

topaz ember
#

Will do!

topaz ember
#

Alright, tested it on a clean system, and the issue was not reproducible

#

So it seems to have been some config error on my part after all

weak breach
#

cool, yeah most likely a typo somewhere or something

topaz ember
#

I suspect it might be because I ran a pull to update it without sudo - maybe that messed something up somewhere

#

Or a typo, very possible

weak breach
#

I have floated the idea of making compose more recommended in any case. i am not sure anyone cares enough though tbh

topaz ember
#

Will mark this as resolved