--
To learn more about MQTT please visit http://mqtt.org
---
You received this message because you are subscribed to the Google Groups "MQTT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mqtt+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mqtt/900f3eb1-9718-4956-80b3-d1c4d16bce44%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mqtt/CAPP_e3Zon3Jp8srnvCs62M%2BnH1WKU%2BbNCCjwAw0-s74T69uHXg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mqtt/CACr69QzPkwJ1B39o9icBv6MG_R9f6ULxmQ8zC1F54Fbi6HW4ug%40mail.gmail.com.
you should only receive one message with the retain flag set, per topic, after you subscribe.You might receive other messages that were published with retain set, but they won’t have retain set on them when they arrive at the subscriber.
--
To learn more about MQTT please visit http://mqtt.org
---
You received this message because you are subscribed to the Google Groups "MQTT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mqtt+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mqtt/CAFnwT5_eUUyUmMgAnodOAbYJp7MM4As6KK1faSD7jwbvUQ_A5w%40mail.gmail.com.
Just be clear. This is not actually part of the MQTT spec, right?Rather sounds like a proprietary bridge configuration provided by a specific broker.
--
To learn more about MQTT please visit http://mqtt.org
---
You received this message because you are subscribed to the Google Groups "MQTT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mqtt+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mqtt/CAFnwT58QSO7DaE0xL6EoKti9iimdpnM1wRxdA5JprWPcef%2B_kA%40mail.gmail.com.
Furthermore, I have a unit test that attempts to publish three retained messages to a topic, then subscribes with a client, and expects to receive a single retained message. However, the client in the unit test frequently can receive 2 or 3 messages, but seems to always receive the latest message last.
Got’ya!Seems i missed the second mail of this thread, switching to the MQTT 5 spec.
For some clarity, the implementation of mqtt that we are using, MQTTnet (https://github.com/chkr1011/MQTTnet) uses protocol version 3.1.1 by default. There is a way to specify version 5.0.0 but we are not using it since it does not seem to work for all server behaviors.So in my case, I am using 3.1.1.I assumed that the retained message behavior would be similar for 3.1.1 and 5.0.0, but for my case, I will focus on 3.1.1.