New RCA HSDB2A 3MP Doorbell IP Camera

[alexdelprete]

This is definitely an RCA camera - received in full RCA packaging, and it's an RCA faceplate (oval camera lens rather than circular like ezviz). The auto-recovery routine is checking for ezviz.dav though. When bootloader is interrupted via CTRL+U, the update command looks for digicap.dav.

It may have been possible to recover this doorbell by placing a firmware file named ezviz.dav on the sdcard and possibly doing some press of the reset button that causes it to wipe the config (if there is a reset button sequence that can make it wipe the config - I don't think we really know that).

Do note that I first flashed the firmware using update, and the doorbell was still bricked at that point, because writing firmware doesn't dump the config (see screenshot below). The info I had from previous owner is that he was changing wireless network config when it bricked. Something was definitely messed up in the config. But hey that's how I got it for 50 bucks shipped and started on this science project....

Only once I issued the format command (which erases everything but bootloader) followed by the update command did it unbrick.

It makes sense that updating firmware doesn't drop the config - this is how the DB stays setup for your network, phone app account, etc. through firmware changes.

This is from page 23 of the Putty log file on my previous post - when I did format followed by update. Notice the format command wipes the config area, while the firmware update doesn't touch it.

It would be great to have that log while pressing the physical reset button on the camera, to see if it resets the whole config like the format command or not. I think it doesn't. But probably there's a procedure to do it that is undocumented.

 

[David L]

It would be great to have that log while pressing the physical reset button on the camera, to see if it resets the whole config like the format command or not. I think it doesn't. But probably there's a procedure to do it that is undocumented.

View attachment 74724

Yeah, maybe a series of buttons, like hold Reset and Door Bell Button at the same time then apply power, etc.

 

[alexdelprete]

Seriously I think if someone has a dead vdb I would suggest taking a blank se card and putting 2 copies of firmware on it ezviz and digital that sdcatd will most likely recover 90% of dead vdb

But there has to be an undocumented procedure to hard-reset it (like issuing the format command) and then pickup the firmware through the file on the sdcard. We need to find it. It's a matter of trying different procedures. I don't know if ezviz supports will tell us what it is.

We know that there are different kind of resets/wipe config for these VDB. We should find the one that resets the complete config, like that format command does via uboot command.

 

[alexdelprete]

Yeah, maybe a series of buttons, like hold Reset and Door Bell Button at the same time then apply power, etc.

I'm sure there is. The problem is finding it.

It would unbrick all those zombie VDBs.

 

[alexdelprete]

I'm sure there is. The problem is finding it.

It would unbrick all those zombie VDBs.

In Batchconfig there are 2 different kind of wipes: PARTIAL and COMPLETE. Wonder what they do EXACTLY, looking at the logs.

 

[davidew98]

This is definitely an RCA camera - received in full RCA packaging, and it's an RCA faceplate (oval camera lens rather than circular like ezviz). The auto-recovery routine is checking for ezviz.dav though. When bootloader is interrupted via CTRL+U, the update command looks for digicap.dav.

It may have been possible to recover this doorbell by placing a firmware file named ezviz.dav on the sdcard and possibly doing some press of the reset button that causes it to wipe the config (if there is a reset button sequence that can make it wipe the config - I don't think we really know that).

Do note that I first flashed the firmware using update, and the doorbell was still bricked at that point, because writing firmware doesn't dump the config (see screenshot below). The info I had from previous owner is that he was changing wireless network config when it bricked. Something was definitely messed up in the config. But hey that's how I got it for 50 bucks shipped and started on this science project....

Only once I issued the format command (which erases everything but bootloader) followed by the update command did it unbrick.

It makes sense that updating firmware doesn't drop the config - this is how the DB stays setup for your network, phone app account, etc. through firmware changes.

This is from page 23 of the Putty log file on my previous post - when I did format followed by update. Notice the format command wipes the config area, while the firmware update doesn't touch it. View attachment 74705

Wow now your making me interested even more. Looks like this dav file could actually be some compressed file like a tar maybe. This is good stuff.

 

[davidew98]

In Batchconfig there are 2 different kind of wipes: PARTIAL and COMPLETE. Wonder what they do EXACTLY, looking at the logs.

View attachment 74726


View attachment 74728View attachment 74727

As to not brick beyond our current knowledge I highly suggest he puts the rca firmware on his rca vdb then watch serial as he does a partial reset as well as a full reset to see what both erase if anything.

 

[KC8DKT]

This is definitely an RCA camera - received in full RCA packaging, and it's an RCA faceplate (oval camera lens rather than circular like ezviz). The auto-recovery routine is checking for ezviz.dav though. When bootloader is interrupted via CTRL+U, the update command looks for digicap.dav.

It may have been possible to recover this doorbell by placing a firmware file named ezviz.dav on the sdcard and possibly doing some press of the reset button that causes it to wipe the config (if there is a reset button sequence that can make it wipe the config - I don't think we really know that).

Do note that I first flashed the firmware using update, and the doorbell was still bricked at that point, because writing firmware doesn't dump the config (see screenshot below). The info I had from previous owner is that he was changing wireless network config when it bricked. Something was definitely messed up in the config. But hey that's how I got it for 50 bucks shipped and started on this science project....

Only once I issued the format command (which erases everything but bootloader) followed by the update command did it unbrick.

It makes sense that updating firmware doesn't drop the config - this is how the DB stays setup for your network, phone app account, etc. through firmware changes.

This is from page 23 of the Putty log file on my previous post - when I did format followed by update. Notice the format command wipes the config area, while the firmware update doesn't touch it. View attachment 74705

Its easy to tell if its the RCA branded VDB or not, Its the only one (that I know of) with the slotted video cam mount instead of the normal round mount at the top.

 

[tbh]

I figured it was time to replace the old foscam above the front door with an EZVIZ so I went to Amazon, and EZVIZ store there, and ordered one. Said one day delivery. That was 3 days ago. Called Amazon and the doorbell is removed from there store and I was told I wont be getting the order now. Is this the end of that doorbells selling life now? I hope not. There was a link to some 3rd party sellers off the no longer available EZVIZ listing but I really don't want to pay 130 bucks for one when it was down to 79 from EZVIZ.

 

[rayt]

so i just realized with my laview doorbell. my mechanical chime works. but i no longer get alerted on my app when someone rings my doorbell... LOL, can't win!

 

[David L]

so i just realized with my laview doorbell. my mechanical chime works. but i no longer get alerted on my app when someone rings my doorbell... LOL, can't win!

So just tried mine, it works. What I can tell you there have been times it doesn't, not sure if it is a cloud thing or not. Check in next week...

 

[David L]

I figured it was time to replace the old foscam above the front door with an EZVIZ so I went to Amazon, and EZVIZ store there, and ordered one. Said one day delivery. That was 3 days ago. Called Amazon and the doorbell is removed from there store and I was told I wont be getting the order now. Is this the end of that doorbells selling life now? I hope not. There was a link to some 3rd party sellers off the no longer available EZVIZ listing but I really don't want to pay 130 bucks for one when it was down to 79 from EZVIZ.

For some reason I figure this might be coming, a few months back LaView stopped selling it too. Think Nelly's still sells it but I can't say they have ever dropped their price. I bought the LaView last July for $140, and Love It. Only a few hiccups, cloud issues I believe, other than that pretty rock solid. Though lately several here have been having Chime issues...I think mainly the EZVIZ Dbs though...What about eBay?

So buying from marketplace you should still have warranty, though I have read here EZVIZ giving some people trouble with this. Hikvision is another option. If you are after Google/Alexa support, stay with EZVIZ.

https://www.amazon.com/DS-HD1-Hikvision-Original-Megapixel-Doorbell/dp/B0837BTDT2/ref=pd_di_sccai_2/140-6105076-9957826?_encoding=UTF8&pd_rd_i=B0837BTDT2&pd_rd_r=3dc33341-94c2-49a5-a555-bdcdb1dc83a3&pd_rd_w=g21Az&pd_rd_wg=r0wCU&pf_rd_p=5415687b-2c9d-46da-88a4-bbcfe8e07f3c&pf_rd_r=CJEM3KG23QB19DA05WQ2&psc=1&refRID=CJEM3KG23QB19DA05WQ2

 

[ipa4me2]

I figured it was time to replace the old foscam above the front door with an EZVIZ so I went to Amazon, and EZVIZ store there, and ordered one. Said one day delivery. That was 3 days ago. Called Amazon and the doorbell is removed from there store and I was told I wont be getting the order now. Is this the end of that doorbells selling life now? I hope not. There was a link to some 3rd party sellers off the no longer available EZVIZ listing but I really don't want to pay 130 bucks for one when it was down to 79 from EZVIZ.

The ezvizlife.com site has their Black Friday sale going on right now. The DB1 is $80 and the new DB1C (without PIR) is $70.

 

[pcdoctor]

I have an EZVIZ DB1. I loaded the Hikvision firmware Build 200321 with ONVIF Support using Batch Configuration v3.0.2.6 and then reset the config of the cam and set it up again. Unfortunately I'm unable to enable ONVIF in Batch Configuration. I also tried the Laview and Nelly's firmware with ONVIF support but none of them allowed me to enable ONVIF in Batch Configuration. Any suggestions? Anyone else with an EZVIZ DB1 been able to enable ONVIF on it?

 

[David L]

I have an EZVIZ DB1. I loaded the Hikvision firmware Build 200321 with ONVIF Support using Batch Configuration v3.0.2.6 and then reset the config of the cam and set it up again. Unfortunately I'm unable to enable ONVIF in Batch Configuration. I also tried the Laview and Nelly's firmware with ONVIF support but none of them allowed me to enable ONVIF in Batch Configuration. Any suggestions? Anyone else with an EZVIZ DB1 been able to enable ONVIF on it?

There is no Enable opition, it is available (Already Enabled) in the firmware. What are you trying ONVIF on? NVR, Blue Iris, etc.?

Sent from my SM-G930P using Tapatalk

 

[pcdoctor]

There is no Enable opition, it is available (Already Enabled) in the firmware. What are you trying ONVIF on? NVR, Blue Iris, etc.?

Sent from my SM-G930P using Tapatalk

I just got it figured out. I got hung up on trying to enable it. I got it working now in Home Assistant. I was able to add it in Surveillance Station but I'm getting a gray screen. Any thoughts?

 

[KC8DKT]

I just got it figured out. I got hung up on trying to enable it. I got it working now in Home Assistant. I was able to add it in Surveillance Station but I'm getting a gray screen. Any thoughts?

What firmware did you end up with on your VDB, did you end up taking it back to the Hikvision FW?

What build of Serveillance Station are you running and what are you running in on? (NAS, Stand Alone PC, some kind of NVR)

 

[Tehkor]

FIrst off thanks to this forum and its users as the information helped me choose my doorbell. The amount of information in this thread is daunting. I went with a Hikvision DS-HD1 and the installation went smoothly. The question I have to the knowledgeable users is: Are you okay with running Hik-Connect on your phone ? Is it a security issue ? I am currently using DS Cam app but it doesn't have 2-way audio available so that is the only reason I would like to go back to Hik-Connect as it lets you have a conversation through your phone with the person at the door.

 

[DeMichell]

Hi,

Im a long time lurker on this post, eagerly waiting to see someone pop up with a solution to intercept the doorbell push in openhab.
Then i can use my google home speakers to play a sound when the doorbell has been pressed.
I just wanted to share my current workaround of doing this.

I have openhab running on a windows server. I installed the DNS services on my server en changed the DNS address on my Ezviz DB1 trough Batch Configuration to point to my DNS server.
I Enabled logging on my DNS server and it writes the log to c:\temp\log.txt I then have a powershell looping trough the log sending a http request to my openhab.
Here is an example of the DNS request that is been made everytime the doorbell is pressed:
12/11/2020 11:01:58 0C04 PACKET 00000231F06CBFF0 UDP Rcv 192.168.1.37 0030 Q [0001 D NOERROR] A (5)alarm(2)eu(2)s3(9)amazonaws(3)com(0)
Here is an example of how to use this trough powershell:

Get-Content -Path C:\temp\log.txt -Tail 3 -Wait | where { $_ -match "alarm" } |
ForEach-Object{
Write-Host "DOORBELL PRESSED"
}

In the example above the everytime a dns request in the log containts the word alarm, powershell will echo Doorbell Pressed.
You can switch this to a http request answering to a virtual switch in openhab. I hope to find a better solution in the future.

 

[KC8DKT]

Hi,

Im a long time lurker on this post, eagerly waiting to see someone pop up with a solution to intercept the doorbell push in openhab.
Then i can use my google home speakers to play a sound when the doorbell has been pressed.
I just wanted to share my current workaround of doing this.

I have openhab running on a windows server. I installed the DNS services on my server en changed the DNS address on my Ezviz DB1 trough Batch Configuration to point to my DNS server.
I Enabled logging on my DNS server and it writes the log to c:\temp\log.txt I then have a powershell looping trough the log sending a http request to my openhab.
Here is an example of the DNS request that is been made everytime the doorbell is pressed:
12/11/2020 11:01:58 0C04 PACKET 00000231F06CBFF0 UDP Rcv 192.168.1.37 0030 Q [0001 D NOERROR] A (5)alarm(2)eu(2)s3(9)amazonaws(3)com(0)
Here is an example of how to use this trough powershell:

Get-Content -Path C:\temp\log.txt -Tail 3 -Wait | where { $_ -match "alarm" } |
ForEach-Object{
Write-Host "DOORBELL PRESSED"
}

In the example above the everytime a dns request in the log containts the word alarm, powershell will echo Doorbell Pressed.
You can switch this to a http request answering to a virtual switch in openhab. I hope to find a better solution in the future.

If this is working for you I think your the first person to detect a button press from the DB out side the phone app. The onvif will pass a remote trigger for the PIR motion but it does NOT pass anything when you press the button or at least no one has posted that they have found it. I think your helping more on this one. Give some time and see if some one else chimes in that may know more.

Thanks for posting your info, best work around I know of to date!