SDK is not trying to reconnect if a publish was not successful #607
Unanswered
jakob-sturm
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I have the following setup:
MQTT: 3.1.1
KeepAlive: 20 minutes
QoS: 1
Now when my connection has changed under the hood (for example the modem switched carrier, but was offline for only a few seconds) and I want to publish a message, the message doesn't go through. That's fine, but it takes up to 20 minutes or longer (I guess due to the KeepAlive interval) until the SDK recognises that the connection was interrupted. Then it immediately is able to resume the connection and deliver the message. Why does it take so long and can I configure the SDK somehow to detect interrupted connections earlier and reconnect faster?
Beta Was this translation helpful? Give feedback.
All reactions