Fix websocket reliability and auth handling after websockets upgrade - #13
Merged
Conversation
Fix SmartRent websocket auth handling Add Authorization headers to both streaming and command websockets Refresh token and retry once on 403 InvalidStatus Keep heartbeat and jittered backoff for stability
anthonymkz
marked this pull request as draft
September 20, 2025 20:34
anthonymkz
marked this pull request as ready for review
September 20, 2025 20:37
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
2 participants
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.
When upgrading the SmartRent library to a newer websockets release, I began seeing frequent websocket timeouts and 403 errors This PR improves connection stability and command reliability by: