New RCA HSDB2A 3MP Doorbell IP Camera

I don't have a solution other than trying to downgrade firmwares. You can search this Thread for RTSP since I know others had this problem, but it seemed to be awhile back.

I remember my DB would lose AP connections after power outages. Not all the time but I had to power off the DB, turning off the breaker, then power it back on and then all was good. Also had to do this when the SD-Card got full and no longer was recording to it. I would also pull the card and reformat it...

So try a power down and back on. If that does not work, you may want to try a 2 hour or more power down so the battery of the DB is no longer. 24 hour power Off may be better...
Thanks all for looking into this...but guess what. I came across this issue at EZVIZ V5.2.4 build 230404 (DB1) RTSP problem where @cw-kid had the same issue and a "fix". It's ridiculous but it worked :-)!
 
Thanks all for looking into this...but guess what. I came across this issue at EZVIZ V5.2.4 build 230404 (DB1) RTSP problem where @cw-kid had the same issue and a "fix". It's ridiculous but it worked :-)!
Well kinda makes sense, on our Dahua cameras, or any camera, it is a good idea to factory reset and save after upgrading firmware. This is mainly because of new or changed features. You don't always have to do a factory reset since some cameras allow a partial reset to keep your network settings. By @cw-kid resaving the network settings it finished the upgrade. Sorry for not sharing this earlier...
 
  • Like
Reactions: Chen_Arets
I found this thread as i'm sure many did because of the changing firmware to make a doorbell work better, so I have a ezviz DB1 running 240617 , I also have a reolink poe which has replaced it on my front door. I have the DB1 on the walk through door to my garage and would like to set it up with ONVIF so I can get alarms in homeassistant. so i'm wondering if this is even possible anymore, i dont see where i can download the Hikvision 211101 firmware and the only batch configuration software I find is V3.1.3.3 and dont know if this would work, think I read somewhere of a certain version to use. anyway if someone can stear me right I would appreciate it
 
  • Like
Reactions: David L
So I apologize, I never installed Hikvision firmware on my LaView (DB1 variant) since the firmware on the LaView supported ONVIF already. But I did collect the firmwares of the different variant brands. Hikvision 200321 was the last one I collected, I upped the 211101 you requested but also 200321 Don't hold me too it, but thinking several here used 200321

As far as the Batch Config Tool, I used v3.0.2.6 with good success, it is very old but worked for me, last time used was a little over a year ago before I switched to ReoLink DB.
Still even have it installed on an older PC, so below is the build#
1737936823182.png


HTH
 

Attachments

Thanks David L, I use Linux computers and didn't have a windows computer setup to run the batch config tool so after many attempts to load win 10 on an old laptop with a failing hard drive (apparently) I figured it out and got it installed. I was able to get to SYSTEM->SYSTEM MAINTENANCE->Remote Upgrade as per alexdelprete step by step instructions. However when i tried the remote upgrade it didn't seem to work, then after that I couldn't even get my DB1 to show up in the top of the BC window, I struggled with this for 2 days with error messages that it couldn't connect to the camera, yet RTSP obviously still worked and connected because I was still seeing the feed both in the EZVIZ app and in Zoneminder. anyway I finally cut the power to the DB1 and now can connect to it with batch config, but every time I try the remote upgrade I almost immediately get a red "upgrading failed " message in the lower right corner of the BC window. I am currently skimming through this thread to see if anyone else has had a similar problem.
 
  • Like
Reactions: David L
Thanks David L, I use Linux computers and didn't have a windows computer setup to run the batch config tool so after many attempts to load win 10 on an old laptop with a failing hard drive (apparently) I figured it out and got it installed. I was able to get to SYSTEM->SYSTEM MAINTENANCE->Remote Upgrade as per alexdelprete step by step instructions. However when i tried the remote upgrade it didn't seem to work, then after that I couldn't even get my DB1 to show up in the top of the BC window, I struggled with this for 2 days with error messages that it couldn't connect to the camera, yet RTSP obviously still worked and connected because I was still seeing the feed both in the EZVIZ app and in Zoneminder. anyway I finally cut the power to the DB1 and now can connect to it with batch config, but every time I try the remote upgrade I almost immediately get a red "upgrading failed " message in the lower right corner of the BC window. I am currently skimming through this thread to see if anyone else has had a similar problem.
There is a way to put the firmware on the sd-card and upgrade from it. I have not tried it but some others here have...just FYI
 
So today I was also able to get my chime working, my steps were similar but slightly different, so posting here for completeness...

Hardware: Hik-Vision DS-HD1
Prior Firmware: Hikvision 200321
Previously configured via BCT only and placed on restrictive IOT VLAN.
Was unable to configure via any phone app, and in addition to the chime, no DNS calls etc were being made on doorbell press.

