Receiving duplicated messages after client reconnection to broker. #15
Replies: 1 comment 3 replies
-
Hello, thank you for letting me know. Can you please tell me which MQTT version are you using? Also are you sending retained messages? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Davide and all,
I'm testing this broker implementation with android MQTT clients and I would like to know if this behavior is some implementation decision in the broker side.
Using a broker such as EMQX and mosquitto for example, when an android MQTT client disconnect and connect again after a while, the client can receive only the missing messages during the disconnection period (clients were set with QoS=1 and cleanSession=False, unique clientID). However, with same client configuration but using this Broker implementation after an android MQTT reconnection, the client receives all messages even messages that it already received before. There is a way to configure in the broker to after a reconnection sent only the missing events instead of all events?
Thank you. Regards, André.
Beta Was this translation helpful? Give feedback.
All reactions