Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rename and rename_last does not clean up old availability topic #4432

Closed
svh1985 opened this issue Sep 22, 2020 · 1 comment
Closed

rename and rename_last does not clean up old availability topic #4432

svh1985 opened this issue Sep 22, 2020 · 1 comment
Labels
feature request Feature request

Comments

@svh1985
Copy link
Contributor

svh1985 commented Sep 22, 2020

Is your feature request related to a problem? Please describe

I think the rename and rename_last are not complete; I would expect z2m to clean up the retained messages for its previous name.

Currently when use rename_last or rename 0x001788234200589e to Kitchen Lamp, the old avalabiltity topic remains there (retained) with value zigbee2mqtt/0x001788234200589e/availability online

After some testing, it also seems that the new device does not get the availability topic.

Describe the solution you'd like

I would expect z2m to clean up the old topic or at least set the availability to offline

Describe alternatives you've considered

Currently, we have to manually remove the retained messages with an MQTT client.

@svh1985 svh1985 added the feature request Feature request label Sep 22, 2020
@Koenkk
Copy link
Owner

Koenkk commented Sep 25, 2020

Fixed!

Changes will be available in the latest dev branch in a few hours (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Feature request
Projects
None yet
Development

No branches or pull requests

2 participants