Add MQTT auto-reconnect with exponential backoff#151
Merged
Conversation
QMqttClient does not reconnect on its own, so an unexpected disconnect (broker restart, transient network drop) left the app stuck on the "broker disconnected" banner until the user manually tapped retry — while every other MQTT client on the network self-heals. MqttManager now arms a single-shot QTimer on entering the Disconnected state and re-dials with exponential backoff (2s base, 60s cap), resetting on a successful connect. An m_reconnectWanted intent flag gates the timer so an explicit disconnect() / MQTT-off never triggers an unwanted re-dial. The Disconnected hook also covers failed reconnect attempts, so the backoff keeps escalating until the broker returns. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
QMqttClient does not reconnect on its own, so an unexpected disconnect (broker restart, transient network drop) left the app stuck on the "broker disconnected" banner until the user manually tapped retry — while every other MQTT client on the network self-heals.
MqttManager now arms a single-shot QTimer on entering the Disconnected state and re-dials with exponential backoff (2s base, 60s cap), resetting on a successful connect. An m_reconnectWanted intent flag gates the timer so an explicit disconnect() / MQTT-off never triggers an unwanted re-dial. The Disconnected hook also covers failed reconnect attempts, so the backoff keeps escalating until the broker returns.
Checklist: