Conversation
This was referenced Sep 13, 2026
JonnyTran
approved these changes
Sep 23, 2026
This branch has not been deployed
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
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 native Wyze source requests the wrong HD resolution for HL_BC, leaving
the camera at 640×360. This model requires K10056 wire resolution byte 5,
the existing
FrameSizeFloodlightenum value 4, to serve 2304×1296.Select that frame size in
hdFrameSize()for HL_BC. The existing K10056payload, bitrate setting, authentication, and TUTK channel work unchanged.
Adding HL_BC to
is2K()alone selects wire byte 4 and does not fix it.Verified on a physical HL_BC running firmware 21.1.6.1161:
05 f0 00 00 00returns01; K10050 readback returnsf0 00 05 14 01 01(bitrate 240, resolution 5, 20 fps).and Frigate input measured 2304×1296, nominal 20 fps, approximately 1.53 Mbps.
go test ./pkg/wyze ./pkg/tutk/...passes, and the binary builds.The recording decoded without warnings, but native packet-fragment loss
caused missing keyframes and temporal gaps. This resolution change does not
claim to fix transport loss or prove equivalence to the app's image quality.
Related to #2314.