Computers & network

Portainer

portainer

Built inLocal pollingPlatinum

The Portainer integration is used as an interface to the Portainer API. Portainer is a lightweight management UI that allows you to easily manage your Docker containers, images, networks, and volumes. It works on every Docker host or Swarm cluster.

Documentation Source code

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

Entity	Shows up as	Note
`switch`	Switch or outlet
`binary_sensor`	Sensor (motion, contact, leak, smoke…)
`button`	Button (as a switch)

What people report

Portainer integration manages containers via polling; stacks and Edge are unsupported. Recent issues cover false-positive update entities and 403 errors for locally built images.

Not working2
Won’t be supported1

Device	In Home Assistant	What they said	Source
Portainer update entity (traefik:latest)	Not working	False positive image update when registry digest is already in local RepoDigests Saved copy The 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
Portainer with locally built images	Not working	Continuous 403 errors for local images absent from any registry Saved copy The problem the Portainer integration (Home Assistant Core 2026.x), it continuously logs 403 Forbidden errors for locally built Docker images that do not exist in any registry. ### What version of Home Assistant Core has the issue? 2026.8.1 ### What was the last working version of Home Assistant Core? 2026.5.1 ### What type of installation are you running? Home Assistant Container ### Integration causing the issue Portainer ### Link to integration documentation on our website _No response_ ### Diagnostics information Failed to check image debian-monitor:latest on endpoint 3: Connection error … Excerpt saved from GitHub on 2026-10-23.	Issue #179146 · 2026-08
Portainer stacks and Edge computing	Won’t be supported	Stacks and Edge computing not supported Saved copy Limitations: Currently, the integration does not support stacks or Edge computing. Excerpt saved from home-assistant.io on 2026-10-23.	Docs

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Local polling

Talks to the device on your network, asking it for updates every so often.

Details

Installs (analytics)	2,067 (0.29%)
Quality scale	Platinum
Added in	Home Assistant 2025.10
Set up in the UI	Yes
Maintainers	@erwindouna

Limitations from the docs

Currently, the integration does not support stacks or Edge computing.

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.