homeassistant-portainer icon indicating copy to clipboard operation
homeassistant-portainer copied to clipboard

[Bug] all Endpoints shown offline if one Endpoint is offline

Open Ajimaru opened this issue 10 months ago • 6 comments

Describe the issue

HA shows both Endpoints as offline if one Endpoint is offline.

How to reproduce the issue

Steps to reproduce the behavior:

  1. Shutdown one Endpoint, here the Endpoint "PBS": Bildschirmfoto 2024-04-01 um 09 33 27

  2. Click on Portainer Card: Bildschirmfoto 2024-04-01 um 09 34 07 Bildschirmfoto 2024-04-01 um 09 13 15 Bildschirmfoto 2024-04-01 um 09 13 04

  3. Start the previously stopped Endpoint: Bildschirmfoto 2024-04-01 um 09 12 21 Bildschirmfoto 2024-04-01 um 09 12 46

Expected behavior

HA Portainer integration shows only the offline Endpoint as offline.

Screenshots

Software versions

  • Home Assistant version: Core 2024.3.3 Supervisor 2024.03.1 Operating System 12.1 Frontend 20240307.0

  • Portainer integration version: v1.0.2

  • Portainer software version: Endpoint Homeserver 24.0.5 Endpoint PBS 25.0.3

Diagnostics data

Traceback/Error logs

Additional context

The second integration is on another system, witch is online only every 3 days.

Ajimaru avatar Apr 01 '24 07:04 Ajimaru

I also see all my sensors as Unavailable. Not sure if this is the reason why, but have tried all the usual remediations, including rebooting, uninstalled and reinstalled the plugin, and generating a new API key.

uberoptix avatar Apr 02 '24 21:04 uberoptix

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

github-actions[bot] avatar Apr 17 '24 01:04 github-actions[bot]

@tomaae any sugesstions?

Ajimaru avatar Apr 17 '24 10:04 Ajimaru

Experiencing the same issue at the moment. In preparation of a move I have shut down one of my Portainer servers already. Now everything shows as unavailable within Home Assistant.

pdsccode avatar Jun 18 '24 21:06 pdsccode

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

github-actions[bot] avatar Aug 09 '24 01:08 github-actions[bot]

Experienced the same issue and found a fix.

mhosse avatar Aug 16 '24 14:08 mhosse

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

github-actions[bot] avatar Aug 31 '24 01:08 github-actions[bot]

bump

mhosse avatar Sep 05 '24 18:09 mhosse

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

github-actions[bot] avatar Sep 20 '24 01:09 github-actions[bot]

This issue was closed because it has been stalled for 5 days with no activity.

github-actions[bot] avatar Sep 27 '24 01:09 github-actions[bot]