You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have multiple containers shown as sensors, and most of them are unavailable and could only be deleted manually - the problem is that I noticed it late and now I have ~1400 sensors listed in HA and it slows things down a bit.
To be clear: this is connected to Portainer with 2 docker standalone environments and running around 30 containers - definitely not in the thousands.
How to reproduce the issue
🤷♂️
Expected behavior
Containers as sensors don't get duplicated
Screenshots
Software versions
Home Assistant version: 2024.1.3
Portainer integration version: V1.0.2
Portainer software version: 2.19.4 BE
Diagnostics data
🤷♂️
Traceback/Error logs
🤷♂️
Additional context
I am runnig Portainer Business Edition - the problem seems to be is that when I update a stack using Portainer BE and select Re-pull image and redeploy
The number of entities goes up by the number of containers in the stack - indicating that this is caused by portainer stopping containers, pulling the latest image and then re deploying them. It also seems that additional container senors in the integration get a new index when they get recreated. For example:
The text was updated successfully, but these errors were encountered:
Describe the issue
I have multiple containers shown as sensors, and most of them are unavailable and could only be deleted manually - the problem is that I noticed it late and now I have ~1400 sensors listed in HA and it slows things down a bit.
To be clear: this is connected to Portainer with 2 docker standalone environments and running around 30 containers - definitely not in the thousands.
How to reproduce the issue
🤷♂️
Expected behavior
Containers as sensors don't get duplicated
Screenshots
Software versions
Diagnostics data
🤷♂️
Traceback/Error logs
🤷♂️
Additional context
I am runnig Portainer Business Edition - the problem seems to be is that when I update a stack using Portainer BE and select Re-pull image and redeploy
The number of entities goes up by the number of containers in the stack - indicating that this is caused by portainer stopping containers, pulling the latest image and then re deploying them. It also seems that additional container senors in the integration get a new index when they get recreated. For example:
The text was updated successfully, but these errors were encountered: