How to Connect Amcrest Cameras to LightNVR
Use Amcrest's realmonitor RTSP endpoint to bring the camera's full-resolution and sub streams into LightNVR for recording and live viewing.
1. Before you start
This guide assumes the camera is already powered, activated, and visible on your local network. Complete the RTSP test from a computer on that same network before involving a VPN or cloud recorder. That separates a camera configuration problem from a routing problem.
You will need:
- The camera’s local IP address
- A camera-local username and password with live-view permission
- A computer with VLC or
ffprobefor the local test - Network access from LightNVR to the camera, directly or through a private tunnel
2. Prepare the Amcrest camera
- Locate the camera: Use Amcrest IP Config or your router's DHCP lease list to find the local IP, then reserve that address in DHCP.
- Verify the RTSP port: Sign into the camera web interface and check Setup, Network, then Connection or Port. The normal RTSP port is 554; use the configured value if yours differs.
- Use a camera-local account: The URL needs a user defined on the camera. Amcrest Cloud or mobile-app credentials are not interchangeable with the camera login.
3. Build the main and sub-stream URLs
Replace the placeholders with the camera account and reserved local IP address.
| Use | RTSP URL |
|---|---|
| Main recording stream | rtsp://username:password@CAMERA_IP:554/cam/realmonitor?channel=1&subtype=0 |
| Lower-bandwidth live stream | rtsp://username:password@CAMERA_IP:554/cam/realmonitor?channel=1&subtype=1 |
channel=1 selects the first camera channel. subtype=0 requests the main stream and subtype=1 requests the first extra/sub stream. Multi-channel devices use channel=2, channel=3, and so on.
If a username or password contains reserved URL characters such as @,
:, /, ?, or #, percent-encode that value
before embedding it in the URL. Do not weaken the camera password just to make the URL easier to type.
4. Test the feed locally
Quick visual test with VLC
- Connect the test computer to the same network as the camera.
- In VLC, choose Media → Open Network Stream.
- Paste the main-stream URL and select Play.
- Repeat with the sub-stream URL and confirm it is the lower-resolution feed.
Inspect the stream with ffprobe
This reports the codec, dimensions, and frame rate without creating a recording:
ffprobe -v error -rtsp_transport tcp \
-show_entries stream=codec_name,width,height,r_frame_rate \
-of default=noprint_wrappers=1 \
"rtsp://username:password@CAMERA_IP:554/cam/realmonitor?channel=1&subtype=0"Do not move on until at least the main URL works locally. If it fails, use the RTSP troubleshooting checklist to identify authentication, path, port, and codec failures in that order.
5. Add the camera to LightNVR
- Confirm the LightNVR host can route to the camera IP. A cloud instance should use a WireGuard tunnel; do not forward RTSP port 554 from the public internet.
- Open the LightNVR interface and select Streams in the main navigation.
- Select Add Stream.
- Under Basic Settings, enter a short name such as
front_door. - Paste the main URL into Stream URL.
- Paste the lower-bandwidth URL into Sub Stream URL.
- Optionally enter the camera’s web address in Camera Admin URL.
- Select Test Connection. Save with Add Stream only after the test succeeds.
6. Tune recording and live view
Once the basic connection is stable, tune one setting at a time:
- Set the main stream to H.264 at a fixed bitrate while commissioning the camera.
- Configure sub stream 1 at a lower resolution and bitrate, then enter it in LightNVR's Sub Stream URL field.
- If audio is not needed, disable it at the camera while isolating video connection problems.
- Budget using the camera’s configured bitrate, not resolution alone. A 4 Mbps stream transfers about 43 GB per day before retention overhead.
- After every codec or profile change, rerun Test Connection and check a newly created recording.
7. Troubleshooting
The camera is visible in the app but RTSP fails
- Confirm the model actually supports local RTSP.
- Make sure the URL contains the camera-local username and password, not Amcrest account credentials.
- Some Smart Home models document an additional authbasic=64 query parameter; follow the model-specific Amcrest article when required.
Main and sub streams appear reversed
- Use subtype=0 for the main stream and subtype=1 for the first extra stream.
- Check the camera's Encode page to confirm which resolution is assigned to each stream.
It works in VLC locally but not from LightNVR Cloud
- Confirm the WireGuard tunnel shows a recent handshake.
- Confirm the routed camera subnet contains the camera IP.
- Test TCP port 554 from the LightNVR side; a successful ping does not prove RTSP is reachable.
- Open System → System Logs, reproduce the failed connection, and inspect the newest warning or error.
8. Keep the connection secure
- Use a dedicated camera user with live-view permission instead of the administrator account.
- Keep the camera on an isolated camera or IoT VLAN when practical.
- Route RTSP through the LAN or WireGuard; never expose port 554 directly to the public internet.
- Keep camera firmware current and remove unused accounts and services.
- Remember that credentials embedded in an RTSP URL are sensitive. Do not paste a real URL into public issues or screenshots.
Vendor reference: Amcrest: accessing devices using RTSP. Menu names can move between firmware versions, but the linked vendor documentation is the source of truth for the stream path.