-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Try both HLS and webRTC and pick best stream #22585
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Core PR merged |
// Browser support required for WebRTC | ||
return typeof RTCPeerConnection === "undefined"; | ||
// No video in HLS stream and no video in WebRTC stream | ||
return true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bramkragten I think this change might have caused a regression in the HLS player. When the _setRetryableError
is called from the ha-hls-player
with:
private _setRetryableError(errorMessage: string) {
this._error = errorMessage;
this._errorIsFatal = false;
fireEvent(this, "streams", { hasAudio: false, hasVideo: false });
}
This code path (or the updated path from #22674) will cause the camera stream to switch to the mjpeg
stream without retrying. I have a situation where an intermittent bufferAppendError
being raised from an HLS stream, and instead of retrying it immediately falls back to the mjpeg stream. Previously I think that fallback would only have happened if fetchStreamUrl
failed.
What do you think?
Proposed change
If a camera has support for both HLS and webRTC we try both and pick the best result.
Needs: home-assistant/core#128455
Type of change
Example configuration
Additional information
Checklist
If user exposed functionality or configuration variables are added/changed: