New RCA HSDB2A 3MP Doorbell IP Camera

I mounted my DB1 on the same position as my old dorbell. As the DB1 is smaller (46 mm) than my old doorbell (diameter ca. 60 mm), its imprint can be seen behind the DB1 (which bothers me).
For the Nest doorbell there are several wall back plates available which would cover the imprint. This link show some examples : The best covers and wall plates for your Nest Hello doorbell
Does anybody know if something simular is available for the DB1 or has a own solution?
I have some ideas to manufacture something for myself but if its commercially available.......
 
  • Like
Reactions: David L
Jack007 said:
I mounted my DB1 on the same position as my old dorbell. As the DB1 is smaller (46 mm) than my old doorbell (diameter ca. 60 mm), its imprint can be seen behind the DB1 (which bothers me).
For the Nest doorbell there are several wall back plates available which would cover the imprint. This link show some examples : The best covers and wall plates for your Nest Hello doorbell
Does anybody know if something simular is available for the DB1 or has a own solution?
I have some ideas to manufacture something for myself but if its commercially available.......
Click to expand...
I am not aware of any, let us know what you come with. Do you have a 3D printer?
 
David L said:
I am not aware of any, let us know what you come with. Do you have a 3D printer?
Click to expand...
No, i don't have a 3d-printer.

As the DB1 is mounted on a flat stone surface, I was thinking of making a brushed stainless steel backplate (1 mm thick) which is about 5 mm wider and taller than the standard backplate. This should be enough to cover the imprint of the old doorbell and give a nice finish.
As i don't want to disassemble the DB1 yet, do you (or anybody else) know the dimesnions of the standard mounting plate (length x width, position of the 2 mounting holes.?
 
  • Like
Reactions: David L
Jack007 said:
No, i don't have a 3d-printer.

As the DB1 is mounted on a flat stone surface, I was thinking of making a brushed stainless steel backplate (1 mm thick) which is about 5 mm wider and taller than the standard backplate. This should be enough to cover the imprint of the old doorbell and give a nice finish.
As i don't want to disassemble the DB1 yet, do you (or anybody else) know the dimesnions of the standard mounting plate (length x width, position of the 2 mounting holes.?
Click to expand...
So here is what I found so far, there have been many here that made custom mounts.

New RCA HSDB2A 3MP Doorbell IP Camera

New RCA HSDB2A 3MP Doorbell IP Camera
 
  • Like
Reactions: Jack007
So a note to RCA / Nelly's firmware bricks... I noticed while looking for measurements for Jack007, Nelly's listed firmware date is from last year in June, except if you download it now, it has a Nov. date., but same build number 190625 (2019-11-22) Did Nelly's change something to hinder their firmware and that is why the RCA units bricked for so many? Just a thought.

www.nellyssecurity.com

3MP Wi-Fi Video Doorbell ONVIF Compliant IP Camera with 2 Way Audio, PIR Motion Sensor, Night Vision, 16GB SD Card Pre-Installed, and 3 Face Plates (NSC-DB2)

Video Doorbell Camera delivering 3MP of crisp clear video Dual Band Wifi (2.4Ghz / 5GHz) to reach all types of routers and wireless access points PIR Motion Detection to detect true human movement. Much less false motion events than standard pixel based motion. Clear Night Vision up to 16' -...
www.nellyssecurity.com www.nellyssecurity.com
1580474213743.png
 
  • Like
Reactions: Jack007
David L said:
So a note to RCA / Nelly's firmware bricks... I noticed while looking for measurements for Jack007, Nelly's listed firmware date is from last year in June, except if you download it now, it has a Nov. date., but same build number 190625 (2019-11-22) Did Nelly's change something to hinder their firmware and that is why the RCA units bricked for so many? Just a thought.

www.nellyssecurity.com

3MP Wi-Fi Video Doorbell ONVIF Compliant IP Camera with 2 Way Audio, PIR Motion Sensor, Night Vision, 16GB SD Card Pre-Installed, and 3 Face Plates (NSC-DB2)

Video Doorbell Camera delivering 3MP of crisp clear video Dual Band Wifi (2.4Ghz / 5GHz) to reach all types of routers and wireless access points PIR Motion Detection to detect true human movement. Much less false motion events than standard pixel based motion. Clear Night Vision up to 16' -...
www.nellyssecurity.com www.nellyssecurity.com
View attachment 54876
Click to expand...
@David L
This has been my thinking all along, but had nothing, in the way of proof.

I now think that what you've just found, (in the way of firmware date changes for the same build#), just might be the missing link, and or proof. It makes since to me anyway.

On that note,
Do we have any confirmed bricked RCA units after attempting to update via Laview, or have all the affected users Bricked while updating to Nelly's?

If the latter is the case, and if our theory from David L's "last post" is correct, and we have, a good copy of the older of the 2 "Nelly's 190625 firmware file"?

Assuming the above to be true,

I would think all that would be needed, to confirm,
would be a guinea pig
"so to speak"


Our Guinea Pig would need

1.
To be willing to accept, the consequences of a bricked device if all goes to shit!

2.
An RCA Doorbell Cam, "preferably within the applicable return period in case, "1 from above" is the end result, thus minimizing, and or off-putting the cost of said consequence.

3.
The June issue of the Nelly's firmware file, build# 190625 and again with the June "Not Nov." build date.



Thinking out Loud,
I bet Nelly's Security was getting bombarded with questions about updating, "non Nelly's sub-branded doorbell-cams" using Nelly's firmware to gain ONVIF + ALexa features. and decided to nip the problem in the bud.
While it makes me sad to say, most of the people asking, the said questions, were probably armed with information from this beloved thread.

Thoughts?

...
.
 
Last edited:
  • Like
Reactions: David L
phatboyj said:
@David L
This has been my thinking all along, but had nothing, in the way of proof.

I now think that what you've just found, (in the way of firmware date changes for the same build#), just might be the missing link, and or proof. It makes since to me anyway.

On that note,
Do we have any confirmed bricked RCA units after attempting to update via Laview, or have all the affected users Bricked while updating to Nelly's?

If the latter is the case, and if our theory from David L's "last post" is correct, and we have, a good copy of the older of the 2 "Nelly's 190625 firmware file"?

Assuming the above to be true,

I would think all that would be needed, to confirm,
would be a guinea pig
"so to speak"


Our Guinea Pig would need

1.
To be willing to accept, the consequences of a bricked device if all goes to shit!

2.
An RCA Doorbell Cam, "preferably within the applicable return period in case, "1 from above" is the end result, thus minimizing, and or off-putting the cost of said consequence.

3.
The June issue of the Nelly's firmware file, build# 190625 and again with the June "Not Nov." build date.



Thinking out Loud,
I bet Nelly's Security was getting bombarded with questions about updating, "non Nelly's sub-branded doorbell-cams" using Nelly's firmware to gain ONVIF + ALexa features. and decided to nip the problem in the bud.
While it makes me sad to say, most of the people asking, the said questions, were probably armed with information from this beloved thread.

Thoughts?

...
.
Click to expand...
So to add, even though I did not find any post of RCA users upgrading to Nelly's June firmware, it is still hard for me to believe there were none. Also, if anyone did brick their unit we would definitely hear about it here. So there is still hope LaView's may work.

Unless I missed a message, I don't believe we have anyone who recently purchased a RCA update to LaView. If anyone does successfully do so then we can positively blame it on Nelly's firmware.

So I have possible good and bad news. I am pretty sure I have a copy of the June firmware (I was saving each just for this reason and I am hoping I did not overwrite it with the Nov. same build # one). Bad news is my PC motherboard died a few weeks ago in which I did receive a replacement, But as of last night I have not been able to get any video upon boot. Still working on it, but I am also in the middle of going through a close family death, in which I am gathering pictures, music, writing the Obituary, making the funeral arrangements, contacting family/friends, mourning, etc. This weekend will be looking for a larger suit since mine no longer fits :( I do not have access to the files since my M.2 has the firmwares, which resided on the motherboard and I do not have a way to retrieve it since I am presently using my laptop. Next week looks like it will also be full for me as the funeral nears quickly. I will post once I have my hands on the June firmware file.

Of course this is a long shot, the file on their site could of simply been moved to another folder causing the date change too :) With WGET you get the last modified date in the header of the HTTP transfer, which depending on how the file was moved/copied on their site could of changed.

Last, it is possible also that someone out there who updated their RCA between June and Nov. 2019 may still have a copy of the file. I will be checking this Forum periodically through tapatalk

Oh and thanks again phatboyj for your message about my procedure, unfortunately it was canceled. Apparently it is not life threatening which is good for me at this time...
Let me edit the above statement I am Very glad it was canceled, it allowed me to be with my Loved one who passed.
 
Last edited:
  • Like
Reactions: phatboyj
VorlonFrog said:
I was online for work a few hours last night, and didn't have time to test a different USB/TTY adapter. :(
Click to expand...
My other USB cable was the same type chip, and I tried placing RXD on all three pins that are not ground, at 9600, 19200, and 115200 baud. Nothing. Nada. Zip. Zilch. Zero.

The only other thing I can think of, which I'll start trying now is: Maybe they're waiting for input on the port before outputting anything at all. Knowing Hikvision, it will require a super-secret passphrase of some sort. I really hate this thing isn't as easily hackable as most IoT devices. :rolleyes:

Something else that comes to mind is, what if CN2 (4 pins) is an RS-485 connector, or a USB connector?

Definitely NOT USB. First pin (next to the CN2 marking) is definitely GND.
But the three remaining pins all have 3v3 DC on them.
/me scratches head, ponders more . . .
 
Last edited:
  • Like
Reactions: phatboyj, bob2701 and David L
VorlonFrog said:
My other USB cable was the same type chip, and I tried placing RXD on all three pins that are not ground, at 9600, 19200, and 115200 baud. Nothing. Nada. Zip. Zilch. Zero.

The only other thing I can think of, which I'll start trying now is: Maybe they're waiting for input on the port before outputting anything at all. Knowing Hikvision, it will require a super-secret passphrase of some sort. I really hate this thing isn't as easily hackable as most IoT devices. :rolleyes:

Something else that comes to mind is, what if CN2 (4 pins) is an RS-485 connector, or a USB connector?
Click to expand...
May be in Mandarin too. :secret:
 
Does anyone know the url to get the snapshot jpg on the EZVIZ DB1 with the stock firmware (no onvif support)? Obviously the url http://<IP Address>/onvif/snapshot.jpg does not work in this case.
 
Last edited:
  • Like
Reactions: David L
aralos1999 said:
Does anyone know the url to get the snapshot jpg on the EZVIZ DB1 with the stock firmware (no onvif support)? Obviously the url http://<IP Address>/onvif/snapshot.jpg does not work in this case.
Click to expand...

i don’t think this camera has a still image url. I’ve tried all variations of them without success. Usually it would be:

http://user:pass@ip:port/Streaming/channels/101/picture
 
  • Like
Reactions: David L
Chadsturgill said:
i don’t think this camera has a still image url. I’ve tried all variations of them without success. Usually it would be:

http://user:pass@ip:port/Streaming/channels/101/picture
Click to expand...
Let’s see if I can do this without these dang emojis

“user : pass@ip : port”

no spaces obviously
 
  • Like
Reactions: David L
KlaverBoer said:
You cannot add the Ezviz DB1 camera to your Synology using the normal way. But you must connect to your Synology using SSH.

1) First open a SSH connection to your Synology.
2) Create a new file for example : Ezviz-DB1.conf It should be placed in /var/packages/SurveillanceStation/target/device_pack/camera_support
3) Change the ownership of the file to the same user and group of the other conf files in my case that is SurveillanceStation:SurveillanceStation
4) Edit the Ezviz-DB1.conf file with sudo vi
5) Paste the following lines into the conf file:

[Ezviz*DB1]
api = custom
resolution_h264 = 2048x1536
default_resolution_h264 = 2048x1536
fps_h264_2048x1536 = 5,10,15,20,25,30
fps_h264_1280x720 = 5,10,15,20,25,30
default_fps_h264_2048x1536 = 15
default_image-quality = 5

h264 = rtsp
mpeg4 = rtsp
mjpeg = rtsp
motion = h264,mpeg4,mjpeg

motion_param = sensitivity,threshold
rtsp_keepalive = none
rtsp_protocol = auto,udp,tcp

6) Save and close the file

7) Now go to the Surveillance Station management page
8) Add a new camera. Complete Setup.
9)
Brand: Ezviz
Camera Model: DB1
Port: 554
Username: admin
Password: Activation code of your doorbell
10) Next
11) In the next screen (Video) i did not change anything
12) In the Recording settings. You can change what suits you
13) In the Schedule settings i only use Motion Detection. But Continuous also works fine.
14) Once the camera is added. Now you have to edit the camera
15) In Device Settings go to the Advanced tab
Transport protocol: udp
Streaming Information Source: Streaming
16) Every setting where you can choose the quality i have chosen High Quality.
17) It should work now

When you first add your camera the "live preview" is still not visible but when you click on it you see the live stream. I do see a the small live preview but that was after i exported the config. Made some changes to the stream paths and imported the camera config again.

I hope it is clear enough.
Click to expand...

Hi KlaverBoer,

I just wanted to send you a big THANK YOU, these instructions were very clear, and helped me to finally get my DB1 up and running.
Cheers,
Wade
 
  • Like
Reactions: KlaverBoer and David L
I am installing my doorbell and we are doing rough height location for camera placement.

We thinking camera len about 49 inches from the floor look right for us.

We are curious how many inches is your camera len from the floor? Not the doorbell button or motion sensor. just the len
 
  • Like
Reactions: David L
You must log in or register to reply here.
Top Bottom