alexdelprete
commented
1 year ago @fmartinou This is an issue I'm also having (not with Portainer, simple docker-compose files) since quite some time. Wanted to analyze the problem better before opening the issue. It seems to be triggered when I recreate the container (to restart/upgrade etc.). I usually update the compose file then I do this: docker compose up -d --force-recreate --remove-orphans
After recreating it, I notice that in WUD, often the name of the instance has a weird random string prefix. Check here, I upgraded Home Assistant 2 times and later I saw this in my MQTT broker (and also WUD UI obviously):
In order to clean this, I stop WUD, delete the json file, clean the bad topics in MQTT (both in WUD topic and homeassistant discovery topic), then restart WUD and all the names would be ok again.
It's very annoying to do this everytime I upgrade something...:)
aheath70
RK62
For some of my containers I use the stack feature (docker compose) of Portainer. While updating the container, Portainer creates the new container at first with a prefixed name. After the successful update the old container is removed and the new one is renamed. Unfortunately, wud does not change the name after the update as well.
Example: I updated the container with name "homeassistant". In wud the updated container is named "8b3b3c4de280_homeassistant". In MQTT both container are visible but only "8b3b3c4de280_homeassistant" gets new values. Btw: The prefix are the first characters of the old container id.
I can fix this by recreating the container without any change. But this can only be a workaround. If I update the container directly everything works as expected as well.
Btw: wud also does not recognize when the container name is changed in Portainer.