Unistall mqdockerup

[lamasseriadipolverara]

I've been happily using mqdockerup, but now, to free up space and transfer everything to another server, I've uninstalled it. The strange thing is, I still see MQTT messages in MQTT Explorer that mqdockerup should generate, even though it's been uninstalled.
Why?

[github-actions]

👋 Welcome to the project! Thank you for raising your first issue. We will look into it as soon as possible.

[mdisabato]

If I recall correctly, if the "retain" flag is set to TRUE, the messages will remain after the source disappears. If you use a viewer such as MQTT Explorer, you can delete them. After that they will not return until you start up the service again.

Then you need to go to the MQTT Integration in HA and manually delete the devices. Click the three dots under Device Info to and select "Delete".

Thank you.

[arrikhan]

I used MQTT explorer to delete /homeassistant/sensor/-updates and /homeassisstant/update/-updates relating to the containers defined by mqdockjerup and HA removes the devices automatically.

mqdockerup obviously doesn't account for containers/images that are deleted either and manage that update to Home Assistant so stuff 'hangs around' forever unless manual intervention is required. Feels like a running list needs to be managed to be able to change the retain flag, as well as a flag to 'clear' what it is managing for situations like this.

[MichelFR]

Thanks for reaching out, ill implement some logic to prevent the containers from beeing persisted.
it happens because of the retained flag which i used previoulsy.

since we now have a sqlLite db it should not be needed.

ill keep this open to report on progress