Skip to content

Fix native 2K resolution selection for Wyze Bulb Cam HL_BC - #2497

Open
seitzbg wants to merge 1 commit into
AlexxIT:masterfrom
seitzbg:fix-wyze-hlbc-resolution
Open

seitzbg wants to merge 1 commit into
AlexxIT:masterfrom
seitzbg:fix-wyze-hlbc-resolution

Conversation

@seitzbg

@seitzbg seitzbg commented Sep 13, 2026

Copy link
Copy Markdown

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 FrameSizeFloodlight enum value 4, to serve 2304×1296.

Select that frame size in hdFrameSize() for HL_BC. The existing K10056
payload, 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:

  • Wire values 1 and 4 leave the stream at 640×360 despite a success ACK.
  • Payload 05 f0 00 00 00 returns 01; K10050 readback returns
    f0 00 05 14 01 01 (bitrate 240, resolution 5, 20 fps).
  • A two-minute recording through the patched native source, RTSP restream,
    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.

@AlexxIT AlexxIT self-assigned this Oct 1, 2026
@AlexxIT AlexxIT added enhancement New feature or request brand/wyze labels Oct 1, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

brand/wyze enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants