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'm testing bigclown sensors with homeassistant (hass) on Turris 1.1 and it doesn't work well. Hass connects to mqtt broker periodically and in many times it simply miss the value change from sensor.
After some searching I've found that there is "Retain Message Flag", that tells broker to store the last value. So hass always gets the last value when asks.
I've tested it, extended the publish function call with parameter retain=True and now hass works as I expect.
So it will be nice to have this flag in configuration and I can enable it when need.
Only question I have: is it OK to enable it for all published messages in general or should be configurable per message type or even per message?
The text was updated successfully, but these errors were encountered:
It makes sense to use retain messages for some topics, but definitely not for all (in general) - it'd be incorrect solution for this issue. MQTT supports persistent sessions.
I'm testing bigclown sensors with homeassistant (hass) on Turris 1.1 and it doesn't work well. Hass connects to mqtt broker periodically and in many times it simply miss the value change from sensor.
After some searching I've found that there is "Retain Message Flag", that tells broker to store the last value. So hass always gets the last value when asks.
I've tested it, extended the publish function call with parameter
retain=True
and now hass works as I expect.So it will be nice to have this flag in configuration and I can enable it when need.
Only question I have: is it OK to enable it for all published messages in general or should be configurable per message type or even per message?
The text was updated successfully, but these errors were encountered: