180 was nice and mine was angled down to capture packages at the foot of my door. But it was too tall IMO, I did not need 180. You get alot of the ceiling of a porch with 180...guessing why 130 now...
New RCA HSDB2A 3MP Doorbell IP Camera
- Thread starter fleece
- Start date
Respectfully disagree. It all depends how far away someone would be standing. If the doorbell is right next to the door, a person could easily take up the majority of the frame top to bottom. I could do away with 10-20 degrees from the top, but definitely not 45. Additionally, doorbells angled down look stupid. Left or right is one thing, but angling the entire thing downward is a non-starter for me not only for athletics but also function (pressing the button is slightly more awkward). If they're going to reduce fov, they should be angling the camera downward within the doorbell so the doorbell can be mounted straight, like it should be. It's all just wrong. A video doorbell is to see people and packages right in front of your door. Nothing else. The floor area directly in front of the door is most important for packages. If someone wants to see more than that, like the road or their driveway, they should get another camera. This change fails to make sense to me. It must be cheaper. That's all I can think of.
Does anyone know what the "diagonal" fov is for this doorbell? Sometimes I only see a diagonal fov value while looking at other doorbells, and I can't find a diagonal fov value for this doorbell.
Does anyone know what the "diagonal" fov is for this doorbell? Sometimes I only see a diagonal fov value while looking at other doorbells, and I can't find a diagonal fov value for this doorbell.
It was only angled down a few degrees, not noticeable. It only takes a few degrees for cameras. What was noticeable was the angled brackets I had to use, 2 of them, since my doorbell wiring was on the side wall and not on the door wall/frame. You do what you have to do. As far as capturing someone, you have them walking up to the door which is plenty for Identifying someone, then when/if they pressed the doorbell, which is rare now a days, you will capture their face. The best captures I got was after they pushed the button or knocked they normally would step back and stand there posing for the camera 
, but these were mostly Solicitors or Neighbors...What I found over these last 4-5 years is I would get a motion notice (snapshot) of the delivery person, which really is all I needed to know I had a package at my front door. Some here have another camera facing their doormat or a mirror for packages.
It is all up to what works for you...
Last edited:
As an eBay Associate IPCamTalk earns from qualifying purchases.
Hello,
I'm coming into this discussion incredibly late. I recently purchased an RCA HSDB2A for my elderly mother. I went this route because of the price, no subscription fees, use existing wiring, and I can still (relatively easily) use the existing mechanical door chimes -- all of this was important.
From what I can gather, 2 way audio will only function through the cloud. I see Google has delisted the RCA app -- I did find the APK's floating around on questionable websites -- but if RCA is not maintaining the app, is it safe to assume the servers are also NFG?
And if so, if I were to crossflash to the Hikvision firmware, could I then use Hik-Connect (for 2 way audio) instead?
Thank-you!
I'm coming into this discussion incredibly late. I recently purchased an RCA HSDB2A for my elderly mother. I went this route because of the price, no subscription fees, use existing wiring, and I can still (relatively easily) use the existing mechanical door chimes -- all of this was important.
From what I can gather, 2 way audio will only function through the cloud. I see Google has delisted the RCA app -- I did find the APK's floating around on questionable websites -- but if RCA is not maintaining the app, is it safe to assume the servers are also NFG?
And if so, if I were to crossflash to the Hikvision firmware, could I then use Hik-Connect (for 2 way audio) instead?
Thank-you!
Welcome to IPCamTalk @noparking247.
It should work.
Personally took mine off the internet and switched it to older Hikvision firmware. It still works fine here. I did test it initially and the audio functions worked.
Nelly's Security NSC-DB2 NDB313-W V5.2.4 HikVision FW build 200321
Initially purchased the RCA camera which was registered to the cloud. It was used. RCA could not remove the account so I returned the camera.
When I was taking care of my elderly mother (93) (RIP) I moved her over to a Ring alarm infrastructure using a paid script.
It should work.
Personally took mine off the internet and switched it to older Hikvision firmware. It still works fine here. I did test it initially and the audio functions worked.
Nelly's Security NSC-DB2 NDB313-W V5.2.4 HikVision FW build 200321
Initially purchased the RCA camera which was registered to the cloud. It was used. RCA could not remove the account so I returned the camera.
When I was taking care of my elderly mother (93) (RIP) I moved her over to a Ring alarm infrastructure using a paid script.
Thank-you @pete_c -- greatly appreciate your help.
Sorry, for clarification you still think the RCA servers would still work? Or, would you move it over to the Hikvision firmware and use Hik-Connect?
What is "Nelly's Security NSC-DB2 NDB313-W V5.2.4 HikVision FW build 200321"? How would this build differ than the International 200321 Hikvision firmware?
(Apologies if these are stupid questions).
All the best!
Sorry, for clarification you still think the RCA servers would still work? Or, would you move it over to the Hikvision firmware and use Hik-Connect?
What is "Nelly's Security NSC-DB2 NDB313-W V5.2.4 HikVision FW build 200321"? How would this build differ than the International 200321 Hikvision firmware?
(Apologies if these are stupid questions).
All the best!
Last edited:
You should be able to use any of the Apps...only thing is some you have to unregister the doorbell to register it on the new App.
Check out our 101
⦁ Available Apps (Allows Remote Access):
iO/S: Hik-Connect, RCA Security, EZVIZ, LaView One, Guarding Vision
Android: Hik-Connect, RCA Security, EZVIZ, LaView ONE, Guarding Vision
⦁ Android 9 Hik-Connect Setup Help - Dewcal
⦁ In App be sure and change Hi-Def to Ultra HD
Last edited:
FW 200321 offers more features (ONVIF) for connectivity. Firmware is same domestically and internationally.
Last edited:
Just noticed RCA link is no good. Will this App work?
Just noticed RCA link is no good. Will this App work?
According to ChatGPT, no. But TBD. I plan to do a rough install of the doorbell at home soon before taking it to my mothers and will give it a shot.
Would you recommend I upgrade to the latest RCA firmware (if prompted)? Or, leave it as is (if I can), with the intention of likely going to the Hikvision firmware?
Personally I would configure it at home on your workbench leaving the firmware alone then updating to the Hikvision firmware.
On the workbench just attach a power cord to an AC doorbell transformer (buy it from Amazon then return it once you have completed your testing).
On the workbench just attach a power cord to an AC doorbell transformer (buy it from Amazon then return it once you have completed your testing).
If RCA's cloud is no more, you probably won't get a firmware update notice. The reason people use other firmwares, like Hikvision's is due to more features, like ONVIF. If it were me I would try the firmware on it and if it works, leave it alone. There is always a risk updating firmware via WiFi, though there is a way you can put the file on the SD-Card and do it, but I would check out our 101 for that.
Do you plan on RTSP to a recorder? NVR? Blue Iris? If so then you may want ONVIF for events from the Doorbell...though I never used ONVIF, I liked Blue Iris and how you can set motion zones/trips/intrusions, etc.
The PIR on the Doorbell is ok but did not work for me, that is why I used Blue Iris motion...
A bit of an update here -- unfortunately none of it is good.
I downloaded the modern "RCA Smart" app onto my Pixel and it refused to pair with the doorbell. I headed over to various APK sites and found a copy of the old "RCA Security" app. I installed it, and any time I try to register an account (either with e-mail or SMS) I get an error code.
At this point I figured "alright, neat -- time for Hikvision firmware" -- nope. I see it is broadcasting an SSID of "HSDB2_C5XXXXXX" -- I type in the verification code of "XXXXXX" and it is not enough characters. I tried various version of this -- lower case, a zero instead of an "o" -- same result.
Using my Pixel camera on the QR code, I see the contents are "rca c5XXXXXX XXXXXX hsdb2" -- fine, I'll try that. Nope. OK, I'll try with no spaces. Nope. No connection.
Any thoughts as to next step? My OCD/insaity does not like to be beaten by this.
I downloaded the modern "RCA Smart" app onto my Pixel and it refused to pair with the doorbell. I headed over to various APK sites and found a copy of the old "RCA Security" app. I installed it, and any time I try to register an account (either with e-mail or SMS) I get an error code.
At this point I figured "alright, neat -- time for Hikvision firmware" -- nope. I see it is broadcasting an SSID of "HSDB2_C5XXXXXX" -- I type in the verification code of "XXXXXX" and it is not enough characters. I tried various version of this -- lower case, a zero instead of an "o" -- same result.
Using my Pixel camera on the QR code, I see the contents are "rca c5XXXXXX XXXXXX hsdb2" -- fine, I'll try that. Nope. OK, I'll try with no spaces. Nope. No connection.
Any thoughts as to next step? My OCD/insaity does not like to be beaten by this.
Last edited:
Personally what I did while running my Lenova Tiny PC.
No smartphone app used.
Used / Using a Lenova Tiny is running W2016 standard Windows server. (XP, W7, W8, W10 and W11 should also work)
Note its been a long time that I have done this and I keep referring to AI Google searches which end up getting info from this website.
David, Alex and I put together this documentation from posts / user experiences here on the forum.
docs.google.com
1 - enable wireless on PC computer or laptop.
2 - look for the AP SSID name HSDB2_C50447266 of the doorbell
3 - the password is above. (RCA_XYOCVX or softap_XYOCVX) copy and paste your password.
4 - connect to the AP and find out the IP of the AP gateway.
5 - Run Hikvision Batch Configuration Version 3.2.0.6 (It will ask to update. Do not update)
6 - configure / add the IP of the doorbell to Hikvision Batch. It will connect fine in AP mode
7 - log in to the doorbell with admin and the password as described in the documentation.
8 - change the doorbell from AP mode to client mode putting in your home SSID and password.
IE: This unique password is also referred to as the "Verification Code" and is usually a 6-character, all-caps code found on the box or XYOCVX
9 - update to Hikvision firmware FW build 200321
10 - personally changed the admin password to a personal one and added user pete as a second admin (different from documentation - worked for me)
11 - enable ONVIF mode
12 - change the settings of the camera to your preferences. Static IP et al.
NOTE: when running multiple streams from DB; the DB would bounce and go to AP mode. All of the settings would stay the same. I used Batch Configuration to reset the DB back to client mode. I use a proxy now for the streams.
No smartphone app used.
Used / Using a Lenova Tiny is running W2016 standard Windows server. (XP, W7, W8, W10 and W11 should also work)
Note its been a long time that I have done this and I keep referring to AI Google searches which end up getting info from this website.
David, Alex and I put together this documentation from posts / user experiences here on the forum.
HIKVISION DOORBELL101
HIKVISION DOORBELL 101 HIKVISION (DS-HD1), RCA (HSDB2A), EZVIZ (DB1), LAVIEW (LV-PDB1630-U), NELLY'S (NSC-DB2), LTS (LTH-7132-WIFI) * NEW RCA OWNERS READ WARNINGS: SECTION * * IF YOUR CHIME AS RECENTLY (2020) STOPPED WORKING AFTER APP UPDATE, SEE TROUBLESHOOTING TIPS: SECTION: * (DO NOT UPGRADE T...
docs.google.com
1 - enable wireless on PC computer or laptop.
2 - look for the AP SSID name HSDB2_C50447266 of the doorbell
3 - the password is above. (RCA_XYOCVX or softap_XYOCVX) copy and paste your password.
4 - connect to the AP and find out the IP of the AP gateway.
5 - Run Hikvision Batch Configuration Version 3.2.0.6 (It will ask to update. Do not update)
6 - configure / add the IP of the doorbell to Hikvision Batch. It will connect fine in AP mode
7 - log in to the doorbell with admin and the password as described in the documentation.
8 - change the doorbell from AP mode to client mode putting in your home SSID and password.
IE: This unique password is also referred to as the "Verification Code" and is usually a 6-character, all-caps code found on the box or XYOCVX
9 - update to Hikvision firmware FW build 200321
10 - personally changed the admin password to a personal one and added user pete as a second admin (different from documentation - worked for me)
11 - enable ONVIF mode
12 - change the settings of the camera to your preferences. Static IP et al.
NOTE: when running multiple streams from DB; the DB would bounce and go to AP mode. All of the settings would stay the same. I used Batch Configuration to reset the DB back to client mode. I use a proxy now for the streams.
- Concurrent Streams Limit: User experiences suggest the camera can become overloaded and unreliable if forced to provide too many concurrent streams (e.g., cloud stream, NVR stream, and multiple Home Assistant streams). The reliable limit is reported to be around three streams.
- Workaround for More Streams: To manage multiple downstream uses without overloading the doorbell camera, users recommend using a proxy function of an NVR or a local server (like NGINX with rtmp plugin) to pull a single stream from the doorbell and then distribute it to multiple clients or services.
Last edited:
Back when I had my Doorbell I used EZVIZ App. It works on all the different brands of this Doorbell. Or at least, use to...
A bit of a lackluster update here, but hopefully it can benefit others.
The "RCA Security" app has been removed from the Google Play store. The latest APK I could find was "RCA Security 3.11.2.0830" -- however, after loading this it was largely useless. When I attempted to create an account it would throw an error. It did so with both e-mail and phone # registration. The "RCA Smart Home" app is present but refuses to acknowledge this doorbell camera. If you try to add it manually there is no valid option, and the QR code fails as well.
Luckily, my mother has an iPhone. The "RCA Security" app is still valid in the Apple AppStore. I downloaded and installed the app, created an account using her e-mail address, and was able to successfully add the camera to the app. Upon doing so, I was prompted to upgrade from V5.2.4 build 180809 to V5.2.4 build 190124 -- to which I did. After ~2-3 minutes the update was successful, and I was able to configure the camera. However, when I clicked on the camera to view the stream it would immediately kill the app. I rebooted the phone, same thing.
I tried logging in using the aforementioned account on Android, but got the same error message I got when I tried creating an account -- so, Android is out.
I went back to the AppStore to see if there was an update and noticed another app called "Guarding Vision" -- I clicked it, and one of the comments specifically called out my scenario, so I figured it was worth a shot. In typical Hikvision fashion, the app was not perfect but usable -- I created an account using the same address as above, activated it, and when I logged in was met with a prompt essentially saying "We see your existing account on previous partners servers -- is it OK if we migrate yours over?" -- I hit "yes" -- and was prompted to enter my verification code (which I did). Within a couple seconds, my camera was showing real-time. I did a couple test calls on the bench and it seems to be working great with my mothers iPhone.
At this point I'm not sure what the next steps should be. On one hand I'm thinking it would be wise to factory reset the device + delete it from the "RCA Security" app, and the "Guarding Vision" app, to avoid being locked into one or the other. "Guarding Vision" seems to work -- so I'm unsure if I should proceed with fixing it until I break something, or leave well enough alone...
(Again, thank-you all for your help thus far)
The "RCA Security" app has been removed from the Google Play store. The latest APK I could find was "RCA Security 3.11.2.0830" -- however, after loading this it was largely useless. When I attempted to create an account it would throw an error. It did so with both e-mail and phone # registration. The "RCA Smart Home" app is present but refuses to acknowledge this doorbell camera. If you try to add it manually there is no valid option, and the QR code fails as well.
Luckily, my mother has an iPhone. The "RCA Security" app is still valid in the Apple AppStore. I downloaded and installed the app, created an account using her e-mail address, and was able to successfully add the camera to the app. Upon doing so, I was prompted to upgrade from V5.2.4 build 180809 to V5.2.4 build 190124 -- to which I did. After ~2-3 minutes the update was successful, and I was able to configure the camera. However, when I clicked on the camera to view the stream it would immediately kill the app. I rebooted the phone, same thing.
I tried logging in using the aforementioned account on Android, but got the same error message I got when I tried creating an account -- so, Android is out.
I went back to the AppStore to see if there was an update and noticed another app called "Guarding Vision" -- I clicked it, and one of the comments specifically called out my scenario, so I figured it was worth a shot. In typical Hikvision fashion, the app was not perfect but usable -- I created an account using the same address as above, activated it, and when I logged in was met with a prompt essentially saying "We see your existing account on previous partners servers -- is it OK if we migrate yours over?" -- I hit "yes" -- and was prompted to enter my verification code (which I did). Within a couple seconds, my camera was showing real-time. I did a couple test calls on the bench and it seems to be working great with my mothers iPhone.
At this point I'm not sure what the next steps should be. On one hand I'm thinking it would be wise to factory reset the device + delete it from the "RCA Security" app, and the "Guarding Vision" app, to avoid being locked into one or the other. "Guarding Vision" seems to work -- so I'm unsure if I should proceed with fixing it until I break something, or leave well enough alone...
(Again, thank-you all for your help thus far)