Why Reolink works well with Home Assistant
Reolink has an official Home Assistant integration. It connects to the camera, NVR, or Home Hub over your local network, using the device’s own API. It doesn’t need a Reolink cloud account or a subscription. The integration requires Home Assistant 2023.1 or later, and it supports standalone cameras, Reolink NVRs, and Home Hubs. Home Assistant often finds these devices automatically through DHCP discovery.
Step 1: Enable the right protocols in the Reolink app
In the Reolink app, open the camera’s settings and go to Network > Advanced. Menu names vary by app version. Turn on:
- RTSP
- ONVIF
- HTTP or HTTPS, as needed
Note the device’s IP address. Reolink’s default ports are HTTP 80, HTTPS 443, RTSP 554, RTMP 1935, ONVIF 8000, and media 9000. Port settings are in the same Network area.
Step 2: Create a local admin account
Use a local admin account rather than a cloud login. Set a strong password before you connect the camera to your network, and avoid unusual special characters, which can complicate some addresses.
Step 3: Add the integration
- Go to Settings > Devices & services. If Home Assistant discovers the camera, it may appear as a device you can configure.
- If it doesn’t appear, choose Add integration and search for Reolink.
- Enter the camera’s IP address, your username (the default is
admin), and your password. - Finish setup. Camera entities appear with their controls.
The integration uses push events, with polling as a fallback. It creates motion, person, vehicle, pet, and visitor sensors. Depending on the model, it also adds entities for the camera streams, IR and spotlight controls, a siren, PTZ, record and push switches, and a firmware update entity.
Step 4: Choose a stream
The integration exposes stream options such as Clear, which is higher resolution, and Fluent, which uses less bandwidth. Use Fluent for dashboards and Clear when you need detail. If you’re unsure, start with Fluent and check the image quality.
Using RTSP with the Generic Camera instead
If you’d rather use the Generic Camera integration, Reolink’s RTSP addresses follow this pattern:
rtsp://user:password@192.168.1.60:554/h264Preview_01_main
Use _sub at the end for the substream. H.265 models use h265Preview_01_main instead. Frigate’s documentation recommends HTTP-FLV, RTMP, or go2rtc over raw RTSP for better stability with Reolink cameras. If you use Frigate, check its Reolink guidance first. See the Frigate guide.
Local recording options
Reolink cameras can record locally in a few ways:
- A microSD card in the camera
- A Reolink NVR, such as the RLN8-410 or RLN16-410
- A Reolink Home Hub with microSD storage
Capacity varies by model. Home Assistant’s Media browser can play back recordings from a microSD card or an NVR.
Battery cameras and the Home Hub
Battery (Argus) cameras sleep to save power. They don’t offer a continuous RTSP stream, and they expose fewer entities. Continuous live streaming drains the battery quickly. Many people bring battery cameras into Home Assistant through a Home Hub, which acts as a local bridge.
Network tips
- Use PoE when you can. Power over Ethernet (802.3af) is generally the most reliable option.
- If you use Wi-Fi, use 5 GHz where the model supports it.
- Set DHCP reservations so each camera keeps the same IP address. A changed address can break saved RTSP addresses and the integration’s connection.
Common misconceptions
- “Reolink needs its cloud for Home Assistant.” The integration is fully local.
- “Battery models stream continuously.” They don’t.
- “The integration is just ONVIF.” It uses Reolink’s own API.
- “Recordings on the SD card can’t be viewed in Home Assistant.” The Media browser can play them.
Troubleshooting
If the live view is black, see why your camera feed is black. For the basics of RTSP addresses and dashboard cards, see the Home Assistant cameras guide.