New RCA HSDB2A 3MP Doorbell IP Camera

I have the doorbell registered in the bottom section of batch configuration.
Hi pete_c. Thank-you for explaining. So I infer from your elaboration that you are managing user additions from the "bottom" section of batch config. For further clarity I enclose photos of my Batch Config Tool showing what my understanding of your explanation is.

Clearly, I am a hapless n3wb because, for the life of me, I cannot determine how to add a user when my camera device is registered ONLY in the "bottom section". :)
 

Attachments

  • Sections of Batch Confirg Tool showing TRUE build number.png
    Sections of Batch Confirg Tool showing TRUE build number.png
    114 KB · Views: 0
  • Bottom registered.png
    Bottom registered.png
    95.5 KB · Views: 0
  • Like
Reactions: David L
Hi pete_c. Thank-you for explaining. So I infer from your elaboration that you are managing user additions from the "bottom" section of batch config. For further clarity I enclose photos of my Batch Config Tool showing what my understanding of your explanation is.

Clearly, I am a hapless n3wb because, for the life of me, I cannot determine how to add a user when my camera device is registered ONLY in the "bottom section". :)
I remember having to hit refresh a few times before both sections would show the Doorbell...
 
  • Like
Reactions: MikeFromCanmore
So I infer from your elaboration that you are managing user additions from the "bottom" section of batch config. For further clarity I enclose photos of my Batch Config Tool showing what my understanding of your explanation is.

So the user adds are from the top section.

I just registered the doorbell on the bottom section. Didn't do anything else with it.

The users and passwords remained when the doorbell would reset. Well everything remained in placed except for the switch over to AP mode.
 
So I infer from your elaboration that you are managing user additions from the "bottom" section of batch config. For further clarity I enclose photos of my Batch Config Tool showing what my understanding of your explanation is.

So the user adds are from the top section.

I just registered the doorbell on the bottom section. Didn't do anything else with it.

The users and passwords remained when the doorbell would reset. Well everything remained in placed except for the switch over to AP mode.
Thank-you pete_c. I experienced the same. Settings survive a reboot and even reversion to AD_HOC mode. i.e. today it suddenly switched SSID to sofap_Exxxxxxx and waited for me to go through the config process.
1) Connect to Ad-Hoc SSID softap_Exxxxxx and use batch config to change SSID to EZVIZ_Exxxxxxxxx
2) Change the WiFi password to EZVIZ_PASSWORD
3) Use the app to connect Ad-Hoc and go through the install process in the app.

I also tried to shortcut this by setting my SSID and Password to the desired final state and changing Working Mode from Ad-Hoc to Manage all in steps 1) and 2). But that did not seem to work as expected.

Once a DB1 has been set up once, do you know of a way to go directly from softap_Exxxxxx Ad-Hoc to the final WiFi SSID connection and also resulting in DB1 registered with the app, skipping the intermediate app-based install steps?

Thank-you.
 

Attachments

  • Shortcut Setup WiFi Ad-Hoc to Manage.png
    Shortcut Setup WiFi Ad-Hoc to Manage.png
    79.4 KB · Views: 0
  • Like
Reactions: David L
There is a referral to an article here in the forum posts above as to why the DB goes to AP mode. For me it was too many calls to the DB to my touchscreens.

Now using a proxy and do not get any resets.

I saved the password here and IP under batch configuration as it is always the same to reconfigure it back to regular wifi mode.

1) Connect to Ad-Hoc SSID softap_Exxxxxx and use batch config to change SSID to EZVIZ_Exxxxxxxxx
2) Change the WiFi password to EZVIZ_PASSWORD
3) Use batch config to connect Ad-Hoc and you are done.

It saves everything else.
 
There is a referral to an article here in the forum posts above as to why the DB goes to AP mode. For me it was too many calls to the DB to my touchscreens.

Now using a proxy and do not get any resets.

I saved the password here and IP under batch configuration as it is always the same to reconfigure it back to regular wifi mode.

1) Connect to Ad-Hoc SSID softap_Exxxxxx and use batch config to change SSID to EZVIZ_Exxxxxxxxx
2) Change the WiFi password to EZVIZ_PASSWORD
3) Use batch config to connect Ad-Hoc and you are done.

It saves everything else.
Hi pete_c. Wow, that is a lot of very helpful info! I have a few questions:

1) I found a post you made describing how to bypass the phone based config app after the DB1 reverts to AP Mode here where you say "You can log in and configure the DB to your liking totally bypassing the smartphone app." This is precisely what I want to do! I have tried following the steps 1) thru 3) you enumerate above, as shown in the screen shot I posted here, but cannot get it to work. The part I am struggling with is "and you are done" after your step 3) above.

What I tried: After connecting to softap_Exxxxx AP with a laptop running batch config tool, I tried to change the DB1 from AP Mode to Client mode by using Batch Config Tool to change the "Working Mode" setting from "Ad-Hoc" to "Manage" and entering the SSID and password credentials for the AP that I want the DB1 to client connect on (with the expectation that would change the DB1 from AP mode to Client mode) as shown in the screen shot linked above.

What actually appears to happen is that the DB1 reverts to AP mode with SSID = softap_Exxxxxxx. Is there some menu setting I need to change other than "Working mode" n order to turn off AP Mode and have the DB1 connect to the camera client network?

2) I cannot find the referral to article you mention above as to why the DB1 goes to AP mode. All I could find was a thread that mentioned Ad-Hoc here. Can you find the URL for the article you mention above explaining why DB1 spontaneously goes to AP mode?

3) Can you please explain your proxy configuration with the DB1? I would like to try that as a solution to the DB1 spontaneous reverting to AP Mode with SSID softap_Exxxxxx

Thanks for all your help and contributions to this forum pete_c, greatly appreciated.
 
  • Like
Reactions: David L
So set the SSID and password to your home WAP initially using DHCP. Also change the admin password and create a new user. Rebooting it will connect to your home WAP.

Here used a Lenova Tiny running WIndows 2016 server. It has a WLAN card and it is connected to the LAN via Ethernet port.

I do not know why it goes in to AP mode other than I was connecting the display to a few touchscreens.

The other FAQ was posted on an autonomous link and referred to in this thread. I do not recall when or by whom.
 
So set the SSID and password to your home WAP initially using DHCP. Also change the admin password and create a new user. Rebooting it will connect to your home WAP.
Hi pete_c.

That worked! Here is exactly what I did:
  1. Reset the DB1 to factory defaults using batch config using Batch Config 3.0.2.6
  2. Changed the SSID, Password, WPA2-PSK, and Working Mode from 'Ad-Hoc' to 'Manage' using Batch Config 3.0.2.6
  3. Rebooted using Batch Config using Batch Config 3.0.2.6
As documented in the attached screen shots. It looks like I was missing step 3 before. Thanks so much for all your patience and help!

Kind regards,

MikeFromCanmore

P.S. Regarding the article dealing with possible causes of EZVIZ DB1 spontaneous reversion to AP mode, I used this search string in Google. I found some great instructions and insight from yourself, but I could not locate the aforementioned article. "site:New RCA HSDB2A 3MP Doorbell IP Camera AP Mode"
 

Attachments

  • Restore Factory Default Settings.png
    Restore Factory Default Settings.png
    125.9 KB · Views: 0
  • Saving Change Credentials and Working Mode.png
    Saving Change Credentials and Working Mode.png
    180 KB · Views: 0
  • Reboot from Batch Config.png
    Reboot from Batch Config.png
    129.3 KB · Views: 0
  • Like
Reactions: David L
P.S. Regarding the article dealing with possible causes of EZVIZ DB1 spontaneous reversion to AP mode, I used this search string in Google. I found some great instructions and insight from yourself, but I could not locate the aforementioned article. "site:New RCA HSDB2A 3MP Doorbell IP Camera AP Mode"
Here is Google AI's wisdom on the question "EZVIZ db1 changes back to AP Mode periodically". Not super helpful for me because I have a very strong WiFi connection:

An EZVIZ db1 changing back to AP mode periodically is usually caused by network configuration issues or a weak Wi-Fi signal. To resolve this, ensure the camera is within a strong Wi-Fi range, the router is functioning correctly, and the app is not blocked by antivirus software or battery optimization settings.

Here's a more detailed breakdown of potential causes and solutions:
1. Weak Wi-Fi Signal or Interference:
  • Solution: Move the camera closer to the router, minimizing obstacles like walls or appliances that can interfere with the signal.

  • Solution: Ensure the router is functioning correctly and try rebooting it if necessary.

  • Solution: Consider changing the Wi-Fi channel to a less crowded one on your router.
2. Router Issues:
  • Solution: Verify the router's 2.4 GHz network mode is enabled, as some EZVIZ cameras only support this frequency.
  • Solution: Ensure the router can distribute IP addresses or disable static IP settings.
  • Solution: Check if any firewalls or other network restrictions are in place.
3. App Settings and Device Configuration:
  • Solution:
    Ensure the EZVIZ app is not blocked by antivirus software on your phone.

  • Solution:
    For iOS 15 and above, check if Do Not Disturb or Focus mode is enabled, and disable it.

  • Solution:
    For Android, check if battery optimization is turned off for the EZVIZ app.

  • Solution:
    Reset the camera by holding the reset button for a few seconds and reconfigure it using the EZVIZ app.

  • Solution:
    When configuring the network, ensure the camera is close to the router (within 1.5 meters).
4. Other Troubleshooting Steps:
  • Solution: Try connecting to the camera's AP manually via your phone's Wi-Fi settings, using the "EZVIZ_SN" as the network name and the six-digit verification code as the password.
  • Solution: If the issue persists, contact EZVIZ support for further assistance.
 
  • Like
Reactions: David L
Great news.

Interesting I have been using Google AI too here. Most of it though is from here on the forum.

Thinking my spontaneous change to AP mode was due to taxing the CPU on the Video Doorbell. I use Ruckus AP's here and have three where as I only really need one.

What was happening was that I was using the Touchscreen interface to my OmniPro alarm interface and Homeseer (15 touchscreens) and Home Assistant.

The article / FAQ was not MFG specific. Just relating to the Hikvision DB (and EZViz and Nelly et al). It mentioned possible number of sessions relating to stability and that number was 3.

I did leave the AP mode configuration saved in Batch Configuration.

Not sure if you are using Kodi. I built a couple of strm files for the Doorbell and they work fine with Kodi.
 
Great news.

Interesting I have been using Google AI too here. Most of it though is from here on the forum.

Thinking my spontaneous change to AP mode was due to taxing the CPU on the Video Doorbell. I use Ruckus AP's here and have three where as I only really need one.

What was happening was that I was using the Touchscreen interface to my OmniPro alarm interface and Homeseer (15 touchscreens) and Home Assistant.

The article / FAQ was not MFG specific. Just relating to the Hikvision DB (and EZViz and Nelly et al). It mentioned possible number of sessions relating to stability and that number was 3.

I did leave the AP mode configuration saved in Batch Configuration.

Not sure if you are using Kodi. I built a couple of strm files for the Doorbell and they work fine with Kodi.
Hi pete_c, good explanation. That would account for the crash wiping the config despite good WiFi. I do know that each RTSP request launches a separate stream so perhaps if I inadvertently leave my phone app on, and my ONVIF viewer, and my NVR all at the same time that might be a sufficiently heavy load to swamp the CPU. I also tried a restore from a Batch Config save-file and that actually works very smoothly, so I think rolling forward I will do that. It is a one button fix. Also, I set up a laptop on my network to have two NICs one WiFi and one wired Ethernet. Today I tried VPN into that Laptop over the Interwebs and then connecting to softap_Exxxxxx and forcing the DB1 back to client mode. Worked perfectly. So if all of us are away, and the DB1 reverts to AP-Mode, I can remotely restore it.

