New Reolink Wired POE Doorbell Cam ?

[David L]

After various further tests, I am now fairly certain that the hardware (CPU + RAM) used in the Reolink Doorbell WiFi is simply too weak to reliably establish and maintain multiple simultaneous connections. I can now consistently reproduce these connection drops at will.

As previously mentioned, my Reolink Doorbell WiFi is connected via Wi-Fi and linked to the Reolink app, a Dahua NVR (via ONVIF), and Home Assistant (via the Reolink integration). Even this setup occasionally causes the Reolink Doorbell to "drop out" and become unreachable. If I then add it to a second Home Assistant VM, for instance, things essentially grind to a halt, and the Reolink Doorbell WiFi fails completely - becoming inaccessible even through the Reolink app itself. Naturally, this triggers corresponding warnings and error messages in Home Assistant. Example:

View attachment 248609

It only becomes reachable again once I reduce the number of active connections to the Reolink Doorbell WiFi - for example, by disconnecting it from Home Assistant.

Yes, anyone using the Reolink Doorbell solely via the Reolink app - or perhaps adding a lightweight integration with software like Frigate, Agent DVR, Blue Iris, or similar - likely won't encounter these issues. However, various other users have confirmed that the hardware Reolink uses is somewhat underpowered. The Home Assistant Reolink integration documentation itself explicitly points this out:

"Reolink cameras can support a limited amount of simultaneous connections. Therefore using third-party software like Frigate, Blue Iris, or Scrypted, or using the ONVIF integration at the same time can cause the camera to drop connections."

Yes, a problem like that might well occur with video doorbells from other manufacturers too - even though I didn't experience it with my previous Dahua OEM video doorbell (Imou DB61i). In that sense, I don't necessarily want to fault Reolink for it, but it is worth knowing that you might encounter this kind of issue with the Reolink Wi-Fi doorbell.

In other words, the question of where these timeouts come from - such as when I adjust settings in the Reolink Doorbell WiFi web GUI - and why other connection drops occur from time to time is now resolved for me. At least, that is my own explanation for it.

You need to use/try RTMP. I had problems with RTSP and this ReoLink in BI. Once I switched to RTMP I had and still have Zero Drops...and I have the WiFi version...


I too use HA and have had zero problems...also have Blue Iris Integration going to. The ReoLink DB can handle Main and Sub streams fine...

If you want to really do a test, have the DB stream to multiple VLC connections/windows...I think I had 4 going in my test awhile back when I first got the DB. Thinking 3 main streams was no problem, 4 was pushing it...

Use this for Media/Open Network Stream in VLC

 

[Jim_OS]

Thanks for the information and suggestions. I’ve already run plenty of tests over the last few weeks, and I’m aware that switching the streams to RTMP has helped some users.

However, in my opinion, total resource consumption isn't actually the problem; I could address that by lowering the stream quality - for instance, by reducing the frame rate - which is something I’ve already done.



Looking at the NVR, for example, you can see that the bitrate for the Reolink Doorbell (Channel 4) isn't particularly high.



To me, it looks more like the camera struggles when "too many" processes are running - or need to run - simultaneously. I’m not sure if it’s running out of RAM, if the CPU simply can't handle processing that many tasks, or if there are entirely different reasons involved.

Besides that, when integrating via ONVIF, I can't always choose whether to use RTMP or RTSP for the streams; for example, that’s not possible with my Dahua NVR



(though it is possible with the Home Assistant Reolink integration).

As previously mentioned, I’ve tried to figure out exactly where the problem with the Reolink Wi-Fi doorbell lies and what might be causing it. To me, it seems the camera gets overwhelmed when pushed "too hard" - something I didn't experience with my Dahua OEM doorbell. That said, the Dahua model did have fewer features than the Reolink Wi-Fi doorbell.

But sure, anyone facing similar issues might want to give the RTMP stream a try. That said, as far as I know, the original reason for preferring RTMP was a bug in older firmware versions that caused frame dropping in the RTSP stream - though that has likely been fixed by now.

PS: It remains a mystery to me how Reolink could decide not to allow the motion detection function to be disabled at all. I have no need for motion detection in this instance, yet it creates unnecessary load and consumes system resources.

 

[David L]

Thanks for the information and suggestions. I’ve already run plenty of tests over the last few weeks, and I’m aware that switching the streams to RTMP has helped some users.

However, in my opinion, total resource consumption isn't actually the problem; I could address that by lowering the stream quality - for instance, by reducing the frame rate - which is something I’ve already done.

View attachment 248615

Looking at the NVR, for example, you can see that the bitrate for the Reolink Doorbell (Channel 4) isn't particularly high.

View attachment 248616

To me, it looks more like the camera struggles when "too many" processes are running - or need to run - simultaneously. I’m not sure if it’s running out of RAM, if the CPU simply can't handle processing that many tasks, or if there are entirely different reasons involved.

Besides that, when integrating via ONVIF, I can't always choose whether to use RTMP or RTSP for the streams; for example, that’s not possible with my Dahua NVR

View attachment 248617

(though it is possible with the Home Assistant Reolink integration).

As previously mentioned, I’ve tried to figure out exactly where the problem with the Reolink Wi-Fi doorbell lies and what might be causing it. To me, it seems the camera gets overwhelmed when pushed "too hard" - something I didn't experience with my Dahua OEM doorbell. That said, the Dahua model did have fewer features than the Reolink Wi-Fi doorbell.

But sure, anyone facing similar issues might want to give the RTMP stream a try. That said, as far as I know, the original reason for preferring RTMP was a bug in older firmware versions that caused frame dropping in the RTSP stream - though that has likely been fixed by now.

PS: It remains a mystery to me how Reolink could decide not to allow the motion detection function to be disabled at all. I have no need for motion detection in this instance, yet it creates unnecessary load and consumes system resources.

Yeah the Dahua DB connected to the Dahua NVR would not need ONVIF, I could see where it would be a better match. How old is your Dahua NVR?

I run Max bitrate on my DB, and pretty high bitrates on all my cameras. I have an Enterprise network with Enterprise Manage Switches...she runs great...



In looking at BI, decided to up my bitrates on the CAMS. Gonna try 8192 up from 6144

Also, recently changed all my cameras from 15FPS to 30. Here, our new home in the woods, not really using the cameras as surveillance Cams like we did in our other house in the city. Here capturing wildlife/critters. There is a slight increase in CPU usage in Blue Iris but nothing to be concerned about. We will see when 5 more cameras are added.

 

[David L]

So I bought a used POE DB from a member here awhile back. Just noticed it has a newer firmware with the I-Frames.



One of the main reasons I did not up my firmware is the Diagnostic Logs I had available on the WiFi DB where many here stated they did not have that option with newer firmware but since I can Export a Diag. Log on this newer firmware POE DB I think I will be upping the firmware on my older WiFi DB My guess now is the Windows Client version I am using is what allows the Diag. Log...



As you can see I am running an older (Windows) Client:


What made me even notice the firmware difference was seeing this icon pop up when our dog was in view/motion. I put the POE DB in the Living Room temporarily, we wanted to see what our dogs do when we were away, all they do is sleep, no parties, lol.



I really want the I-Frames in BI to be 1.00 like all my other Cameras.

Ok, don't rib me about my Camera Naming, haha, I am still working on it, I want the location AND the direction of the view in the description, still trying to figure out a good naming scheme.

Here is a small example of this big Log file, it has alot, alot of info in it...which may be useful one day...

 

[Jim_OS]

the Dahua NVR would not need ONVIF, I could see where it would be a better match.

That said, connecting via ONVIF versus directly via API and port 37777 doesn't actually make a difference regarding the RTSP stream load. Of course, I don't know if there might be differences in terms of specific underlying processes.

How old is your Dahua NVR?

Old. It’s from late 2021 - and yes, it reached EOL a long time ago. Nevertheless, it continues to perform very well here.

My network setup here certainly isn't the problem. I’m using 2.5G managed switches (e.g., from Zyxel), and the Wi-Fi runs on an Asus XT8 mesh system dedicated solely to wireless connectivity.

Doorbell Wi-Fi Signal



As I mentioned earlier, I don't think the total load from various streams is the issue; rather, it likely comes down to the number of simultaneous processes the Reolink Wi-Fi doorbell can handle. Of course, I also can't rule out the possibility that a) there are additional bugs in the current firmware or b) integrating the doorbell with the NVR is having some sort of negative impact. I recently noticed again that whenever I throw another application (another HA VM) at the Reolink Wi-Fi doorbell, timeouts and connectivity issues start to pile up - which points to an "overload" situation, whatever the exact cause might be.

