Reolink Integration Setup

Reolink cameras and doorbells connect to Home Assistant through the built-in Reolink integration. It talks to each device on the local network with the device’s own login, not a Reolink cloud account, and receives motion, person, vehicle, and doorbell events as they happen.

Before You Start

1. Update the firmware. Install the latest firmware from the Reolink Download Center . The update check in the Reolink app does not always offer the newest version, and Home Assistant refuses firmware that is too old.
2. Set a local password. Set the device up in the Reolink app and give it an admin password of at most 31 characters, using only letters, digits, and @$*~_-+=!?.,:;'()[]. Other characters break the video streams. A device bound to a Reolink cloud account without a local login cannot be added.
3. Reserve the IP addresses . Leave each camera on DHCP, which is its default, and reserve the address it received in the router. Do not set a static IP in the camera itself: Reolink devices then send incorrect DHCP requests.

Home Assistant can follow a camera to a new address when it sees the camera’s DHCP request, but it usually does not see it once the cameras sit on their own VLAN, which is where they belong. A reservation removes the problem.

Step 1: Add the Cameras to Home Assistant

1. Go to Settings > Devices & Services. Each camera usually appears under Discovered as Reolink. Select Add. If it is not there, select Add Integration, search for Reolink, and enter its IP address.
2. Enter the device’s admin Username and Password, the local login from the Reolink app, not the Reolink cloud account.
3. Assign the camera to an area.

Add each camera or doorbell separately. Cameras recorded by a Reolink NVR or Home Hub can be added through it instead: add the NVR once and its cameras come with it.

Each device appears with its camera streams, motion and AI detection sensors (person, vehicle, and animal, depending on the model), and switches for its lights, siren, and recording. The integration turns on the network services it needs on the camera. If it cannot, it raises a Reolink port not enabled repair: turn that service on in the Reolink app or desktop client.

Step 2: Make Sure Events Arrive

Most wired cameras push their events over their own connection with Home Assistant, on TCP 9000. Some models push them to Home Assistant’s local URL instead (ONVIF push, which needs a plain HTTP address), and battery cameras added directly use a webhook on that URL. Set the URL up so every model works:

1. Go to Settings > System > Network > Home Assistant URL.
2. Under Local network, use http:// and the Selora Hub’s IP address, for example http://192.168.1.20, not a hostname and not https://. Add :8123 on a Hub set up before Home Assistant 2026.8.
3. Give the Hub a fixed address, as described in IP Configuration . The cameras that use this URL can no longer reach Home Assistant if the Hub’s address changes.

When a wired camera cannot push its events over TCP, Home Assistant tries ONVIF push, then ONVIF long polling, and last checks for events every 5 seconds, so automations react late. If it cannot reach the URL, it also raises a Reolink webhook URL unreachable repair.

The Doorbell

The doorbell press appears as the Visitor binary sensor, which turns on with each ring: use it to trigger automations such as pausing the music. A Reolink Chime paired with the doorbell appears as its own device, and the reolink.play_chime action rings it from an automation.

Use the PoE doorbell, the model Home Assistant lists as tested. Battery cameras and the original battery doorbell connect to Home Assistant through a Reolink Home Hub or a compatible NVR.

Network and Firewall

On a separate camera VLAN, allow:

• From Home Assistant to the cameras: TCP 80 or 443 (control) and 9000 (event push), plus the video port for the streaming protocol in use: 554 for RTSP or 1935 for RTMP (FLV uses the control port). Add 8000 for cameras that push events over ONVIF.
• From the cameras to Home Assistant: the port in Home Assistant’s local URL, for cameras that push events over ONVIF or a webhook.
• Battery cameras added directly: unrestricted UDP between the camera and Home Assistant, both ways.

The cameras need no internet access for Home Assistant. Block it if the client does not use the Reolink app away from home.

One Connection per Camera

A camera only accepts a few connections at once. Do not also add Reolink cameras through the ONVIF integration: ignore that discovery. When a recorder such as Frigate also pulls the streams, entities can go unavailable: in the Reolink integration’s options, switch the Protocol from RTSP to FLV, which is lighter on the camera, at the cost of 4K.

Troubleshooting

1. “Failed to connect”. Check the camera’s IP address and that the VLAN allows the ports above. If both are right, create a new admin user on the camera and use it in Home Assistant.
2. “Password contains incompatible special character or is too long”. Change the password in the Reolink app to one that follows the rules in Before You Start , then enter it again.
3. “Failed to log in because of outdated firmware”. Update the firmware from the Reolink Download Center.
4. Most entities are unavailable. The camera’s privacy mode is on. Turn it off with the privacy mode switch.
5. Events arrive late. Download the camera’s diagnostics from its device page and look for the event connection it uses. Fast polling means push failed: check TCP 9000 and the Home Assistant URL as in Step 2 .