refactor!: WS client disconnection may not emit a disconnect event#35
Merged
refactor!: WS client disconnection may not emit a disconnect event#35
Conversation
The `disconnect` event is defined in the Integration-API and may not be used to signal a WebSocket disconnection. New events have been introduced to listen to WS connections and disconnections and a new `client_count` property to get the number of clients.
martonborzak
approved these changes
Nov 24, 2025
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.
The
disconnectevent is defined in the Integration-API and may not be used to signal a WebSocket disconnection.New events have been introduced to listen to WS connections and disconnections and a new
client_countproperty to get the number of clients.Discovered in unfoldedcircle/integration-denonavr#137