New Reolink Wired POE Doorbell Cam ?

Hmmm... maybe that's why it didn't power up when I tried it. They use the same manual for both.
The WiFi version comes with a Wall Wart power supply for when you use the Ethernet port or WiFi. The POE version does not.

Only way to get power to the WiFi version is through the two screw terminals. On the POE version it can get power from the POE Ethernet Port or the two screw terminals.

HTH
 
The WiFi version comes with a Wall Wart power supply for when you use the Ethernet port or WiFi. The POE version does not.

Only way to get power to the WiFi version is through the two screw terminals. On the POE version it can get power from the POE Ethernet Port or the two screw terminals.

HTH
Yep ... i figured that out when setting it up.
 
  • Like
Reactions: David L
How or how often do you sync the time on this doorbell if it’s closed network?

I noticed recently it’s off 7 mins from restart 2 days ago, so need to sync with phone app.
(I have local ntp server for cameras but this DB doesn’t support custom ntp server in configuration.)
 
How or how often do you sync the time on this doorbell if it’s closed network?

I noticed recently it’s off 7 mins from restart 2 days ago, so need to sync with phone app.
(I have local ntp server for cameras but this DB doesn’t support custom ntp server in configuration.)
My version POE supports a custom NTP server but doesn't appear to have a configurable sync frequency.

I set it in the Windows Reolink software.

Screen Shot 2024-10-25 at 13.51.40.png
 
  • Like
Reactions: David L and Kevman
Looks like they released 4110

Thanks
I have the Black POE version and I tried this version over the weekend. Installed Sat, Sunday the IR filter switched from night to day. Today, Mon, the IR filter stuck on night mode. I switched back to firmware 3215 as that was the last version that I had no issues with.

Michael
 
  • Like
Reactions: David L
Are there many using the Reolink doorbell via the app via a VPN ?

Does connecting via a VPN when responding to a doorbell press cause too much of a delay ? Thanks
 
  • Like
Reactions: David L
Are there many using the Reolink doorbell via the app via a VPN ?

Does connecting via a VPN when responding to a doorbell press cause too much of a delay ? Thanks
That would depend on how fast the VPN is. Are you talking local VPN or someone else's Cloud/Service VPN?
 
Are there many using the Reolink doorbell via the app via a VPN ?

Does connecting via a VPN when responding to a doorbell press cause too much of a delay ? Thanks
Sorry I should have clarified. Say OpenVPN on the router.
So, I cannot speak for the ReoLink App since I do not use it but maybe this will help until someone else chimes in. I have an OpenVPN server running locally on my pfSense Router in which I connect to via my phone's OpenVPN client. I use the Home Assistant App for viewing the Doorbell live feed and get push notifications (Doorbell Button and Motion) on my phone from my Home Assistant box running locally. I am satisfied with the response time.

It is really up to your Cell Service from where you are connecting to your VPN.

I can share that I use to use the EZVIZ App and do the same thing, connect to my local VPN on my Hikvision Doorbell and found the same results.

Someone here can correct me but it really does not matter connecting to your local VPN, the App connects to the ReoLink cloud anyway. I don't think there is any advantage, you gave them access to your network via their App. Only way to keep them out of your network is stop using their Cloud based App.

So my point is, connecting to your local VPN will/should not have any affect with how fast you receive your notifications and viewing done via their App.

EDIT: To add, my Doorbell has No Internet access. This keeps ReoLink out of my network, I have never registered the Doorbell, ReoLink does not even know I own one. How I access it is thru my VPN Server which gives me encrypted access into my home network where the Doorbell resides. I only allow access to the subnet (VLAN) that my Cameras are on, also my Blue Iris box and my Home Assistant box.

HTH
 
Last edited:
So, I cannot speak for the ReoLink App since I do not use it but maybe this will help until someone else chimes in. I have an OpenVPN server running locally on my pfSense Router in which I connect to via my phone's OpenVPN client. I use the Home Assistant App for viewing the Doorbell live feed and get push notifications (Doorbell Button and Motion) on my phone from my Home Assistant box running locally. I am satisfied with the response time.

It is really up to your Cell Service from where you are connecting to your VPN.

I can share that I use to use the EZVIZ App and do the same thing, connect to my local VPN on my Hikvision Doorbell and found the same results.

Someone here can correct me but it really does not matter connecting to your local VPN, the App connects to the ReoLink cloud anyway. I don't think there is any advantage, you gave them access to your network via their App. Only way to keep them out of your network is stop using their Cloud based App.

So my point is, connecting to your local VPN will/should not have any affect with how fast you receive your notifications and viewing done via their App.

EDIT: To add, my Doorbell has No Internet access. This keeps ReoLink out of my network, I have never registered the Doorbell, ReoLink does not even know I own one. How I access it is thru my VPN Server which gives me encrypted access into my home network where the Doorbell resides. I only allow access to the subnet (VLAN) that my Cameras are on, also my Blue Iris box and my Home Assistant box.

