Added MQTT Disconnect messages from server with reason codes #10734
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.
Pull Request description
PE PR - https://github.com/thingsboard/thingsboard-pe/pull/2579
Due to MQTT v5 specification - server can send disconnect messages to device with specific reason codes, this PR contains realisation for this. It will be useful to understand reasons for disconnects, the simplest cases are: rate limits exceeded or session was taken by another client, session closing by activity timeout, etc. At the moment - transport just closes a channel and client can notice only "Connection refused error".
Also, in order to test response - a was needed to change our default implementation of MQTT client to get ability to receive response in case of disconnecting.
General checklist
Front-End feature checklist
Back-End feature checklist