Identify the TC model and its connection mode
Record the complete Tiandy model designation, firmware version and whether the camera is attached directly to your LAN or to a recorder camera network. Tiandy publishes multiple camera and recorder generations; a protocol listing for one family does not prove that every current product shares its menus, stream path or enabled services.
The linked Spark and Pro product pages list local streaming protocols but describe different ONVIF and P2P combinations. Use each as evidence for its named product, then confirm the enabled settings on the device you own. A P2P connection in the vendor application follows a different access route from a camera URL entered in a local viewer.
Retrieve a real stream instead of guessing a path
- Find the authorized camera or recorder IP address and confirm which device owns the stream you want. Do not substitute the camera address into a recorder channel URL.
- Sign in to the selected device and inspect its network service settings. Record the actual RTSP and ONVIF settings shown by that firmware.
- If the exact model supports ONVIF, enable the documented service and use an account with live-view permission to discover available media profiles on the same LAN.
- Choose one returned profile and use its URI in SmartRTSP. Confirm video and audio independently, then save the working address and profile for future reference.
Main streams, sub-streams and codec choices
Choose a lower bandwidth profile for an initial multi-camera view, and reserve the high resolution profile for a larger image when required. The profile names, codec choices and maximum simultaneous streams depend on the model. When troubleshooting, select standard H.264 if the camera offers it, then verify that profile in the viewer before enabling a higher resolution or a vendor-specific compression mode.
Treat P2P access, ONVIF and camera control separately
The linked Spark bullet-camera page lists P2P as mutually exclusive with ONVIF. The linked Pro motorized turret page instead lists P2P as mutually exclusive with Profile G. These are not the same restriction, so check the exact model before disabling a working access method. Video discovery does not by itself establish PTZ, analytics delivery, alarm handling or access to recordings stored on the device.
Diagnose reachability before changing credentials
An unreachable endpoint calls for an IP, routing or service-port check. A repeated authorization error calls for a local-account and permission check. A missing stream calls for a profile or path check. If a camera is isolated behind the recorder, ask the installation administrator for the approved access method. Keep management and streaming ports private. Reviewed on 2026-10-18 against the linked Tiandy sources; product specifications are scoped to the named products, not a claim of physical-device testing.
Check each feature independently
Start on the same local network with the exact model, firmware and account permissions. A working video stream does not prove support for ONVIF discovery, pan or tilt, two-way audio, events, or every recording feature. Test the features you need in your installed SmartRTSP app.
Keep camera credentials private. Do not expose camera ports to the public internet just to test local viewing. Manufacturer cloud accounts, device accounts and generated sharing links are not interchangeable.
Frequently Asked Questions
What is the universal Tiandy RTSP URL?
This guide does not assert one. Obtain the configured URI from the exact camera manual or an authenticated ONVIF media profile.
Can I use a Tiandy cloud account as the RTSP login?
Use the account required by the camera or recorder serving the stream. Cloud application access does not establish local device credentials.
Why does ONVIF discovery find nothing?
Check model support, service enablement, account permissions and local network reachability before changing or resetting the installation.
Official sources and scope
Read the documentation for the exact model before changing settings. Manufacturer menus, firmware and service availability can change. These sources explain the published connection conditions, not independently verified SmartRTSP hardware compatibility.