[Copilot]

Containers with auto-update enabled briefly showed up as "updatable" in the HA settings while the background update was running. Users could not tell an update was already in progress and might trigger it manually.

• Coordinator (coordinator.py)

  • _async_fetch_data now reports update_available: False to the update entity when an auto-update is about to run. Auto-update runs when updates are detected, auto-update is enabled, no auto-update is already in progress, and docker_create is available on the host.
  • The update_available attribute on the container entity still shows the real value.
  • The existing recreating pending state is unchanged.
  • The auto-update trigger condition is unchanged. It still runs when docker_create is missing, which logs a warning and attempts nothing.

• Failure behavior

  • After the recreate attempt, the coordinator refreshes with _in_auto_update still set, so the real state is reported. If the update failed, the entity returns to updatable.
  • If docker_create is missing on the host, the update stays visible throughout, because nothing can be installed in the background.
  • That refresh does not retry the auto-update. A later poll retries it, and the entity is hidden again while the retry runs.

auto_update_due = update_available and options.get(CONF_AUTO_UPDATE, False) and not self._in_auto_update
auto_updating = auto_update_due and docker_create_available
...
"update_available": update_available and not auto_updating,

• Fixes bug: Updates for Docker containers with auto-update shown as "updatable". #94