THE TUTORIAL IS MEANT TO BE USED WITH THIS VIDEO!
Reolink Video Doorbell WiFi (D340W, white or black), Frigate 0.17 or later running in Docker (the Debian VM from the Proxmox + Frigate series works fine), and Home Assistant. October 2026.
What you end up with: a doorbell with a fixed IP address, sharpening turned down, RTSP, ONVIF, and HTTP turned on, no path to Reolink's servers or the internet, recording 24/7 in Frigate, and the button press showing up in Home Assistant as a local sensor you can hang automations on. Optional: two-way talk from Frigate's live view.
Menu names move around a little between Reolink firmware versions, the app, the desktop client, and the web UI. If a name here doesn't match yours exactly, look for the closest thing in the same area. The settings themselves are the same.
Before You Start
The doorbell is installed, powered from your doorbell transformer or the included adapter, and the Reolink chime is paired. (The chime talks to the doorbell over 433 MHz radio, not the internet. Nothing in this worksheet breaks it.)
The Reolink app on your phone. You need it once, to get the doorbell onto Wi-Fi. If you have a network cable at the door, you can plug into the doorbell's Ethernet port instead and skip the app entirely.
Access to your router's settings, for a DHCP reservation and a firewall rule.
Frigate up and running, reachable at https://YOUR-FRIGATE-VM-IP:8971, with SSH access to the machine it runs on.
Home Assistant up and running.
A doorbell password with letters, numbers, dashes, and underscores only. No @, no #, no slashes, no spaces. The password ends up inside URLs in Frigate's config, where an @ or a slash breaks the URL, and Home Assistant's Reolink integration only accepts a limited set of special characters. Make it long instead of weird.
Most of this happens in one of four places: the Reolink app, the doorbell's web UI (a browser pointed at the doorbell's IP), an SSH session to the Frigate machine, or the Home Assistant web UI. Each step says which. Paste multi-line blocks in one go.
My doorbell IP: ______________________________
My doorbell MAC address: ______________________________
Where I stored the doorbell password: ______________________________
My Frigate VM IP: ______________________________
Frigate camera name (Step 4): ______________________________
Home Assistant visitor sensor entity ID (Step 6): ______________________________
(example: 192.168.0.40 for the doorbell, front_doorbell for the camera name, binary_sensor.front_doorbell_visitor for the sensor.)
Step 1 - Get It On the Network and Turn On RTSP and ONVIF
Reolink app, then your router
1.1 - Add the doorbell in the Reolink app. Follow the app's prompts: scan the QR code on the doorbell, give it your Wi-Fi network, and set the admin password from Before You Start. Pick the Wi-Fi band on purpose. 2.4 GHz reaches farther, 5 GHz is faster. If the app shows a weak signal on 5 GHz, use 2.4.
If the app pushes you to create a Reolink account, you can add the device on the local network without one. Look for a skip or local-add option. If you made an account anyway, that's fine; Step 3 cuts the doorbell off from it.
1.2 - Update the firmware now, while the doorbell can still reach the internet. App: Device Settings > Firmware (or Device Info > Firmware Version) > check for updates. After Step 3, updates are manual (see Maintenance).
1.3 - Write down the IP and MAC address. App: Device Settings > Device Info, or Advanced Network Settings > Network Information. Put both in the boxes at the top.
1.4 - Reserve the IP in your router. Create a DHCP reservation (some routers call it a fixed IP or static lease) for the doorbell's MAC address, pinned to the IP you wrote down. Frigate and Home Assistant both point at that IP, so it can't change.
In UniFi: Client Devices > click the doorbell > Settings > Fixed IP Address.
1.5 - Turn on the services Frigate and Home Assistant need. App: Device Settings > tap the device info row at the top > Advanced Network Settings > Server Settings (older apps: Network > Advanced > Port Settings). Turn these on, and leave the port numbers at their defaults:
HTTP (port 80)
HTTPS (port 443)
RTMP (port 1935)
RTSP (port 554)
ONVIF (port 8000)
Media Port (port 9000)
Save.
Why all of them: Frigate pulls video from the HTTP-FLV stream, which uses the HTTP and RTMP services. Two-way talk uses RTSP. Home Assistant uses HTTP or HTTPS for control, the media port for instant button-press events, and ONVIF as a backup. Home Assistant's docs also note that on some Reolink models, HTTP doesn't work right unless RTMP is on.
1.6 - Check the web UI. On a computer on the same network, open http://YOUR-DOORBELL-IP and log in as admin. You should see the live view. Everything from here on in Steps 2 and 3 happens in this browser window.
STOP HERE if the web UI won't load. Everything after this depends on it. See If It Doesn't Work.
Step 2 - Turn Down the Sharpening and Set Up the Streams
Doorbell web UI
2.1 - Find the image settings. Settings (gear icon) > Camera (or Device) > Display > Advanced.
2.2 - Turn the sharpness to 0
2.3 - (Optional) Leave the rest alone for now. Brightness, contrast, and saturation are fine at their defaults. Day and Night should stay on Auto.
2.4 - Set the main stream. Settings > Camera (or Device) > Stream. On the main stream (Clear):
Resolution: the highest it offers (2560 x 1920, or 1920 x 2560 on the white one)
Frame rate: 20
Max bitrate: 4096 is the default and is fine. Raise it toward 6144 if motion looks blocky.
2.5 - Set the substream (Fluent): frame rate 10 is the default and is fine for Frigate's detection. Leave the resolution at its default.
2.6 - If your firmware shows these, set them (Frigate's docs recommend them for Reolink cameras):
Frame Rate Mode or bitrate mode: On, fluency first (this is constant bit rate)
Interframe Space: 1x (one keyframe every second, so Frigate never waits long for a clean frame)
Save.
If you don't see either option, your firmware doesn't expose them for this model. Move on; Frigate works without them.
Step 3 - Cut Off Remote Access
Doorbell web UI, then your router. After this step, the doorbell only talks to your local network. The Reolink app still works on your home Wi-Fi, or from anywhere over Tailscale if you set that up in the Reolink NVR video.
3.1 - Turn off UID. Settings > Network > Advanced (newer firmware may put it under Network > General or Port Settings). Turn Enable UID off. Save.
Why: UID is Reolink's P2P remote access. With it on, your phone finds the doorbell through Reolink's servers, and video can relay through them when your phone is away from home. With it off, that path is gone.
3.2 - Turn off UPnP. Same area: turn Enable UPnP off. Save. Then make sure UPnP is off in your router too, so nothing on your network can open ports to the internet on its own.
3.3 - Turn off Reolink's push notifications. Settings > Surveillance (or Alarm) > Push. Turn Push off. In the Reolink app, you can also turn off notifications for this device.
Why: push notifications go through Reolink's servers even with UID off. Home Assistant handles notifications in Step 6, locally. After 3.5, Reolink's push can't get out anyway; turning it off just keeps the doorbell from trying.
3.4 - Turn off email and FTP alerts if they're on. Settings > Surveillance > Email and FTP. Off, unless you're deliberately sending clips to a NAS on your own network over FTP.
3.5 - Block the doorbell from the internet in your router. Create a firewall rule that blocks all traffic from the doorbell's IP (or MAC) to the internet. The doorbell still reaches your local network, so Frigate and Home Assistant keep working.
In UniFi with Zone-Based Firewall: Settings > Policy Engine (or Security > Firewall), create a policy. Source: the doorbell, by device or by its IP. Destination: the External zone. Action: Block. If you have a camera VLAN that's already blocked from the internet, putting the doorbell on that VLAN does the same job.
Other routers: look for a parental control, internet access toggle, or block rule per device. Same idea.
3.6 - Fix the clock. Blocking the internet blocks NTP, the time server, so the doorbell's clock will slowly drift. Settings > System > Date and Time > NTP. If you have a local time server (many routers and firewalls can act as one), put its IP there. If you don't, add a narrow exception to the rule in 3.5 that allows only UDP port 123 out, and leave everything else blocked.
My NTP server: ______________________________
3.7 - Test it. Turn Wi-Fi off on your phone, so you're on cellular, and open the Reolink app. The doorbell should fail to connect. Turn Wi-Fi back on; it connects again.
STOP HERE. The doorbell is now local-only. Ring it once and make sure the Reolink chime still rings.
Step 4 - Add It to Frigate
Frigate web UI, then SSH to the Frigate machine
4.1 - Start the wizard. Open https://YOUR-FRIGATE-VM-IP:8971 > Settings > Camera management (in some versions: Global configuration > Camera management) > Add Camera.
4.2 - Pick the stream detection method. Choose Manual selection, then choose Reolink as the brand. Enter the doorbell IP, admin as the username, and the doorbell password. Give the camera a name with lowercase letters and underscores, like front_doorbell, and write it in the box at the top.
Why manual selection: the wizard asks the doorbell what it is and, because it's 5 megapixels, picks the HTTP-FLV stream, which Frigate's docs say is the most reliable option for Reolink cameras at that resolution. The Probe camera method finds RTSP streams instead, and the wizard warns you about that for a camera like this one.
If your Frigate version's wizard doesn't list Reolink as a brand, skip to the config in If It Doesn't Work and add the doorbell by hand.
4.3 - Validation. When the wizard tests the stream, turn on Use stream compatibility mode if it recommends it.
On the doorbell, the wizard only finds the high resolution main stream. It doesn't offer the substream. Finish the wizard anyway; 4.5 adds the substream by hand.
4.4 - Save, and wait for the camera to show up on the Live dashboard. Click it and confirm the picture is moving, then check the audio icon.
4.5 - Add the substream for detection. The wizard gives the doorbell one input with all three roles: detect, record, and audio. It also sets detect to 960 x 720. That means Frigate decodes the full 2560 x 1920 stream at 20 frames per second, all day, and then shrinks every frame down to 960 x 720 just to look for people. The substream is built for that job. SSH to your Frigate machine and open the config:
nano ~/frigate/config/config.ymlFirst, the go2rtc streams. Under go2rtc: > streams:, find the stream the wizard made. It has your camera's name and its line contains channel0_main.bcs. Change it to this, and add the sub stream right below it (use your IP and password, and your camera name if it isn't frontdoorbell):
front_doorbell:
- "ffmpeg:http://YOUR-DOORBELL-IP/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=YOUR-DOORBELL-PASSWORD#video=copy#audio=copy#audio=opus"
front_doorbell_sub:
- "ffmpeg:http://YOUR-DOORBELL-IP/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=YOUR-DOORBELL-PASSWORD"
channel0_main is the high resolution stream, channel0_ext is the substream. The three # parts on the end of the main line tell go2rtc to pass the video and audio through untouched, and to also make an Opus copy of the audio. Opus is the audio format WebRTC uses, so without it you get no sound in Frigate's WebRTC live view, and no two-way talk in Step 5. The sub line doesn't need any of that.
Then, the camera. Under cameras: > front_doorbell:, change ffmpeg:, detect:, and live: to this. Leave enabled: and friendly_name: as they are:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/front_doorbell
input_args: preset-rtsp-restream
roles:
- record
- audio
- path: rtsp://127.0.0.1:8554/front_doorbell_sub
input_args: preset-rtsp-restream
roles:
- detect
live:
streams:
Main: front_doorbell
Sub: front_doorbell_sub
That's three changes. The main input loses the detect role and keeps record and audio. A second input brings in the substream for detect. And the live view gets both streams, so you can switch to Sub on a slow connection.
Delete the detect: section the wizard wrote (detect:, width: 960, height: 720). With it gone, Frigate reads the substream's size on its own. If you have other settings under detect:, keep those and delete only the width and height lines.
Audio stays on the main stream. Audio detection only decodes the sound, not the picture, so it costs almost nothing there.
Save with Control-X, then Y, then Enter, and restart:
cd ~/frigate && docker compose restart frigateBack in Frigate, Settings > Metrics (or System) > Cameras should now show the doorbell with detect running at the substream's resolution, and the Live view for the doorbell should have a stream picker with Main and Sub.
4.6 - Check it's keeping up. Settings (or System) > Metrics > Cameras. The doorbell's camera fps should sit near 10 (the substream rate from 2.5), and skipped fps should be 0.
4.7 - Turn on recording and set what to track, if the wizard didn't. In the same config.yml, find your doorbell under cameras: and make sure it has these sections, at the same indent as ffmpeg: (replace front_doorbell with your camera name, and leave ffmpeg, live, and the rest the way you set them in 4.5):
front_doorbell:
record:
enabled: true
objects:
track:
- person
- dog
- cat
snapshots:
enabled: true
Save with Control-X, then Y, then Enter, and restart Frigate:
cd ~/frigate && docker compose restart frigateIf your config already sets record, objects, or snapshots globally, the camera inherits them and you don't need these lines. Zones, masks, and retention are covered in the Frigate Part 3 worksheet; the front walk is a natural zone for a doorbell.
STOP HERE if you don't care about two-way talk from Frigate. The Reolink app still does two-way talk on your home network.
Step 5 - (Optional) Two-Way Talk From Frigate
SSH to the Frigate machine. Frigate sends your microphone to the doorbell through go2rtc, over the doorbell's RTSP stream, while video keeps coming from HTTP-FLV. This needs WebRTC working in Frigate, and a browser on https (port 8971 is), because browsers only let pages use the microphone over https.
5.1 - Find the wizard's stream. Open the config:
nano ~/frigate/config/config.ymlUnder go2rtc: > streams:, find the stream whose line contains channel0_main.bcs. That's the doorbell's main stream.
5.2 - Add the RTSP line under it, as a second item in the same list:
front_doorbell:
- "ffmpeg:http://YOUR-DOORBELL-IP/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=YOUR-DOORBELL-PASSWORD#video=copy#audio=copy#audio=opus"
- "rtsp://admin:YOUR-DOORBELL-PASSWORD@YOUR-DOORBELL-IP/Preview_01_sub"
The first line is the one you changed in 4.5; it needs the #audio=opus part on the end for this to work. Add only the second line. Do not put ffmpeg: in front of the rtsp line. go2rtc has to handle that stream itself for the audio to go back to the doorbell.
5.3 - Make sure WebRTC is set up. Still in config.yml, under go2rtc:, you need a webrtc section like this (add it if it's missing, at the same indent as streams:):
webrtc:
candidates:
- YOUR-FRIGATE-VM-IP:8555
- stun:8555
And in ~/frigate/docker-compose.yml, under the frigate service's ports:, these two lines need to be there (the standard Frigate compose file has them):
- "8555:8555/tcp"
- "8555:8555/udp"5.4 - Apply it. If you changed the compose file, use up -d; if you only changed config.yml, restart is enough:
cd ~/frigate && docker compose up -d
docker compose restart frigate5.5 - Test it. Open the doorbell in Frigate's live view from a computer or phone with a microphone. Switch the stream to WebRTC if it isn't already, and click the microphone button. Allow microphone access when the browser asks. Have someone stand at the door and listen.
Expect a little delay. Reviewers notice it with the Reolink app too.
Step 6 - Add It to Home Assistant
Home Assistant web UI
6.1 - Add the integration. Settings > Devices & services > Add Integration > search for Reolink. Home Assistant may already show the doorbell under Discovered; if so, click Configure there instead.
Host: YOUR-DOORBELL-IP
Username: admin
Password: YOUR-DOORBELL-PASSWORD
Submit, and assign it to an area (Front Door, Porch, whatever you use).
If it says the password has characters it can't use, change the doorbell password to letters, numbers, dashes, and underscores (doorbell web UI: Settings > System > User Management), then update Frigate's config with the new password too.
6.2 - Find the visitor sensor. Settings > Devices & services > Reolink > your doorbell. Look for the binary sensor named Visitor. Ring the doorbell; it should flip to Detected within a second or two. Write its entity ID in the box at the top. It looks like binary_sensor.front_doorbell_visitor.
Why it's fast: the integration listens for the doorbell's own push events over the media port (9000) on your network. That's why 1.5 turned it on. None of this goes through Reolink's servers, and Home Assistant's docs say the integration keeps working with the doorbell blocked from the internet.
6.3 - Look around the other entities. You also get person and motion sensors, an infrared lights switch, the status LED, quick reply playback, and chime controls, depending on firmware. The camera entity here is Reolink's stream. If you also run the Frigate integration, you'll have a second camera entity from Frigate; use whichever you prefer on your dashboard.
6.4 - Make the button do something. Settings > Automations & Scenes > Create Automation > Create new automation > three-dot menu > Edit in YAML. Paste this, then change the two entity IDs to yours:
alias: Doorbell - someone is at the door
triggers:
- trigger: state
entity_id: binary_sensor.front_doorbell_visitor
to: "on"
actions:
- action: notify.mobile_app_YOUR_PHONE
data:
title: Front door
message: Someone rang the doorbell.
mode: single
Save, ring the doorbell, and check your phone.
The notify action name comes from the Home Assistant Companion app on your phone. Find yours under Developer tools > Actions, search for notify.mobile_app. From here, add whatever you want: flash a light, announce it on a speaker, or ring a smart plug chime in the garage where the Reolink chime can't hear the doorbell.
STOP HERE. Your doorbell is local-only, recording in Frigate, and ringing through Home Assistant.