Overview
This guide walks you through connecting one standalone Reolink IPC camera to Seam. Seam reaches the camera over its local network through a Seam Bridge, so the Bridge must stay running on the same LAN as the camera.Step 1: Prepare the Camera
- Set up the camera in the Reolink app or web interface.
- Give the camera a stable local IP address or hostname. A DHCP reservation in your router prevents the address from changing.
- Create or identify a local camera username and password. Seam uses these credentials to sign in to the camera; do not enter a Reolink cloud or mobile-app login.
- A compatible PoE switch can power and network the camera. You do not need a Reolink NVR.
Step 2: Enable Camera Services
In the Reolink web interface, open the camera’s port settings and enable HTTPS, ONVIF, and RTSP. Reolink’s How to Configure Reolink Ports Settings guide shows where to configure these services. Use the camera’s current values when connecting it to Seam. The integration defaults to:
Reolink notes that port availability varies by model. Check the values displayed by your camera, and keep the camera and Bridge on the same LAN. Do not expose the camera’s management or media ports to the public internet.
Step 3: Install Seam Bridge
Install and pair Seam Bridge on a computer that stays powered on and connected to the camera’s LAN. Use the setup guide for your operating system:Step 4: Connect through a Connect Webview
Reolink is available in the production API, but some released SDKs and generated API reference enums do not yet include
reolink or reolink_camera. If your SDK rejects reolink, create the Webview with a direct HTTP POST to https://connect.getseam.com/connect_webviews/create, using your server-side Seam API key as a Bearer token and a JSON request body whose accepted_providers array contains reolink. Use the returned Webview URL for the steps below. This HTTP connection flow was verified with a production workspace. Keep the API key on your server; do not expose it in browser code.- Open the Connect Webview provided by your application. It must include
reolinkin itsaccepted_providerslist. - Select Reolink as the provider.
- Follow the Seam Bridge instructions in the Webview.
- On the Connect your Reolink camera screen, enter:
- Select Connect camera. Seam verifies the camera through the Bridge, checks that it identifies as Reolink, and records its serial number as the camera’s stable identity.
Step 5: Verify the Connection
After connecting, verify that the camera appears with thereolink_camera device type and shows as online. Before offering live video, check the device’s can_stream_live_video capability. For the client-session and browser WebRTC flow, see Stream Live Video.
To verify motion, enable motion detection and its schedule in the Reolink interface, then create a visible motion stimulus. Look for a camera.activated event with activation_reason: "motion_detected" through your webhook or the Events API. A missed stimulus does not establish a guaranteed detection interval or delivery failure.
Troubleshooting
Seam cannot verify the camera
Confirm that:- The Bridge is running and connected to the same LAN as the camera.
- The camera address is correct and has not changed.
- HTTPS is enabled and the HTTPS port matches the value in the Connect Webview.
- The credentials are the camera’s local username and password.
- The camera identifies as a standalone, single-channel IPC device rather than an NVR or multi-channel device.
443 as its default in Troubleshooting Web Client.
Credentials are rejected
Re-enter the local camera username and password. Seam does not accept the credentials for a Reolink cloud or mobile-app account.The camera shows as offline
Check the camera’s power and network connection, confirm that the Bridge computer is powered on, and verify that the camera address and configured ports are reachable from the Bridge’s LAN.Live video does not start
Check that the camera is online and thatcan_stream_live_video is true. Create a new live-view session and use a fresh browser WebRTC offer. Browser audio is unsupported for this integration; use include_audio: false. Sessions are short-lived and last from 1 to 600 seconds.