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 was testing an new temp/humidity sensor (sonoff) as I was not happy with my current TuYa one.
So I had 2:
bedroom/sensor (TuYa)
bedroom_aux/sensor (SONOFF)
I was happy with the SONOFF so I decided to replace the TuYa one.
renamed bedroom/sensor to bedroom_old/sensor
renamed bedroom_aux/sensor to bedroom/sensor
I however noticed node-red and some other mqtt clients still saw retained values for bedroom_aux/sensor being published on connect.
2020/09/06 16:51:31 INFO mqtt2rrd: received 'zigbee2mqtt/bedroom_aux/sensor' with '{'temperature': 20.59, 'humidity': 55.82, 'linkquality': 60, 'battery': 100}'
I did some digging to verify it is indeed only the retained value still present on the broker.
What did you expect to happen
I'd expect zigbee2mqtt to tell the broker to forgot the old retained value on rename (or on device removal too actually)
How to reproduce it (minimal and precise)
mosquitto broker with retain configured to be perstistantly stored on disk
z2m connect to mosquitto
other client connected to mosquitto subscribed to the z2m topics.
Bug Report
What happened
I was testing an new temp/humidity sensor (sonoff) as I was not happy with my current TuYa one.
So I had 2:
I was happy with the SONOFF so I decided to replace the TuYa one.
I however noticed node-red and some other mqtt clients still saw retained values for bedroom_aux/sensor being published on connect.
I did some digging to verify it is indeed only the retained value still present on the broker.
What did you expect to happen
I'd expect zigbee2mqtt to tell the broker to forgot the old retained value on rename (or on device removal too actually)
How to reproduce it (minimal and precise)
Debug Info
The text was updated successfully, but these errors were encountered: