-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to detect that reconnect_retries has been exceeded? #72
Comments
Hi @stefangotz |
Hi @Lenka42 ! |
@stefangotz sorry, my bad. Please try upgrade to
I checked, and in your in case with |
Hi @Lenka42 ! Thanks a lot for pointing that out! With v0.5, I do indeed no longer observe this issue. Resolved as far as I am concerned. |
When I set
reconnect_retries
to some value as documented in the README and I want my application to react to the fact that gmqtt has exceeded that number of retries and given up on reconnecting (e.g., to exit the application or to reconnect at a much later stage), how would I do that?The text was updated successfully, but these errors were encountered: