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
Connect Octoprint with this plugin to MQTT service
Disconnect client (home assistant) from MQTT service, and reconnect
Status of device will be unavailable until Octoprint is restarted
What did you expect to happen?
Status of devices remained available.
What happened instead?
Status of devices are unavailable until octoprint is restarted.
Why did it happen?
The LWTT topic is not retained in this case, but HA (and presumably other clients) are watching this topic to know if valid data is coming in from the device. This topic is stateful by nature as a result.
When LWTT is not retained, and the listening client reconnect, it is unable to determine the state (the will published a retained disconnect on top of that), so disconnected tends to be retained in this context anyway.
Given how this topic is intended to be used, I think it makes sense that it is always retained. Or a separate option to control retain on this topic from the rest.
What were you doing?
What did you expect to happen?
Status of devices remained available.
What happened instead?
Status of devices are unavailable until octoprint is restarted.
Why did it happen?
The LWTT topic is not retained in this case, but HA (and presumably other clients) are watching this topic to know if valid data is coming in from the device. This topic is stateful by nature as a result.
When LWTT is not retained, and the listening client reconnect, it is unable to determine the state (the will published a retained disconnect on top of that), so disconnected tends to be retained in this context anyway.
Given how this topic is intended to be used, I think it makes sense that it is always retained. Or a separate option to control retain on this topic from the rest.
This bug is related to: cmroche/OctoPrint-HomeAssistant#55
The text was updated successfully, but these errors were encountered: