New Reolink Wired POE Doorbell Cam ?

[Jim_OS]

This has probably been discussed on the previous 94 pages, but I didn't want to go through them all again.

I'm using:
Reolink Video Doorbell WiFi (D340W)
Hardware: DB_566128M5MP_W
Firmware: v3.0.0.6460_2605211897

and I've now installed the latest firmware (May 2026). Even with the older firmware version, I had the problem that the day/night switching and vice versa repeatedly triggered motion detection and thus recording. This is something I've never experienced with my Dahua cameras and, of course, don't want.

I've already reduced the motion detection sensitivity to 9, but that didn't really help. I still have the sensitivity for person, vehicle, and pet detection set to 50 because I don't think these settings affect recordings during the day/night switching. Or do they?

Is there any useful setting to prevent recordings during the day/night switch?

Instead of various screenshots from the Reolink app, here are the relevant settings via the Reolink integration in Home Assistant.



By the way: The timeouts I mentioned above when accessing the Doorbell WebGUI still occur for me even with the newer firmware version. As mentioned previously, I suspect that the CPU simply cannot cope when "too many" devices access or are connected to the doorbell at the same time. In my case, these are:

• Reolink App
• Dahua NVR
• Home Assistant

If a client also accesses the WebGUI, it seems to be "too much" for the Doorbell. But as long as there aren't any good alternatives to the Reolink Doorbell WiFi that also offer and fulfill the points I mentioned in #1880, I'll have to continue living with the Reolink Doorbell Wifi.

 

[David L]

How is the Dog or Animal motion detection? Just curious...

 

[Jim_OS]

Hi Dave

I don't quite understand your question. Do you want to know how I configured them – which is already visible in the screenshot – or how well or poorly they work with the current setting (49%)?

Dogs don't roam around my property, but cats seem to be detected quite well – at least at night. However, I can't really judge this yet, as I haven't been using the Reolink Doorbell in practice for very long.

 

[David L]

Hi Dave

I don't quite understand your question. Do you want to know how I configured them – which is already visible in the screenshot – or how well or poorly they work with the current setting (49%)?

Dogs don't roam around my property, but cats seem to be detected quite well – at least at night. However, I can't really judge this yet, as I haven't been using the Reolink Doorbell in practice for very long.

Thanks, yeah was just curious how good it detects. I use AI in Blue Iris so was just wondering...CodeProject.AI works pretty good for me...

I see 2025-03-12 they added AI-Animal support in firmware 4662_2503122270 & 4662_2503122271

 

[Jim_OS]

As I said, I can't really say much about it yet, except that there are recordings with "Animal" in the recordings, and I can see recordings of cats there. But I can't really judge how well or poorly cats - or other animals of that size - are recognized, because I don't know when which animals are around the doorbell. In other words, are animals really recognized reliably, or more by chance?

Currently, there's also the problem that I can only view the Reolink recordings via the Reolink app and not via Home Assistant, because there seems to be a bug with the HA Reolink integration. The Reolink integration accesses the SD card in the Reolink doorbell, and this only works once. As soon as you try to open another recording, the connection freezes,

Logger: homeassistant.components.reolink.views
Quelle: components/reolink/views.py:123
Integration: Reolink (Dokumentation, Probleme)
Erstmals aufgetreten: 17:14:25 (2 Vorkommnisse)
Zuletzt protokolliert: 17:15:11

Reolink playback error while getting mp4: Server disconnected
Reolink playback error while getting mp4: Timeout on reading data from socket

and the Reolink doorbell has to be restarted before the HA Host can re-establish a connection. Simply restarting the HA Host isn't enough.

By the way: The AI detection (person, vehicle, pets) of the Reolink Doorbell isn't available via ONVIF either. With my Dahua NVR, to which the Reolink Doorbell is integrated via ONVIF, there are only the standard motion alerts and nothing about people, vehicles, or animals/pets. That means the cat recordings don't appear on the Dahua NVR at all. But okay, I didn't expect anything different with the Reolink + Dahua NVR and ONVIF combination. But I still wanted to mention it in connection with your question about animals.

Edit and PS: I'll be offline again until tomorrow.

 

[David L]

As I said, I can't really say much about it yet, except that there are recordings with "Animal" in the recordings, and I can see recordings of cats there. But I can't really judge how well or poorly cats - or other animals of that size - are recognized, because I don't know when which animals are around the doorbell. In other words, are animals really recognized reliably, or more by chance?

Currently, there's also the problem that I can only view the Reolink recordings via the Reolink app and not via Home Assistant, because there seems to be a bug with the HA Reolink integration. The Reolink integration accesses the SD card in the Reolink doorbell, and this only works once. As soon as you try to open another recording, the connection freezes,

Logger: homeassistant.components.reolink.views
Quelle: components/reolink/views.py:123
Integration: Reolink (Dokumentation, Probleme)
Erstmals aufgetreten: 17:14:25 (2 Vorkommnisse)
Zuletzt protokolliert: 17:15:11

Reolink playback error while getting mp4: Server disconnected
Reolink playback error while getting mp4: Timeout on reading data from socket

and the Reolink doorbell has to be restarted before the HA Host can re-establish a connection. Simply restarting the HA Host isn't enough.

By the way: The AI detection (person, vehicle, pets) of the Reolink Doorbell isn't available via ONVIF either. With my Dahua NVR, to which the Reolink Doorbell is integrated via ONVIF, there are only the standard motion alerts and nothing about people, vehicles, or animals/pets. That means the cat recordings don't appear on the Dahua NVR at all. But okay, I didn't expect anything different with the Reolink + Dahua NVR and ONVIF combination. But I still wanted to mention it in connection with your question about animals.

Edit and PS: I'll be offline again until tomorrow.

Thanks for the info, I am sure this will help those here that use the ReoLink App.

I have never used it, don't plan too, I am anti-cloud When we get motion alerts on our phones, we have the Home Assistant App to jump to for viewing. Also use UI3 webserver in Blue Iris to get all our present/previous footage. We have a VPN client on our phones that connect to our VPN home server when connecting to Blue Iris/Our Cameras (which neither are connected to the Internet). Only way to get to them remotely is via VPN...

Interesting that ReoLink ONVIF don't pass on motion alerts for humans/animals/vehicle.

 

[Jim_OS]

Interesting that ReoLink ONVIF don't pass on motion alerts for humans/animals/vehicle.

Unfortunately, limitations of this kind are common among many manufacturers, which makes it difficult for me to find cameras that make all their features available via ONVIF when integrated into Home Assistant and/or my Dahua NVR.

The "worst" offenders are the manufacturers who advertise AI features but only make them available if the camera is connected to the manufacturer's cloud via their app. At least that isn't the case with Reolink.

Other examples regarding this issue:
1. With Tapo dual-lens cameras (like the C545D), only the wide-angle lens stream is available when connecting to a PC, NAS, or NVR via ONVIF.
2. With my Imou Cruiser Dual - which the NVR recognizes directly as an OEM model and allows to be integrated via port 37777 - the camera's person and vehicle detection features are unavailable on the NVR or HA.
3. Since I’m still looking for an alternative doorbell: Take the Aqara G400, for instance; even though it supports ONVIF, the AI-based person and vehicle detection features aren't available via that protocol.
4. Etc.

Unfortunately, few manufacturers provide details about potential ONVIF limitations, so you usually only find out about them through other users' experiences or by testing the camera yourself.

we have the Home Assistant App

It’s interesting that you use HA as well. That means you’ve probably had your fair share of headaches with your Dahua cameras over the years. Unfortunately, rroller is no longer actively developing his Dahua integration; he only fixes issues or bugs following HA updates every now and then - and usually only when another user posts a suggested solution. I stopped using the Dahua integration a long time ago because it caused too many problems and errors with my Dahua cameras and NVR; I reported these issues to rroller back then, but he never actually fixed them.

Integrating Dahua cameras via the ONVIF integration in HA also comes with its own set of problems and errors. For instance, issues crop up from time to time with go2rtc, which has been part of HA Core since late 2025. There’s also the issue where the "IVS – Line Detector Crossed" feature appears as a sensor under "Diagnostics" rather than as a binary sensor under "Sensors." Getting cameras integrated into HA with minimal issues has cost me a lot of time and given me quite a few gray hairs over the last six years. Just when you think you’ve finally got everything under control, the next HA update (or the one after that) brings a whole new batch of problems.

 

[David L]

Ai (CodeProject.AI) in Blue Iris, works pretty good, but animals are hard to identify at times...here is an example...



AI did good in identifying our dog but AI also threw in there it may be a pig.



But as you can see a minute later AI identified our dog as a cat or pig...grant it, this is our Thermal CAM but it happens on our other cameras including the ReoLink Doorbell too.



Guess it is just which frame AI choses to use in identifying...hopefully AI will improve. For animals, we found we can easily identify them by the way they walk/move.

I got a long list of Identifiers/Labels for the AI models we use...

person,vehicle,car,truck,bird,cat,dog,horse,sheep,cow,bear,deer,rabbit,raccoon,fox,skunk,squirrel,pig

 

[Jim_OS]

Ai (CodeProject.AI) in Blue Iris,

I know BI seems to be very popular in the US, but here in Germany - and Europe in general - very few users actually use it. I don't use it myself, either. Besides, I haven't used Windows for years either; I use only Linux now. Instead, I’ll probably give Frigate and OpenVINO another shot, though the older machines I use for Proxmox and HA (with Core i3-7100 and i3-8100 CPUs) are simply too weak to handle five cameras. We'll see...

But since the whole AI/animal discussion is somewhat off-topic for this thread, perhaps we shouldn't delve any deeper into it. Otherwise, a mod might tell us off.

 

[David L]

I know BI seems to be very popular in the US, but here in Germany - and Europe in general - very few users actually use it. I don't use it myself, either. Besides, I haven't used Windows for years either; I use only Linux now. Instead, I’ll probably give Frigate and OpenVINO another shot, though the older machines I use for Proxmox and HA (with Core i3-7100 and i3-8100 CPUs) are simply too weak to handle five cameras. We'll see...

But since the whole AI/animal discussion is somewhat off-topic for this thread, perhaps we shouldn't delve any deeper into it. Otherwise, a mod might tell us off.

Off-Topic is my middle name, lol

But AI can be discussed in all Camera Threads...

One thing sweet about Blue Iris is being able to use a quite older PC, running Windows (Windows Server preferred) and having no problems with 8 or 10 cameras.

I presently have 5 CAMs running, I disabled an indoor cam to post this pic...other Delivery CAM is a clone I am experimenting with. But as you can see on this Windows 11 PC (i7-4770k), Blue Iris has no problem, CPU running at 20%






Let me add; all cameras are recording continuous 24/7 plus sending motion notices to HA. I have 5 more cameras I will be adding...will be changing boxes, upgrading from i7-4770K to i7-6700K, lol, when I switch from BI5 to BI6. I still laugh looking at these old PCs still running great...

My BI PC has Zero access to the Internet, so no annoying Windows Updates...only time I ever manually connect is to update BI.




I have several Linux boxes too, really wish Blue Iris had a Linux version...but it is what it is, no complaints here. Blue Iris is top notch. I am not a fan of proprietary NVRs, Blue Iris has a ton more great options...and most every one has an old PC laying around...

 

[TheWaterbug]

I saw that, too, but literally saw a listing on Amazon with the option of white or black. I clicked back on it, and now it's only the black one.

Ugh. I have one application where the tall/narrow FOV of the White POE version would be great, but I also am seeing no availability of the White version, either on Reolink's site, nor on amazon.

But the good news is that, while madly clicking around the internet to try and find the White model, I did see that Walmart has the Black POE for $90 ($30 off):


Ordered!

Maybe I'll just mount it sideways

 

[Jim_OS]

To revisit the issue of recordings being triggered during the day/night and night/day transitions:

I'm using:
Reolink Video Doorbell WiFi (D340W)
Hardware: DB_566128M5MP_W
Firmware: v3.0.0.6460_2605211897

and I've now installed the latest firmware (May 2026). Even with the older firmware version, I had the problem that the day/night switching and vice versa repeatedly triggered motion detection and thus recording.

I’ve since lowered the detection sensitivity settings further - even setting the motion detection level to just 1.




Yet, the Reolink doorbell still captures two recordings every day - one in the evening and another in the morning.

Do you guys not have this problem with your Reolink doorbells (Wifi)? Or has this already been discussed, with the conclusion being that we just have to live with it because it’s a bug Reolink can’t seem to fix?

 

[TonyR]

Note: The new Reolink Battery Video Doorbell (2nd Gen) is simply too new (for me), and there is currently too little real-world user feedback available.

And no battery-powered video doorbell or camera from Reolink or TP-LINK will stream video via RTSP (the TP-LINK has an option jumper on their battery / wired version to stream RTSP but only if on wired power).

 

[Jim_OS]

That is generally correct, though I am not certain regarding the RTSP stream feature on the Reolink Battery Video Doorbell (2nd Gen). The Reolink Battery Video Doorbell (2nd Gen) can indeed be powered via a doorbell transformer, though this power supply primarily serves to trickle-charge the battery. However - unlike the first generation of Reolink doorbells the Reolink Battery Video Doorbell (2nd Gen) allows for the operation of an existing chime. Additionally, the Reolink Battery Video Doorbell (2nd Gen) supports 24-hour recording when powered (additionally) via a doorbell transformer.

Information from the Reolink FAQ on this topic:

Can I pair this doorbell with my mechanical chime?
Yes. In Battery Mode, the doorbell can ring a compatible mechanical chime when connected to an 8–24VAC, 5VA–40VA transformer.
In Wired Power Mode, keeping the mechanical chime active requires 16–24VAC power and the RLA-PK1 Power Kit (sold separately).

Does the Reolink Video Doorbell (2nd Gen) support pre-recording and 24/7 continuous recording? Will my existing chime still work?
Yes, it does. Connect the Reolink Video Doorbell (2nd Gen) to a 16-24V AC power supply and enable Wired Power Mode for always-on operation, pre-recording, and 24/7 recording.
Please note that full 24/7 recording will be available when the doorbell is used as a standalone unit. 24/7 recordings will be stored only on the doorbell's microSD card, while motion recordings will be kept on an NVR or Hub (if any).

In other words, theoretically, it might be possible to have an RSTP stream available 24/7 even when powered by a doorbell transformer. At the very least, there is no obvious reason why this couldn't be implemented just as TP-Link does with the Tapo Doorbell. However, I don't actually know if that is the case.

 

[David L]

That is generally correct, though I am not certain regarding the RTSP stream feature on the Reolink Battery Video Doorbell (2nd Gen). The Reolink Battery Video Doorbell (2nd Gen) can indeed be powered via a doorbell transformer, though this power supply primarily serves to trickle-charge the battery. However - unlike the first generation of Reolink doorbells the Reolink Battery Video Doorbell (2nd Gen) allows for the operation of an existing chime. Additionally, the Reolink Battery Video Doorbell (2nd Gen) supports 24-hour recording when powered (additionally) via a doorbell transformer.

Information from the Reolink FAQ on this topic:

Can I pair this doorbell with my mechanical chime?
Yes. In Battery Mode, the doorbell can ring a compatible mechanical chime when connected to an 8–24VAC, 5VA–40VA transformer.
In Wired Power Mode, keeping the mechanical chime active requires 16–24VAC power and the RLA-PK1 Power Kit (sold separately).

Does the Reolink Video Doorbell (2nd Gen) support pre-recording and 24/7 continuous recording? Will my existing chime still work?
Yes, it does. Connect the Reolink Video Doorbell (2nd Gen) to a 16-24V AC power supply and enable Wired Power Mode for always-on operation, pre-recording, and 24/7 recording.
Please note that full 24/7 recording will be available when the doorbell is used as a standalone unit. 24/7 recordings will be stored only on the doorbell's microSD card, while motion recordings will be kept on an NVR or Hub (if any).

In other words, theoretically, it might be possible to have an RSTP stream available 24/7 even when powered by a doorbell transformer. At the very least, there is no obvious reason why this couldn't be implemented just as TP-Link does with the Tapo Doorbell. However, I don't actually know if that is the case.

ReoLink, this makes no sense, for your/their Battery Doorbell to be able to connect to an existing chime while their other Doorbells can't? I get the first gen push for their own Chime, I have one, we got use to the chime even though at the time of purchase I would of liked to use our existing chime, the old mechanical chimes are what we grew up with, it has its distinct sound, kinda like the old U.S. Bell phones and their mechanical bell ringers.

24/7 recording to a SD-Card is ridiculous, IMO. The Norm is Motion only recording for backup on a SD-Card., I have them in all my cameras...

I thought the whole idea for a Battery Doorbell is for a no power/wired install? What am I missing here? If you can install with existing wired power, why even have a battery? Don't want to hear, in case of power outages, that is not a good reason...

Today's Engineers are Special people, haha, yellow bus special...LOL

 

[Jim_OS]

Regarding the battery and doorbell transformer power supply: It’s better to have more features than too few. Besides, the battery needs regular charging anyway; connecting it to a doorbell transformer handles that charging - or at least provides a trickle charge.

24/7 recording: Again, better to have it and not need it than to need it and not have it. You don't have to use it, after all.

As for connecting to an existing doorbell or chime: I had that setup with my Dahua OEM models (Amcrest AD110 and Imou DB61i), and I really miss it with the Reolink Doorbell Wi-Fi. The included chime isn't exactly a champion of range. There’s a hallway behind my front door that’s about 6 meters long. Unfortunately, there’s only one power outlet, located on the wall opposite the front door. If I plug the Reolink chime in there, the doorbell can't connect to it, and the chime can't be paired or operated from that spot. Fortunately, the kitchen is right to the right as you enter the front door; there’s an power outlet near the kitchen door - only about 3 meters away from the front door and the doorbell. If I use that power outlet for the chime, it pairs and operates successfully. However, if I close the kitchen door, that’s sometimes enough for the chime to lose its connection to the doorbell.

Yes, I could consider installing another power outlet in the hallway closer to the front door and/or trying to use a Reolink Hub to improve things, but that involves a) work and b) cost.

 

[David L]

Regarding the battery and doorbell transformer power supply: It’s better to have more features than too few. Besides, the battery needs regular charging anyway; connecting it to a doorbell transformer handles that charging - or at least provides a trickle charge.

So why have a battery? Doesn't make sense. I know all Doorbell CAMs have batteries/capacitors to keep settings but not for camera power...so again, why have only the Battery Doorbell be able to connect to an existing chime? Like having an EV car with a gas generator in the trunk.

Prior to the ReolInk I had the Hikvision Doorbell. It was the best on the market at that time. It did everything we all wanted except Ethernet wired. We have a 381 page Thread dedicated just to that Doorbell. We had many firmwares to chose from, alot of options and with Hik's Batch Config Tool we could change most everything the Doorbell had to offer. ReoLink is no where close...or atleast I am not aware of any such tool...

F

Thread 'New RCA HSDB2A 3MP Doorbell IP Camera'

Aug 18, 2018

Has anyone gotten their hands on one yet? Is it a Hik rebrand as well? RTSP/ONVIF support?

The specs look promising otherwise. 3MP, 5GHz wifi, and I really like the included up/down/side tilt mounting plates.

RCA : Home Security : HSDB2A

Moderator edit: Please see this post for a great installation write-up

• fleece
• Replies: 7,610
• Forum: Doorbells

• 

Doorbell 101:

Post in thread 'New RCA HSDB2A 3MP Doorbell IP Camera'

Jan 8, 2020

HIKVISION DOORBELL101
HIKVISION (DS-HD1), RCA (HSDB2A), EZVIZ (DB1), LAVIEW (LV-PDB1630-U), NELLY'S (NSC-DB2), LTS (LTH-7132-WIFI)

OFFLINE 101

* NEW RCA OWNERS READ WARNINGS: SECTION *
* IF YOUR CHIME AS RECENTLY (2020) STOPPED WORKING AFTER APP UPDATE, SEE TROUBLESHOOTING TIPS: SECTION: LINK *...​

• David L

• 

 

[Jim_OS]

I know all Doorbell CAMs have batteries/capacitors to keep settings but not for camera power...so again, why have only the Battery Doorbell be able to connect to an existing chime?

That actually makes sense, because then you presumably don't need an additional battery (or capacitor) - unlike with the Amcrest AD410 or Imou DB61i, for example. It simply runs off the battery, which also allows the doorbell to operate on its own without a chime transformer. But if you want to know exactly why Reolink offers something like that, you'd probably have to ask Reolink directly.

Yes, I’m familiar with the Hikvision OEM model(s) and the discussions about it here, but that has nothing to do with the Reolink Doorbell - and there’s no point in lamenting discontinued models from Hikvision or Dahua. The Dahua DB6I (aka Amcrest AD410 or Imou DB61i) was exactly what I needed here, too, but the fact is, it’s no longer available.

 

[adolphora5]

ReoLink, this makes no sense, for your/their Battery Doorbell to be able to connect to an existing chime while their other Doorbells can't? I get the first gen push for their own Chime, I have one, we got use to the chime even though at the time of purchase I would of liked to use our existing chime, the old mechanical chimes are what we grew up with, it has its distinct sound, kinda like the old U.S. Bell phones and their mechanical bell ringers.

24/7 recording to a SD-Card is ridiculous, IMO. The Norm is Motion only recording for backup on a SD-Card., I have them in all my cameras...

I thought the whole idea for a Battery Doorbell is for a no power/wired install? What am I missing here? If you can install with existing wired power, why even have a battery? Don't want to hear, in case of power outages, that is not a good reason...

Today's Engineers are Special people, haha, yellow bus special...LOL

Good news: REOLING is cheap comparing to other cameras...

 

[Jim_OS]

The timeouts occurring when accessing the Reolink doorbell's web GUI are likely due either to insufficient CPU performance when the doorbell is running on Wi-Fi -especially when the web GUI is also being accessed - and/or simply because the web GUI isn't well-programmed.
Other users have reported these WebGUI access timeouts, and I actually encountered the same issue myself when testing the Reolink Doorbell in 2024. I had just hoped that Reolink had managed to get a handle on it by now.

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:



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.