The short answer
Check the exact Safie model and installed firmware before choosing a connection method. The information below separates vendor-documented preparation from actual playback verification with your camera and client.
Reference 1 · Reference 2 · Reference 3 · Reference 4 · Reference 5
What to know for this brand
Configure the device with its owner or an authorized setup account and verify internet connectivity for both the camera and Safie Viewer.
Safie documents cloud service prerequisites and model-specific network constraints, but these sources do not establish a reusable local RTSP endpoint for Safie One or PT CAM.
The GO 360 architecture uses ONVIF or RTSP inside its managed camera-router arrangement, which does not establish an exported stream or generic PTZ interface for Safie subscribers.
Product families to identify
Safie One · Safie PT CAM · CC-2/CC-2L · Safie GO 360
These names help identify the relevant documentation; they are not an exhaustive list or a hardware certification.
Connection route
A cloud or vendor-app workflow does not establish an open local RTSP or ONVIF endpoint. Use only a documented export or explicitly compatible integration. A third-party bridge adds its own host, credentials and dependencies; it does not turn a proprietary camera into a natively supported device.
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
Identify the exact Safie model, firmware and whether the source is a camera, recorder, hub or API. Match the documentation to that source rather than another device with a similar name.
Confirm the documented local service or export route. Create the required local account where supported; a cloud-account login is not automatically a camera-stream credential.
Check the reachable private address, scheme, configured port and stream selection. A controller token or temporary API session may have different lifetime and access requirements from a camera account.
Test one authorized source and one client. Preserve the error stage: address timeout, authentication failure, unsupported secure mode and decoding errors require different corrections.
Verify a changing live scene, the intended lens or channel and a reconnect. Test audio, PTZ, events and offline restart separately instead of inferring them from video playback.
What to verify
Record model, firmware, source, account type and the actual decoded-video result. This guide does not assert physical-device testing, certification or every optional capability in AeoCam.
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.