Right now, I don't have the time or inclination to keep looking for the exact potential cause. My new Dahua IPC-PTS2449C-4E3Z-S-PV-PRO should arrive next week; I’ll integrate it with the NVR to replace my Imou Cruiser Dual Lens. I’ll need to make a few changes in HA anyway at that point, so I’ll also consider whether to keep the Reolink Wi-Fi doorbell integrated with the NVR. I also won't need the motion detection (MD) feature currently activated via the Reolink's own MD function anymore; instead, I’ll use the NVR’s IVS functions (AI-by-recorder) for the Reolink. In fact, I haven't used standard motion detection for years - I’ve always used IVS with line detection. I am currently using the NVR's two available 2-channel perimeter detection slots (AI by NVR) for my Imou Cruiser Dual; however, since the IPC-PTS2449C-4E3Z-S-PV-PRO can handle this itself (--> AI by camera), that function on the NVR will become available again, allowing me to use it for the Reolink Doorbell Wi-Fi. I'll see...

After all, it would be boring otherwise if you weren't constantly tinkering with something - or having to.

I think I will be upping the firmware on my older WiFi DB

I’ll keep my fingers crossed that the problems don’t crop up for you as well when you update the firmware now.

 

[David L]

So I Did It!!! haha, after owning this WiFi DB since 01-2023, I finally upgraded the firmware, haha. And Yes the Diag. Log is still there, kewl so I can now confirm it is Client version related. Decided to stay with same firmware the POE DB had...so not the latest...2026-06-08 version...
Maybe Home Assistant will stop barking at me to upgrade my firmware now


I-Frame finally fixed in BI too. All 1.00s now...nice...


As those here that know me, I am not one to chase the latest firmware's. Not a good practice...unless your device is connected to the Internet, which also is not wise, and there is a new security update.

 

[David L]

That said, connecting via ONVIF versus directly via API and port 37777 doesn't actually make a difference regarding the RTSP stream load. Of course, I don't know if there might be differences in terms of specific underlying processes.

Old. It’s from late 2021 - and yes, it reached EOL a long time ago. Nevertheless, it continues to perform very well here.

My network setup here certainly isn't the problem. I’m using 2.5G managed switches (e.g., from Zyxel), and the Wi-Fi runs on an Asus XT8 mesh system dedicated solely to wireless connectivity.

Doorbell Wi-Fi Signal

View attachment 248629

As I mentioned earlier, I don't think the total load from various streams is the issue; rather, it likely comes down to the number of simultaneous processes the Reolink Wi-Fi doorbell can handle. Of course, I also can't rule out the possibility that a) there are additional bugs in the current firmware or b) integrating the doorbell with the NVR is having some sort of negative impact. I recently noticed again that whenever I throw another application (another HA VM) at the Reolink Wi-Fi doorbell, timeouts and connectivity issues start to pile up - which points to an "overload" situation, whatever the exact cause might be.

Right now, I don't have the time or inclination to keep looking for the exact potential cause. My new Dahua IPC-PTS2449C-4E3Z-S-PV-PRO should arrive next week; I’ll integrate it with the NVR to replace my Imou Cruiser Dual Lens. I’ll need to make a few changes in HA anyway at that point, so I’ll also consider whether to keep the Reolink Wi-Fi doorbell integrated with the NVR. I also won't need the motion detection (MD) feature currently activated via the Reolink's own MD function anymore; instead, I’ll use the NVR’s IVS functions (AI-by-recorder) for the Reolink. In fact, I haven't used standard motion detection for years - I’ve always used IVS with line detection. I am currently using the NVR's two available 2-channel perimeter detection slots (AI by NVR) for my Imou Cruiser Dual; however, since the IPC-PTS2449C-4E3Z-S-PV-PRO can handle this itself (--> AI by camera), that function on the NVR will become available again, allowing me to use it for the Reolink Doorbell Wi-Fi. I'll see...

After all, it would be boring otherwise if you weren't constantly tinkering with something - or having to.


I’ll keep my fingers crossed that the problems don’t crop up for you as well when you update the firmware now.

So you did not have the issues until a newer firmware? I will update if I have any issues with this newer firmware though since my POE DB has the same firmware and has been running fine kinda doubt my WiFi will present any issues, but we will see.

Curious to know if your new NVR has any issue(s) with the ReoLink DB. As we know, all cameras have their limits on streaming, CPU speeds, memory, etc. Can't say this ReoLink is in the same league as our Dahua CAMs but it does preform better than my previous Hik DB which I ran for 3+ years prior to this ReoLink which is almost 4 years old.

Also, the RTSP vs. RTMP issue was more of a Blue Iris thing, I may try RTSP now with this new firmware, though I think I already have the answer to this since I have been running the Living Room POE for a few months now using RTSP
So it must of been the older firmware...



Thanks for all your post, you got me to upgrade my firmware, lol, which this old man don't budge much, lol Also learned I could of upgraded a long time ago, in that I did not lose the Diag. Log.

 

[David L]

Well so much for HA stopping messaging about upgrading firmware

No biggies, I am use to Skipping Update...