CHANGELOG 1.14.4 Security Fixes Build chain certificate update for eMudhra intermediate ca certs issue Container rebuilt with latest uv version and os ca-certificates for eMudhra issue CI workflow now has a docker container integration test 1.14.3 Portainer Wait for the stack deployment to complete, using the stack’s deployment status, rather than treating Portainer accepting the redeploy request as success. Portainer 2.41+ now deploys in the background, so a failed deployment was previously reported as a successful update. Failures now log Portainer’s error message, and a redeploy requested while another deployment of the stack is in progress waits for that to finish first Added dind test framework to automate integration testing for compose and portainer 1.14.2 Configuration A default config.yaml is no longer auto-generated when MQTT_USER and MQTT_PASS are set as env vars, since the env vars already fully describe the config. Set U2M_AUTOGEN_CONFIG=1 to generate it anyway Fixes After an update, Home Assistant could keep showing the old installed version until the next scan or a restart of Updates2MQTT, most likely when updating via Portainer, where the redeploy can return before the container is recreated. The post-update rescan now waits (up to 60s) for the container to be running the newly pulled image before republishing its state 1.14.1 Portainer PORTAINER_CA_CERTS env var, or ca_certs in config, to verify Portainer with a private root CAPORTAINER_VERIFY_SSL env var, as alternative to verify_ssl in config Docker Optionally remove the replaced image after a successful update, using remove_old_image in config or U2M_REMOVE_OLD_IMAGE env var CLI mqtt=check also reports the update and Portainer settings, with the env var each comes from, and checks the Portainer ca_certs file exists Fixes When PORTAINER_API_KEY or PORTAINER_URL were set, an auto-generated config file copied their values into config.yaml, rather than referencing the env vars as for MQTT settings Without a Configuration File docs listed MQTT_PASSWORD rather than the correct MQTT_PASS env var Docs README and translations updated for Portainer support and old image removal 1.14.0 Portainer Initial API support for Portainer is provided, to bring it up to a similar level of functionality to the Docker Compose Instructions and limitations at Portainer Configuration This is in Beta at present, so use with caution, and feedback where you have issues Internal Automated testing on every build extended to Py3.15, and backwards to Py3.14 Omegaconf restricted to <2.4.0 as new release broke many tests. Reviewing use of pydantic instead for config before embarking on upgrade for omegaconf (project has been moribund since 2022) 1.13.0 Compose Compose project name now passed with -p when restarting or building, so projects whose name differs from their directory are recreated in place rather than duplicated can_restart now only reported when the compose working directory is actually visible inside the Updates2MQTT containerNew compose_path_found and compose_project attributes in MQTT installation_detail, and a warning logged when the compose directory can’t be seen Portainer Portainer stacks detected from their /data/compose/<id> working directory, with a portainer_stack_id attribute added Containers in Portainer stacks can now be updated from Home Assistant, by redeploying the stack through the Portainer API ( #18 ) Configure with PORTAINER_URL and PORTAINER_API_KEY env vars, or a docker.portainer section in the config file Images are pulled locally first, and the redeploy doesn’t pull, so only the updated containers are recreated Web editor and Git stacks supported, Portainer itself and its agents are excluded 1.12.0 MQTT TLS More MQTT configuration available as environment variables MQTT_TLS_MODE ( on,off or insecure)MQTT_TRANSPORT ( tcp, unix or websockets)MQTT_CERT_REQUIRED ( CERT_REQUIRED, CERT_OPTIONAL, CERT_NONE ) CLI Debug CLI script renamed from cli to u2m-cli, so it can be installed with uv tool install updates2mqtt CLI with no arguments now shows help instead of trying to look up a frigate container, and a Docker connection failure gives a one line error rather than a stack trace New mqtt=check CLI command to show MQTT settings (without secrets) and test the broker connection Fixes Rejected MQTT credentials at startup no longer wait for the full connection timeout 1.11.1 Fixes Fix for #175 (OCI_V2 lookup never finds an update for single-platform images without an image index) OCI_V2_MINIMAL mode now fixed CLI fixed for case sensitive API names Tag responses could be over-cached, registry mutable_cache_ttl now defaults to 1 hour Older caches entries will persist until cache directory cleaned out Image creation time now read correctly from OCI image config Python 3.13 compatibility issue found in config validation and resolved Internal Minor dependency update Documentation site generation switched from mkdocs to ProperDocs ty now also used for type checking, and minor type fixes made 1.11.0 MQTT TLS ca_certs is now optional for TLS, so can default to built-in certificate authorities where broker has a public verified certtls_mode can be on,off or insecureTLS keyfile password can be set using client_key_password in config or MQTT_CLIENT_KEY_PASS env var MQTT Transport The default tcp transport can now be overridden by using transport in MQTT configuration, for either websockets or unix Internal Minor dependency update Upgraded ruff to 0.16.0 and enabled its huge number of new checks in that version, fixing minor issues identified 1.10.0 TLS support for MQTT brokers Password is no longer mandatory, to support client-cert auth, or no-auth Node name now defaults to $NODE_NAME if set, where no node name in config, failing which back to os.uname() as before Updated common Docker images, including Valkey, OpenClaw and Vaultwarden Dependency refresh 1.9.7 Reduce MQTT login churn where broker keep alive <= client keep alive Add configurable MQTT keep alive, defaulting to 30 secs (previously hardcoded to 60s) Moved connection log line back to debug MQTT QoS changed to 1, so queued messages are resent if there is a disconnect. QoS logged. 1.9.6 MQTT now has a connect_timeout defaulting to 10 seconds, and will wait for this before attempting to publish scan updates Drop duplicate update commands when update for that component already in hand 1.9.5 Dependencies update Additional common packages added for logos and repos, including MariaDB and Redis Cache age stats easier to understand Common packages can have a list of image names Improve self-bounce behavior, allow more time for command to complete before exit Clean up lingering in progress state from previous update Replace TaskGroup with simpler await usage so MQTT updates appear as they happen rather than in bulk at end of scan 1.9.4 More defensive access to linuxserver.io docker image info to handle missing fields, prompted by changes to HomeAssistant image in early May 2026 Better defensive data access on registry manifests, versions, labels, annotations Improved test coverage 1.9.3 Logging New option to emit JSON structured logs when running as server (not attached to terminal) Fixed stacktrace logs on server having rich library’s box drawing special chars Loggers cached as per structlog best practice, and colour switched off for headless tty 1.9.2 Fix handling of expired Github access token 1.9.1 Translations for Dutch, French, German, Hindi, Italian, Japanese, Polish, Portuguese, Simplified Chinese and Spanish Vertalingen voor Nederlands, Traductions en français, Übersetzungen auf Deutsch, हिंदी में अनुवाद, Traduzioni in italiano, 日本語の翻訳, Tłumaczenia po polsku, Traduções em português, 简体中文翻译 en traducciones al español 1.9.0 Use the GitHub package versions API for GHCR images without a valid tag in image CLI improved to allow single container dump Github API now has its own cache_ttl config Refactor GitHub API code to separate module 1.8.5 Initial clean of MQTT topic on startup to remove any hanging in-progress status Default max summary size now 6K Truncation now logged 1.8.4 Release Info Default max summary size now 8K, to avoid Home Assistant warnings on state This limit can be increased, or removed, if the Update entities are excluded from Home Assistant’s state history 1.8.3 Release Info Release summaries can now have a max length, using release_summary_max_size, default 16k 1.8.2 Version Detection Tighten up auto and fallback rules for cases where digests don’t match Use versions in tag where they are SemVer or casual versions CLI Added dump=csv, dump=json and help commands Common Packages Added EMQX, Mosquitto, Plex, Emby, Tailscale, AppWrite, Traefik, Grafana, Prometheus, WhatsUpDocker, Lychee and HomeAssistant 1.8.1 Home Assistant Re-publish state every scan to ensure fresh Main discovery and state message now better in sync on in_progress flag State not published during update if Home Assistant mode off Version Detection Version Policy now includes TIMESTAMP for image creation date/time, which is also now part of auto version algorithm Version policy can be also be set in custom_packages.yaml or in the packages section of config Detect common mis-configuration where ubuntu base layer version published as derived image version MQTT MQTT result code, MID and publish status logged at debug, and at warning if non-success result code 1.8.0 Package Info The common_packages.yaml that ships inside the Docker image can be extended, or overridden, using the packages section of the main config file Source platform will be inferred, and verified, for GitHub, Gitlab, Quay, LSCR and Codeberg Release Notes If the component tag doesn’t match the release tag (e.g. 1.7.3 vs v1.7.3), an alt lookup will be made on latest github released, and used if the tag name on that release matches the expected tag, with a common v,V,r or R prefix A GitHub personal access token can now be added in the github: config section, which will increase number of API calls that can be made for release info before being throttled Release notes can be better guessed, subject to URL validation, for Gitlab and GitHub CLI Logging improved, with different default for container lookup, so there’s always some output from commands Added a tags option to retrieve list of known tags in the registry Housekeeping MQTT topic clean overhauled - Now runs only after scan Checks topics against current discoveries vs previous session key based check 1.7.3 Minor fix for stats reporting 1.7.2 API Stats OCI v2 API client maintains api stats per host, and errors per status code, with a cache hit ratio and avg elapsed time Container Registry Checks The Config document is now also pulled in, which means more images have annotations, nice versions and release notes OCI_V2_MINIMAL option to make only the calls needed for version checksDiagnostic code now distinguishes two ways that different digests are checked between old and new Stats now tallied for all registry URL calls, and periodically logged CLI Fixed issues with docker.io fetches Colourful and jq friendly JSON output Log level now defaults to WARNING to make it easier to pipe results to jq, can change to see headers using log_level=DEBUG 1.7.1 No code change, version changed to fix a pypi publish issue 1.7.0 py3.14 Image now built with python 3.14 by default Tests update for py3.14 mock async changes OCI Container Registry APIs By default now uses the OCI v2 Distribution APIs rather than old Docker APIs via Docker SDK Older method can be switched back on using docker.registry.api: docker_client configuration Container registry also used where available to pull in annotations ( including a meaningful version ) using the OCI Distriubtion API Docker, GitHub GHCR, Gitlab, LSCR, Microsoft MCR and Codeberg configured Authentication logic to automatically adapt and retry dynamically for other platforms Annotations will be sourced from the Index or Manifest, with priority for the (platform-specific) manifest Digest matching adapts to different practices across repos Registries can now be selectively included/excluded using registry_select in Docker configuration section GitHub Release Enrichment Where an annotation points to a source URL and hash, this can be used to derive a diff_url, a direct link to the actual release notes, and a release summary pulled from the Github source repo releases and passed onto Home Assistant A token can be provided, e.g. a Personal Access Token, at container level using UPD2MQTT_REGISTRY_TOKEN Common packages now have a source_repo_url and don’t need a release notes URL too if on GitHub Version Policies Version policies available to make use of meaningful versions from annotations AUTO will detect what looks like a SemVer and report only the meaningful version to HAVERSION,DIGEST and VERSION_DIGEST can be used to fix on which fields to useIf the chosen option isn’t available, next preference is for version:digest qualified version, falling back to whatever else is available Version policy can be set at container level using UPD2MQTT_VERSION_POLICY env var or corresponding label Version selection now has a diagnostic code, version_basis, that ties back to precisely which code used Local Docker Image Enrichment Metadata from local org.opencontainers labels published where available Added more packages to common-packages, vector and greptime Selective Home Assistant Discovery New version_select option in Docker config works like image_ref_select using the reported version instead Pinned Digests Better handling of tags with a pinned digest, e.g. ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:41eacbe83eca995561fe43814fd4891e16e39632806253848efaf04d3c8a8b84 API Throttling Throttling fixed for TTL taken from remote API Docker provider shuffles the list of containers it scans so if there is aggressive throttling there isn’t the same set of containers always getting scanned before the rate limit hits Caching Index and Manifest local cache age now reported on MQTT message Additional logging and defaults for caching Local cache TTL override can be removed by using None for cache_ttl in registry config 1.6.0 MQTT Topics Separated out generic and Home Assistant specific topics The State , Command and Discovery topics are strictly Home Assistant schema The full discovery attributes are now published on their own topic This can also be supplied as additional attributes to the Home Assistant Update entity These can be turned off using the extra_attributes flag in homeassistant config Selective Home Assistant Discovery New image_ref_select option in Docker config List of include strings or regular expressions, containers which don’t match these won’t be Home Assistant discoverable List of exclude strings or regular expressions, containers which match these won’t be Home Assistant discoverable Containers not selected because of image_ref_select can still have an Auto update policy, so will be updated but not visible to Home Assistant Docker Labels Container customization can now be made by Docker labels instead of, or in addition to, env vars API Throttling Docker API now throttled per registry if receives 429 Too Many Requests Uses retry_after header value, if missing or unreadable defaults to configurable default_api_backoff Local Builds General overhaul of some issues and improvements for local git repo image builds Version now synthesized in place of image version git:<short sha> for current versiongit:<short sha>+<commits behind> for latest version Auto update policy restricted to when there’s an update to build For local git repos, install available check made now at discovery time Install update in HA only appears if there’s a pull available Internal Many more test cases added, focusing on Docker and MQTT integration Self-bounce now recognized and attempts to set exit code to 1, though container may still override that 1.5.2 Internal Build backend changed to uv_build GitHub Actions workflows updated, including to new uv actions 1.5.1 MQTT_VERSION environment variable added, defaults to 3.11U2M_AUTOGEN_CONFIG environment variable added to control auto-generation of config files and directoriesU2M_LOG_LEVEL environment variable added to set log level without config fileTitle generation for Docker images reverts to same whether HA device set or not Test added to ensure component always functions without a config file, if no env var present 1.5.0 Target specific service on docker compose commands, where available from com.docker.compose.service label Log level in config is now an enum, and forced to be upper case Removed unnecessary latest_version fields from config message, which also saves a redundant MQTT subscription Publication of command_topic for each discovery can now be forced with force_command_topic option More common packages: docker:cli Common packages can now match on the image ref rather than base name, for example docker:cli Reduced log noise in INFO and increased logging detail for DEBUG Common Packages now allow entries without all the values, initially rtl_433 which lacks a logo 1.4.2 Replace origin in config MQTT message with device for better HomeAssistant compatibility An area can be defined in the Home Assistant section of config and this will then be used as suggested_area for device Icon and release note info added for Owntone, Nextcloud, n8n, and Homarr More testcases 1.4.1 More logging for Docker discovery on why Home Assistant doesn’t show an update button More test cases MqttClient is now MqttPublisher to avoid confusion with actual MQTT clientTask cleanup now only interrupts explicit list of tasks - healthcheck and discovery tasks 1.4.0 MQTT protocol can now be set, to one of 3.1,3.11 or 5 Debug messages now provided for on_subscribe and on_unsubscribe callbacks Troubleshooting, installation, configuration docs updated, images optimized 1.3.7 Improved initial setup when run without config or env vars for MQTT Minor test deps update and pyproject docs 1.3.6 Changed exit code on graceful shutdown to 143 App now exits if the MQTT username / password is not authorized Improved handling of env vars, default config now assumes MQTT_HOST etc unless overridden Will now run without a config if correct MQTT_HOST,MQTT_USER,MQTT_PASS,MQTT_PORT env vars set or match the defaults (127.0.0.1:1883) Deps update