Direct answer
For the powered WiFi/D340W or PoE/D340P doorbell, enable RTSP and ONVIF and use the doorbell IP with Preview_01_main or Preview_01_sub. For Video Doorbell Battery/D340B, use a compatible Home Hub endpoint; do not reuse the powered-doorbell IP instructions.
Compatibility by model
| Model | Direct RTSP / ONVIF | Endpoint to use | Important detail |
|---|---|---|---|
| Video Doorbell WiFi / D340W | Yes | Doorbell IP | Powered by 12-24 VAC or 24 VDC; WiFi is not the battery model. |
| Video Doorbell PoE / D340P | Yes | Doorbell IP | Network connection uses Ethernet/PoE; two-wire doorbell power is not Ethernet. |
| Video Doorbell Battery / D340B | No | Compatible Home Hub IP | No direct RTSP/ONVIF; hub streams can sleep and need wake time. |
| Doorbell through NVR | Via recorder | NVR IP and assigned channel | Smart visitor features depend on exact NVR hardware and firmware. |
RTSP URL and ports
The powered WiFi and PoE doorbells use Reolink's normal standalone path. Their documented 5MP streams are H.264. RTSP normally uses port 554 and ONVIF normally uses 8000; use the displayed settings if changed.
Setup steps
- Confirm whether the unit is powered WiFi/D340W, PoE/D340P or Battery/D340B.
- For WiFi/PoE, in Reolink App 4.59+ open Device Settings > device information row > Advanced Network Settings > Server Settings and enable RTSP/ONVIF.
- In Reolink Client use Device Settings > Network > Advanced > Server Settings.
- Test Preview_01_sub first, then Preview_01_main. Use doorbell credentials for direct access.
- When connecting through an NVR, use NVR IP, NVR credentials and the recorder channel, such as Preview_02_main for channel 2.
- For the battery model, configure protocol access on a compatible Home Hub and allow wake-up time.
Troubleshooting by symptom
| Symptom | Likely cause | Check or fix |
|---|---|---|
| No Server Settings on battery model | D340B has no direct protocol service | Use a compatible Home Hub. |
| ONVIF scan finds nothing | Ports disabled or different subnet | Enable RTSP/ONVIF and test on the same LAN. |
| Video works but no doorbell event | RTSP carries media, not every vendor event | Use Reolink app/NVR for visitor, package and chime features. |
| No talkback | Client does not implement Reolink/ONVIF audio return | Treat two-way audio separately from RTSP playback. |
| Wrong NVR doorbell | Incorrect assigned channel | Check NVR camera management and URL channel. |
Functions that need separate testing
RTSP playback does not guarantee visitor notifications, quick replies, package detection, chime control or two-way talk in a third-party viewer. The WiFi and PoE doorbells have native two-way audio, but the client and endpoint must support the return path. These doorbells have a fixed lens, so PTZ should not be expected.
View the camera in SmartRTSP
SmartRTSP can show the local video stream on iPhone, iPad, Mac and Apple TV once the correct RTSP/ONVIF endpoint is available. Add the substream for a multi-camera view and the main stream for a detailed door view. Keep Reolink's app for vendor-specific doorbell controls that are not part of basic RTSP playback.
Security: Keep RTSP and ONVIF on the trusted local network. For remote access, use a VPN instead of exposing camera ports to the public internet.
Frequently asked questions
Does Reolink Video Doorbell WiFi support RTSP?
Yes. The powered WiFi/D340W and PoE/D340P models support direct RTSP and ONVIF.
Does the battery doorbell have direct RTSP?
No. Reolink's current compatibility table requires a compatible Home Hub.
What is the current Reolink doorbell RTSP path?
Use /Preview_01_main or /Preview_01_sub for a directly connected powered doorbell.