Portainer
Portainer update entity (traefik:latest)
Routers · And More
Not working
1 report: 1 says it doesn’t work.
Reported with 1 integration: Portainer.
What people report
| Integration | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Portainer | Not working | False positive image update when registry digest is already in local RepoDigestsSaved copyThe problem The Portainer integration reports an image update as available even though the current registry digest is already associated with the exact local Docker image used by the running container. In my case, the container uses `traefik:latest`. Home Assistant reports: installed_version: sha256:1c32e7c368204fd72812152ebdd2ac0425993df6fd982317deb02e48f2d5423c latest_version: sha256:24841fe2de7304c149343d877d2923b4c8800a38ba015dea9174c23b20e344a0 and the update entity remains `on`. However, Docker shows that the local `traefik:latest` image has both RepoDigests associated with the same … Excerpt saved from GitHub on 2026-10-23. | Issue #182911 · 2026-09 |
Each row is one report from a GitHub thread, an integration’s docs, or r/homeassistant. Check the date and the linked source before you buy.
In ReReHome
Once Home Assistant’s HomeKit Bridge shares it, this device reaches Apple Home as a HomeKit accessory behind your Home Assistant bridge, so ReReHome shows and controls it like any other.
Identifiers
| Brand | Portainer |
|---|---|
| Category | Routers |