Skip to content

Add better pause behaviour to Portainer#167453

Merged
joostlek merged 1 commit into
home-assistant:devfrom
erwindouna:portainer-better-pause-behaviour
Apr 6, 2026
Merged

Add better pause behaviour to Portainer#167453
joostlek merged 1 commit into
home-assistant:devfrom
erwindouna:portainer-better-pause-behaviour

Conversation

@erwindouna
Copy link
Copy Markdown
Member

@erwindouna erwindouna commented Apr 5, 2026

Breaking change

Proposed change

Adds better pause behaviour to Portainer. Meaning the power on/of switch can still be used once paused, as well as getting stats whilst paused. For instance, the memory isn't cleared in a paused state.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes Improve paused containers #167446
  • This PR is related to issue:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend pull request:

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Portainer integration to treat paused containers as “on” so entity state and coordinator behavior better match Docker/Portainer semantics.

Changes:

  • Add paused to ContainerState.
  • Update the container switch “on” logic to consider both running and paused containers as on.
  • Include paused containers when selecting which containers to fetch stats for.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
homeassistant/components/portainer/switch.py Treat paused containers as is_on for the container switch.
homeassistant/components/portainer/coordinator.py Fetch container stats for paused containers in addition to running ones.
homeassistant/components/portainer/const.py Add PAUSED to ContainerState.

Comment thread homeassistant/components/portainer/switch.py
Comment thread homeassistant/components/portainer/coordinator.py
@joostlek joostlek merged commit 34dc52c into home-assistant:dev Apr 6, 2026
36 of 37 checks passed
Copy link
Copy Markdown
Contributor

@jtjart jtjart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR got closed before I finished the review. But I thought those comments could improve the code in the future, so I will simply post them. 😄

@@ -216,7 +216,8 @@ async def _async_update_data(self) -> dict[int, PortainerCoordinatorData]:
running_containers = [
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The name could be misleading as there are not just running containers. Maybe renaming it to active_containers would be better.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree. With the current state it's probably a better definition.

Comment on lines 21 to +22
RUNNING = "running"
PAUSED = "paused"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As you are also the owner of the API, you could add an enum to the API, which represents all possible states according to the API's documentation.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, I'll add this on a bit later. :)

@erwindouna erwindouna mentioned this pull request Apr 6, 2026
21 tasks
@github-actions github-actions Bot locked and limited conversation to collaborators Apr 7, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve paused containers

4 participants