Use the VIGI camera stream names
TP-Link documents stream1 for the higher-quality camera stream and stream2 for the lower-quality camera stream in its VIGI RTSP guide. Substitute the current camera address and configured RTSP port. The following examples describe that camera workflow; they do not establish a universal VIGI NVR channel address.
rtsp://CAMERA_IP:554/stream1
rtsp://CAMERA_IP:554/stream2Camera account, NVR account and TP-Link ID are different
Use the local device credentials created or configured for the VIGI camera. A TP-Link ID used to sign in to a management app is not automatically the username and password accepted by a camera RTSP service.
If the camera is installed behind an NVR camera network, its private address may not be reachable from your phone or computer. Decide whether the viewer should connect directly to a reachable camera or to a documented recorder stream. Use the corresponding device account and channel settings instead of mixing the two endpoints.
Set up and verify a camera feed
- Confirm that the exact VIGI model and installed firmware are covered by the TP-Link local-stream guidance.
- Complete camera initialization in the supported VIGI interface and configure a unique local device password.
- Find the current camera IP address and confirm that the viewing device can reach it on the local network.
- Check the RTSP service and configured port; use stream1 or stream2 only for the documented camera workflow.
- Add the URI and local camera credentials in SmartRTSP, or use supported ONVIF discovery with the camera advertised settings.
- Verify stable video on the actual receiving device, then compare the lighter stream if the high-quality profile is too demanding.
Check ONVIF settings without importing Tapo assumptions
The VIGI third-party integration guide describes device-specific ONVIF configuration and authentication considerations. Use the port advertised or configured by your VIGI device. Do not copy a Tapo ONVIF port simply because both brands are made by TP-Link.
Discovery, authentication and video decoding are separate stages. If discovery succeeds but playback fails, inspect the returned stream address, account permissions and encoding. If only the TP-Link app works, confirm that you are testing the local interface rather than relying on app connectivity as proof. RTSP video also does not establish PTZ presets, alarm delivery or two-way-audio support. Check those capabilities separately and avoid publicly exposing camera services for an initial local test.
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
Does a VIGI camera use the same account as my TP-Link ID?
Use the local device account required by the camera. The management-app cloud login is not automatically a camera RTSP credential.
Can I use stream1 for a VIGI NVR channel?
Do not assume so. The examples here are from the camera guide. A recorder can have its own channel URI and account requirements.
Should I reuse Tapo ONVIF settings for VIGI?
No. Follow the VIGI model documentation and the service port it advertises or configures. A shared manufacturer does not establish identical firmware settings.
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.