Skip to main content

​
Overview

Reolink makes wired and Wi-Fi security cameras for homes and small properties. Seam connects to a standalone Reolink IPC camera over its local HTTPS, ONVIF, and RTSP services through a Seam Bridge.
Reolink cameras are in beta. Camera events and live video are available in every workspace. Behavior and API shapes may change before general availability.
Reolink requires a Seam Bridge running continuously on the same local network as the camera. Seam does not reach the camera over the public internet.

​
Supported Devices

Connect compatible standalone Reolink IPC cameras that provide local HTTPS API access, ONVIF, and an H264 RTSP substream. Seam supports one standalone, single-channel Reolink IPC camera per connected account. NVRs and multi-channel devices are rejected by the integration. Seam represents the camera as a device with the reolink_camera device type. A compatible PoE switch can power and network the camera; a Reolink NVR is not required.

​
Supported Features

​
Brand-Specific Restrictions

  • Seam Bridge required. Discovery, live video, motion events, and status checks travel through the paired Bridge. If it stops running or loses access to the camera’s LAN, the camera cannot be verified or observed.
  • One camera per connected account. Each Reolink connection authorizes one camera address and one set of local camera credentials.
  • Local credentials required. Enter the Reolink camera’s local username and password. These are different from a Reolink cloud or mobile-app login.
  • Stable local address required. Seam stores the camera’s local IP address or hostname. Reserve the address in your router so it does not change.
  • No recording or PTZ support. The integration does not provide NVR or multi-channel discovery, continuous recording, recording search, or PTZ control.
  • Generic motion events. Reolink events use activation_reason: "motion_detected"; this integration does not report human, vehicle, package, or other motion subtypes.

​
Brand-Specific Events

Seam fires camera.activated when it receives an ONVIF motion notification through the running Bridge. The event includes activation_reason: "motion_detected". Motion timing, latency, and delivery are not guaranteed for every physical motion stimulus.

​
Device Provider Key

Seam identifies these devices with the reolink device provider key. Include reolink in the accepted_providers list when creating a Connect Webview. For more information, see Customize the Brands to Display in Your Connect Webviews.

​
Setup Instructions

For camera port configuration, Seam Bridge requirements, Connect Webview fields, and troubleshooting, see the Reolink Setup Guide. For the shared live-video flow, including client sessions, capability checks, and browser WebRTC negotiation, see Stream Live Video.

​
Manufacturer Resources

How to Configure Reolink Ports Settings

Introduction to ONVIF Protocol