Step 1: Uploaded EZVIZ firmware 200220
Step 2: Hard Reset, to include removal of power, holding in reset button while re-applied (resets admin PWD as well)
Step 3: Added temporary firewall rule to IOT VLAN to allow all outbound connections
[At this point, attempted to add device using an iPhone SE-2 running iOS 14.2 and the EZ-Viz app and Hik-Connect app... all failed at the "Connect to device wifi" step, even when I manually joined to network]​
Step 4: Using an iPad Mini running iPad OS 13.4.1, ran setup successfully at least partway.
[This reached the "Device Setup" stage, and then it would not progress past a "Light Linkage" page, as when I pressed save it would merely go back to the previous page... but at the previous page I could get the device QR code]​
Step 5: Switching to the iPhone, finished adding the device using the QR Code from the iPad.
Step 6: Under "Device Settings" was able to select the chime type and set to mechanical (was set to "No Chime). Viola... at this point the doorbell is working, and also is sending notifications back to the app
Step 7: Connected via BCT and saved configuration file
Step 8: Took full packet capture of bootup and chime press, saw DNS call to alarm.use.s3.amazonaws.com as others have reported, followed by a port 443 connection.
[Confirmed ONVIF unavailable as expected, also noted inability to change admin password or add additional users from BCT]​
Step 9: Updated to firmware 200321 from within the EZVIZ app [Note that this is EZVIZ 200321, not Hikvision 200321 as there is an EZVIZ logo superimposed on the ONVIF video stream]
Step 10: Added "viewer" user using BCT, confirmed ability to now connect via ONVIF, and adjust motion detection zones. Note that the secondary video stream must have it's resolution set to CIF before the main stream can be edited as the 200220 firmware used resolution not supported under 200321 apparently and so you'll get an error when you try to save.
Step 11: Confirmed chime still working, and that EZVIZ app still showed the option to set mechanical/electronic/none.
[Note somewhere in here my viewer account permissions disappeared and so my NVR was suddenly unable to start recording... but since it was a valid user/pass, the "test" feature still reported success... this took longer to figure out than it should have... but adding the permissions in again via BCT worked fine an all is well again on the ONVIF front]​
Step 12: Add firewall rule blocking all outbound traffic except port 443 to the applicable amazon regions
Step 13: Changed encryption password in EZVIZ app.
Step 14: Saved Config File.

So now I have a working chime, working ONVIF recording on the local LAN with camera-driven motion detection zones for event recording, and doorbell presses cause notifications in the phone and I can tap a button or two and see the doorbell video/audio. The only thing that won't work is the ability to see video after button presses when my phone is not on the local LAN, but that's my preference. Also all the "dial home" packets are being blocked as confirmed by the firewall.

I can definitely redirect the cam's port 443 traffic to a local IP using (outbound) port forwarding, which would then make local notifications outside the EZVIZ app environment easier, but then the app notifications break. I did see in the packet capture a reference to MQTT, so I would suspect that's the protocol in use for the doorbell.
Hi, misally. I've been running an ezviz branded DB1C on firmware ezviz build 220802 which has no ONVIF, just RTSP, and so, no motion detection recordings on my NVR. I'd like to downgrade to the ONVIF-enabled firmware you have, 200321, but don't know A) from where to get it and B) how to load it. Any guidance would be appreciated. Thanks.
 
  • Like
Reactions: David L
  • Like
Reactions: David L
Have you checked the "101". It has a TON of info:
Thanks. It seems my DB1C is NOT compatible with firmwares for the legacy DB1. Looks like it will never have ONVIF. Hoping someone can prove me wrong about that.
 
Thanks. It seems my DB1C is NOT compatible with firmwares for the legacy DB1. Looks like it will never have ONVIF. Hoping someone can prove me wrong about that.
I think you are right, I have not seen a firmware with ONVIF support for the DB1C either...

But even though my DB1 variant (LaView) had ONVIF firmware, I chose to use Blue Iris with it's motion and trigger/tripwire detection. It would be an option for you too. Later I incorporated Home Assistant for notifications, but you can get notifications through Blue Iris as well.
 
I think you are right, I have not seen a firmware with ONVIF support for the DB1C either...

But even though my DB1 variant (LaView) had ONVIF firmware, I chose to use Blue Iris with it's motion and trigger/tripwire detection. It would be an option for you too. Later I incorporated Home Assistant for notifications, but you can get notifications through Blue Iris as well.
Yeah, BlueIris is easy. I was hoping to get ONVIF working so I'd have motion detection working for this cam on my Dahua NVR. Presently, it records the RTSP stream constantly and nearby cameras' motion detection trigger motion recording on this one. That's the best I can do with this setup, I think.
 
  • Like
Reactions: David L