Skip to content

HL_PAN4 (Wyze Cam Pan v4) - IOTC_ER_UNLICENSE on firmware 4.70.1.3311 #1533

@namcbrid-hash

Description

@namcbrid-hash

Describe the bug

Wyze Cam Pan v4 (model HL_PAN4) fails P2P connection with IOTC_ER_UNLICENSE (-10) on both latest and dev tags of docker-wyze-bridge v2.10.3. Camera is discovered and added to streams, but never connects.

Bridge version

v2.10.3 (tested both mrlt8/wyze-bridge:latest and mrlt8/wyze-bridge:dev, sha256 89f2439f... for dev)

Camera model

  • Model: HL_PAN4 (Wyze Cam Pan v4)
  • Firmware: 4.70.1.3311 (latest production as of March 2026)
  • Nickname: "Kaydence"

Relevant log output

[+] Adding Kaydence [HL_PAN4]
[kaydence] [-10] IOTC_ER_UNLICENSE

PTZ endpoints (e.g. /api/ptz_position) return timed out — the camera never reaches a connected state.

What I tried

  • Switched from latest to dev tag — same result, same error
  • Camera connects and streams fine in the official Wyze app
  • Other cameras (non-Pan v4) work as expected

Notes / Questions

A few things worth noting based on research:

  1. HL_PAN4 doesn't appear in the bridge's supported cameras table — only Pan v3 (HL_PAN3) is listed as the newest supported Pan model. Is HL_PAN4 intentionally unsupported, or is this a TUTK license gap?

  2. TUTK SDK version — Is there a plan to update the TUTK SDK version to support newer Wyze firmware? The HL_CAM4 firmware update issue (BUG: Wyzecam v3 and v4 no longer work with bridge after auto-firmware update #1438) also surfaced TUTK license/compatibility problems.

  3. Workaround? — Is there any known workaround (e.g. firmware downgrade, specific env vars, network_mode: host) that has worked for HL_PAN4?

  4. v4fix fork — Saw nickdnj/docker-wyze-bridge-v4fix which uses WebRTC via AWS Kinesis instead of TUTK for HL_CAM4. Does that approach extend to HL_PAN4? Any plans to incorporate WebRTC support for Pan v4 into the main bridge?

Thanks for maintaining this project!

Environment

  • Bridge type: Docker Run
  • Host OS: Windows 11 Pro (Docker Desktop 29.2.1)
  • Bridge port mapping: 5000, 8554, 8888

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions