Need to update components twice

[brhahlen]

System Health details

System Information

version	core-2025.2.3
installation_type	Home Assistant Container
dev	false
hassio	false
docker	true
user	root
virtualenv	false
python_version	3.13.1
os_name	Linux
os_version	6.12.11-200.fc41.x86_64
arch	x86_64
timezone	Europe/Amsterdam
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	4982
Installed Version	2.0.5
Stage	running
Available Repositories	1537
Downloaded Repositories	37

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Dashboards

dashboards	6
resources	25
views	46
mode	storage

Network Configuration

adapters	lo (disabled), eth2 (disabled), eth0 (enabled, default, auto), eth1 (disabled)
ipv4_addresses	lo (127.0.0.1/8), eth2 (172.12.0.3/24), eth0 (172.10.0.5/24), eth1 (172.11.0.3/24)
ipv6_addresses	lo (::1/128), eth2 (), eth0 (), eth1 ()
announce_addresses	172.10.0.5

Recorder

oldest_recorder_run	4 February 2025 at 11:41
current_recorder_run	13 February 2025 at 14:35
database_engine	mysql
database_version	11.4.4

Checklist

• I'm running the newest version of HACS https://github.com/hacs/integration/releases/latest
• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• I have read https://hacs.xyz/docs/help/issues/
• This issue is related to the backend (integration part) of HACS.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This is a bug and not a feature request.
• This issue is not a duplicate issue of currently open or issues pending release.

Describe the issue

I'm not entirely sure when this started, but it seems to be something of this year.
Also not entirely sure where I should look to figure out what goes wrong, as I see nothing in the logs.
Whenever a custom component notices an update, I get the nice little message in HA to update.
I do that, then reboot HA, but then the same popup appears again.
This time, when I do the update and restart HA (by restarting the container), everything works.

Reproduction steps

1. Click update on a custom component
2. Restart HA (recreate the container)

Debug logs

2025-02-13 14:35:24.525 INFO (MainThread) [custom_components.hacs] Starting download, v5.8.0
2025-02-13 14:35:24.526 INFO (MainThread) [custom_components.hacs] <Integration blakeblackshear/frigate-hass-integration> Running pre installation steps
2025-02-13 14:35:24.526 INFO (MainThread) [custom_components.hacs] <Integration blakeblackshear/frigate-hass-integration> Pre installation steps completed
2025-02-13 14:35:24.526 INFO (MainThread) [custom_components.hacs] <Integration blakeblackshear/frigate-hass-integration> Running installation steps
2025-02-13 14:35:25.989 INFO (MainThread) [custom_components.hacs] <Integration blakeblackshear/frigate-hass-integration> Downloading repository archive
2025-02-13 14:35:26.215 INFO (MainThread) [custom_components.hacs] <Integration blakeblackshear/frigate-hass-integration> Content was extracted to /config/custom_components/frigate
2025-02-13 14:35:26.218 INFO (MainThread) [custom_components.hacs] <Integration blakeblackshear/frigate-hass-integration> Installation steps completed
2025-02-13 14:35:26.218 INFO (MainThread) [custom_components.hacs] <Integration blakeblackshear/frigate-hass-integration> Running post installation steps
2025-02-13 14:35:26.218 INFO (MainThread) [custom_components.hacs] Reloading custom_component cache
2025-02-13 14:35:26.221 INFO (SyncWorker_1) [homeassistant.loader] Loaded google_fit from custom_components.google_fit
2025-02-13 14:35:26.221 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration google_fit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.221 INFO (SyncWorker_1) [homeassistant.loader] Loaded audiconnect from custom_components.audiconnect
2025-02-13 14:35:26.221 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration audiconnect which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.222 INFO (SyncWorker_1) [homeassistant.loader] Loaded hacs from custom_components.hacs
2025-02-13 14:35:26.222 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.223 INFO (SyncWorker_1) [homeassistant.loader] Loaded grott from custom_components.grott
2025-02-13 14:35:26.223 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration grott which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.224 INFO (SyncWorker_1) [homeassistant.loader] Loaded teamtracker from custom_components.teamtracker
2025-02-13 14:35:26.224 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration teamtracker which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.225 INFO (SyncWorker_1) [homeassistant.loader] Loaded browser_mod from custom_components.browser_mod
2025-02-13 14:35:26.225 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration browser_mod which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.226 INFO (SyncWorker_1) [homeassistant.loader] Loaded grocy from custom_components.grocy
2025-02-13 14:35:26.226 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration grocy which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.227 INFO (SyncWorker_1) [homeassistant.loader] Loaded postnl from custom_components.postnl
2025-02-13 14:35:26.227 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration postnl which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.227 INFO (SyncWorker_1) [homeassistant.loader] Loaded frigate from custom_components.frigate
2025-02-13 14:35:26.227 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration frigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.228 INFO (SyncWorker_1) [homeassistant.loader] Loaded smartthinq_sensors from custom_components.smartthinq_sensors
2025-02-13 14:35:26.228 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration smartthinq_sensors which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.229 INFO (SyncWorker_1) [homeassistant.loader] Loaded xiaomi_cloud_map_extractor from custom_components.xiaomi_cloud_map_extractor
2025-02-13 14:35:26.229 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration xiaomi_cloud_map_extractor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.230 INFO (SyncWorker_1) [homeassistant.loader] Loaded volkswagencarnet from custom_components.volkswagencarnet
2025-02-13 14:35:26.230 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration volkswagencarnet which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.232 INFO (SyncWorker_1) [homeassistant.loader] Loaded neerslag from custom_components.neerslag
2025-02-13 14:35:26.232 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration neerslag which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.233 INFO (SyncWorker_1) [homeassistant.loader] Loaded tronity from custom_components.tronity
2025-02-13 14:35:26.233 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration tronity which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.234 INFO (SyncWorker_1) [homeassistant.loader] Loaded afvalwijzer from custom_components.afvalwijzer
2025-02-13 14:35:26.234 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration afvalwijzer which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-13 14:35:26.234 INFO (MainThread) [custom_components.hacs] Custom_component cache reloaded
2025-02-13 14:35:26.235 INFO (MainThread) [custom_components.hacs] <Integration blakeblackshear/frigate-hass-integration> Post installation steps completed

Diagnostics dump

config_entry-hacs-31a509aeb5d1c818fffae8e4071de4b3.json

[hacs-bot]

Make sure you have read the issue guidelines and that you filled out the entire template.

If you have an issue identical to this, do not add comments like "same here", "i have this too", instead add a 👍 reaction to the issue description. Thanks! 👍

[ludeeus]

HA is writing the HACS metadata on HA shutdown, make sure you are not killing the container to allow for HA to finish shutdown tasks.

[brhahlen]

HA is writing the HACS metadata on HA shutdown, make sure you are not killing the container to allow for HA to finish shutdown tasks.

When restarting, I do a docker compose stop homeassistant; docker compose rm -f homeassistant; docker compose up -d homeassistant
So I would not expect that to kill the container.

[ludeeus]

It depends on how much time you allow during stop..
Restart in the HA UI and all should be good.

[brhahlen]

It depends on how much time you allow during stop.. Restart in the HA UI and all should be good.

I'll give that a shot on a next update.

Weird thing is that it used to work fine this way...
AFAIK, the stop command should wait for the container to shut down cleanly (I have a number of containers where it takes some time to do this). Maybe HA is not reporting the shutdown properly?