For me, the trick to get the Laptop to connect to both networks was a setting in the BIOS that automatically disabled Wi-Fi whenever an ethernet cable was plugged in. I just turnd that 'feature' off. That, and disabling VLAN and Prioritization on the Ethernet NIC driver, Yahoo!
 

Attachments

  • priority-vlan-disabled.png
    priority-vlan-disabled.png
    155.3 KB · Views: 0
  • Like
Reactions: pete_c and David L
On the Lenova Tiny with Windows 2016 I leave the WLAN off and only turn it on when needed.
 
My EZVIZ DB1 occasionally stops responding to button presses and needs to be power cycled to restore proper functionality. I have mechanical chimes. Normally it works no problem. Chimes ring, phone app activates, just like they should. But eventually the doorbell button just does nothing. Not even the audio from the doorbell itself plays. I can't figure out why and I'm considering replacing it. Unless of course anyone here has heard of, and knows a solution to, this problem.

If not, does anyone know of another doorbell cam with the same FOV as this one? I don't mind the fisheye. Seeing the entire area in front of the door is important to me, and I don't want a dual camera doorbell. I've been very pleased with the view from this one and would be disappointed in anything less. From what I'm seeing, most newer doorbells seem to have lower FOV.
 
Last edited:
  • Like
Reactions: David L
My EZVIZ DB1 occasionally stops responding to button presses and needs to be power cycled to restore proper functionality. I have mechanical chimes. Normally it works no problem. Chimes ring, phone app activates, just like they should. But eventually the doorbell button just does nothing. Not even the audio from the doorbell itself plays. I can't figure out why and I'm considering replacing it. Unless of course anyone here has heard of, and knows a solution to, this problem.

If not, does anyone know of another doorbell cam with the same FOV as this one? I don't mind the fisheye. Seeing the entire area in front of the door is important to me, and I don't want a dual camera doorbell. I've been very pleased with the view from this one and would be disappointed in anything less. From what I'm seeing, most newer doorbells seem to have lower FOV.
What size transformer do you have?
 
  • Like
Reactions: MikeFromCanmore
You are good there...sorry I have to ask...

I really don't have much to add to help your problem. How old is your DB1? Seeing those with 3 years or more having to replace the internal battery...

As far as a replacement, ReoLink does not have the 180 degree view the Hik (yours) has but they do have a fisheye view which is wide and a newer model which is narrow...

This is the first version DB that I have...fisheye but wide...

1753920809656.png
 
As an Amazon Associate IPCamTalk earns from qualifying purchases.
Thank you for your input!

Asking about the transformer makes total sense. No apology necessary.

Looks like mine is just over 3 years old. However, this problem has been going on for a long time. Probably since the beginning. I had the RCA version prior (bird destroyed it), and I don't recall it happening with that one.

Yeah, what your screenshot shows would disappoint me. Had I never owned the EZVIZ/RCA I'm sure it would've been fine to me.

I wish these were still made. I'd try another one. And I really wish someone else made a 180 FOV doorbell. :-(
 
  • Like
Reactions: David L
Thank you for your input!

Asking about the transformer makes total sense. No apology necessary.

Looks like mine is just over 3 years old. However, this problem has been going on for a long time. Probably since the beginning. I had the RCA version prior (bird destroyed it), and I don't recall it happening with that one.

Yeah, what your screenshot shows would disappoint me. Had I never owned the EZVIZ/RCA I'm sure it would've been fine to me.

I wish these were still made. I'd try another one. And I really wish someone else made a 180 FOV doorbell. :-(
I have the one on the right, you could always try the one on the Left and send it back if it don't work for you:
1753959531574.png

 
  • Like
Reactions: TonyR
Yep^^^^.

Decide which aspect ratio you want: taller than wide for better package view (White) or wider than tall (Black) to cover more of the porch width. That will determine which color you order.

Reolink Video Doorbell PoE
Black: H: 135° V: 100°. D: 180°
White: H: 100°. V: 135° D: 180°

Reolink Video Doorbell WiFi
Black: H: 135° V: 100°. D: 180°
White: H: 100°. V: 135° D: 180°
 
  • Love
Reactions: David L