Choose an encoder, not a presumed resolution name
LILIN’s current support article describes stream0 and stream1 as commonly used encoder paths and explains how to find the actual URLs under Video/Audio. The resolution and compression belong to the encoder configuration; a name such as primary or secondary does not fix those settings forever.
An older LILIN test article also contains resolution-based examples. Keep those examples with the camera generation they describe. Mixing a legacy resource name with a modern encoder layout can produce a valid connection to the device without a valid video resource.
Copy and verify the camera-provided URI
- Find the camera’s local IP address and identify its full model and firmware version. Keep the viewing device on a reachable local network.
- Log in to the camera’s authorized web interface and open Setup, then the Video/Audio page described by LILIN.
- Read the URL shown beside the desired encoder. Copy it together with the actual configured RTSP port instead of replacing its path with an example.
- Check that the encoder is enabled and that the local account has permission to receive it. Note the selected video compression and resolution.
- Enter the URI and camera credentials in SmartRTSP. Test live movement, reconnect after closing the view, and repeat with another encoder only if it is required.
rtsp://<camera-ip>:<configured-rtsp-port>/stream0Keep recorder output separate from camera output
LILIN publishes separate NVR streaming instructions with channel and stream parameters. Use that documentation only when connecting to the recorder’s address. A recorder channel number is not the same thing as the encoder index on a standalone camera.
When an installer supplied an NVR stream, identify which recording channel it represents and verify the permitted local user. Avoid changing existing recorder settings merely to make a camera example fit. First establish whether the desired image should come from the camera or from the NVR.
Check performance without changing the working path
A lower-bandwidth enabled encoder can suit a camera grid, while the main encoder may suit a larger display. Choose deliberately and confirm that another recorder is not relying on settings you intend to change. Altering a bitrate does not require guessing a new URI.
If authentication fails, recheck the local account. If authentication succeeds but there is no picture, compare the full copied path and encoder settings. Then verify audio, presets and PTZ separately instead of treating video playback as evidence for every camera feature.
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
Should I always use stream0 for the main image?
Use the URL displayed for the intended encoder on your camera. stream0 is a common documented example, not a guarantee for every LILIN generation.
Can a LILIN NVR URL be used directly on a camera?
Not generally. The official NVR instructions describe recorder output with separate channel and stream selections.
Does this guide certify every LILIN model?
No. Official guidance was checked on 2026-10-18; verify physical operation and each required function on the exact model and firmware.
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.