The short answer
RTSP and RTSPS are different connection modes. Wyze’s testing instructions show /stream0 with RTSP port 554 and RTSPS port 322. Treat these as documented examples, not a replacement for your generated address. A client supporting RTSP does not automatically support the secure variant.
Work through the checks
Read the generated URL and secure-mode setting together. Record the scheme, host, explicit port and path so later edits do not mix two configurations.
Confirm the client’s RTSPS support before selecting secure playback. The vendor’s testing instructions describe client limitations; they do not certify every release or AeoCam combination.
For a trusted-LAN RTSP test, use only the unencrypted endpoint you intentionally enabled. Keep that stream on the private network rather than forwarding its port to the internet.
For RTSPS, keep the TLS endpoint and appropriate transport. Investigate certificate or handshake errors separately from stream-account authentication errors.
Compare the same camera scene after changing only one setting. If using a restreaming server, document the protocol on each side rather than calling the entire route encrypted.
rtsp://CAMERA_IP:554/stream0/
rtsps://CAMERA_IP:322/stream0/What to verify
Record which mode actually produces decoded video. Do not claim secure AeoCam playback or end-to-end encryption solely because the camera offers an RTSPS toggle.
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.