HTH
Thank you. I appreciate the advice. I didn’t realise using a vpn with the app wouldn’t negate any security concerns.

So I am right in thinking the gold standard is to set it up as you have or maybe directly into a NVR. But presumably when plugged in to an NVR using onvif you loose the ability of responding to door bell pushes.
 
  • Like
Reactions: David L
Thank you. I appreciate the advice. I didn’t realise using a vpn with the app wouldn’t negate any security concerns.

So I am right in thinking the gold standard is to set it up as you have or maybe directly into a NVR. But presumably when plugged in to an NVR using onvif you loose the ability of responding to door bell pushes.
Correct. I thought the same when I had my Hikvision Doorbell, but I did use OpenVPN to connect to my Blue Iris (NVR) box at that time which was secure and encrypted.
I have limited networking knowledge, on our Hikvision Doorbell thread we had members use sniffers to monitor traffic on the Doorbell to see what ports/traffic/URLs were being accessed:

HIKVISION DOORBELL NETWORKING TIPS:
⦁ In your Firewall settings, allow ICMP from the Doorbell to your router, otherwise the Doorbell will disconnect/reconnect the WiFi - ronin1, ronin1 - alexdelprete, alecdelprete-ronin1 AND/OR if your RTSP stream drops every 3 or so minutes - cba123
⦁ In order to view the video from Ezviz app allow traffic from your local_devices_ip TO any external IP at port : 6500, 7100 and 10554 -cool77
⦁ In order to answer a ring call from Ezviz app allow traffic from your local_devices_ip TO any external IP at port : 9664 - cool77
⦁ For Streaming (RTSP) add a rule that allows traffic from your local_devices_ip TO all_internal_IP at port : 554 - cool77
⦁ For Remote Access using (iVMS-4200 or Batch Configuration Tool) allow traffic from your local_devices_ip TO any external IP at port : 8000
⦁ It is always a good idea, for security reasons, to Disable UPnP in your router too - Emilks5
⦁ FOR MORE PORT/NETWORK INFO - msmcknight
⦁ SSID Change see - Fractal

Wish someone here with that network knowledge would do the same and share for people who use the ReoLink App.

If you plan on connecting to your NVR remotely then by all means use your local OpenVPN server. Blue Iris has the same limitation in that you cannot two-way talk back to the Doorbell visitor who pushed the button. If this is important to you, the ReoLink App is your only option.

Short history; Back 4 years ago when I got my first Video Doorbell I was excited to be able to talk to someone who was at my door. That quickly changed over time with Delivery drivers running up to the door, pressing the button then running off before I could talk to them. Then they got smart and stopped ringing the Doorbell all together. Sales/Solicitors where the only ones I could talk to. I found it was best not to waste your time with Solicitors since they would not go away, lol, so I stopped talking to them. Family would just be on their phone calling us when they arrived.

Point is, the two-talk on these Doorbells, very few people use.

HTH
 
  • Like
Reactions: looney2ns
Thank you. I appreciate the advice. I didn’t realise using a vpn with the app wouldn’t negate any security concerns.

So I am right in thinking the gold standard is to set it up as you have or maybe directly into a NVR. But presumably when plugged in to an NVR using onvif you loose the ability of responding to door bell pushes.
Oh one more thing, NVRs, they act like their own router. You have an IP for the NVR that connects to your local network. Your cameras are then in a separate subnet than your NVR (assigned by the NVR) and cannot be directly accessed from your network. You are limited to the access that your NVR allows. Which means, some NVRs don't allow access to the cameras settings. I don't have experience with NVRs but this is what I been told/learned.
The author of this Thread experienced this when setting his ReoLink Doorbell up.

Why was access to the ReoLink DB settings important? Well ReoLink for some reason does not have ONVIF or RTSP turned On by default. So when you connect the DB to your NVR (other than a ReoLink NVR), it would not communicate to it. What you have to do is connect the DB to your network first and turn On these ports/protocols before connecting to your NVR.

The reason it works on a ReoLink NVR is they use UID (unique identifier) to identify their cameras.

HTH
 
Last edited:
  • Like
Reactions: TonyR
Oh one more thing, NVRs, they act like their own router. You have an IP for the NVR that connects to your local network. Your cameras are then in a separate subnet than your NVR (assigned by the NVR) and cannot be directly accessed from your network. You are limited to the access that your NVR allows. Which means, some NVRs don't allow access to the cameras settings. I don't have experience with NVRs but this is what I been told/learned.
Just to clarify for Mapano: Yes, true of POE NVR's. :cool:

What you have to do is connect the DB to your network first and turn On these ports/protocols before connecting to your NVR.
Just to clarify for Mapano: Yes, configured in the DB's webGUI by opening a browser to its IP address. :cool:
 
  • Love
Reactions: David L