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
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/availabilityonline
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.
The text was updated successfully, but these errors were encountered:
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
toKitchen Lamp
, the old avalabiltity topic remains there (retained) with valuezigbee2mqtt/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
tooffline
Describe alternatives you've considered
Currently, we have to manually remove the retained messages with an MQTT client.
The text was updated successfully, but these errors were encountered: