The short answer
Wyze RTSP support depends on the exact model and firmware branch. Cam v3 and Pan v3 have a documented 2026 integration; Cam v4 has an official RTSP beta announcement. Cam v2 and the original Pan have separate legacy firmware. A bridge is a different connection route, not native camera RTSP.
- Wyze Cam v3 RTSP: current setup and legacy firmware
- Wyze Cam v4 RTSP: firmware status and connection checks
- Wyze Cam Pan v3 RTSP: setup, firmware and PTZ limits
- Wyze Cam v2 RTSP: legacy firmware and practical limits
- Original Wyze Cam Pan RTSP: first-generation firmware
- Wyze RTSP option missing: model, app and firmware
- Wyze RTSP not working: URL, login and video checks
- Wyze native RTSP or Docker Wyze Bridge?
Reference 1 · Reference 2 · Reference 3 · Reference 4 · Reference 5
What to know for this brand
Wyze released integrated RTSP for Cam v3 4.36.16.5654 and Pan v3 4.50.16.5654, with app 3.9 or later required to use it.
Cam v4's July 2026 RTSP announcement was a beta; later production firmware version numbers alone do not establish that every branch retains that feature.
The cited RTSP announcements establish streaming support for specific branches and do not establish ONVIF discovery or ONVIF pan-and-tilt control.
Product families to identify
Wyze Cam v3 · Wyze Cam Pan v3 · Wyze Cam v4
These names help identify the relevant documentation; they are not an exhaustive list or a hardware certification.
Connection route
This brand includes different product families and connection methods. Identify the exact line before choosing RTSP, ONVIF, a controller export or the vendor app. Do not transfer a URL pattern, account rule or cloud limitation from one family to every product sold under the same name.
ONVIF check
Native ONVIF support is not established here. Do not infer it from the vendor app, an RTSP session or a bridge.
Model-scoped stream examples
No universal direct RTSP template is provided. Obtain a supported endpoint from the exact device, controller or documented API instead of guessing an address.
Use a private, reachable network for the first test. A working vendor cloud view does not prove that a separate computer can reach a local camera service.
Source titles retain the original document language. Check the current manual for your product; firmware, accounts and service availability can change.
Work through the checks
Read the model name in Device Info and on the camera label. Cam v3 is not v3 Pro, and Pan, Pan v2, Pan v3 and Pan v4 are different products.
For Cam v3 and Pan v3, consult the February 2, 2026 release announcement and the current release notes. Record the installed app and camera versions before changing anything.
For Cam v4, distinguish the July 27, 2026 RTSP beta from the current production branch. Confirm that your installed build actually exposes RTSP in Advanced Settings.
Treat v2 and original Pan instructions as legacy. Do not install one model’s image on another. Pan v4, OG and other variants need their own documented support check.
Choose direct RTSP when the camera provides a working URL. For a bridge, verify that project’s model and firmware table; the address then belongs to the bridge host.
What to verify
Keep a record of model, firmware, support route and one decoded live picture. Vendor documentation establishes preparation requirements, not an AeoCam hardware certification.
Sources and scope
AeoCam is available for Windows. Camera settings below describe protocol preparation, not a certification of a particular camera or a promise of every feature in every app version. Check the installed build and the Microsoft Store listing for current availability.
Vendor documents describe the camera or protocol. No physical-camera compatibility test is claimed here. Menus and capabilities can change with model and firmware.