alexdelprete
Getting comfortable
Tell your wife that now I'm not surprised about the good choice of colors and style. The white door is beautiful.
New RCA HSDB2A 3MP Doorbell IP Camera
- Thread starter fleece
- Start date
Tell your wife that now I'm not surprised about the good choice of colors and style. The white door is beautiful.
Welcome to the IPCAMTalk forum @digbybare
Relating to external sound (questions 1 & 2) look on your Hikvision cloud application (Smart phone app) for the options and volume controls). This is the first time I have heard from a user about an external sound from the doorbell based on the motion detector.
Check to make sure that the plastic film is removed from the camera lens. Here left the plastic film on the doorbell button.
For adjustments here utilize Hikvision's Batch Configuration program rather than iVMS. Under image there is a setting for the primary (2048X1536) and the secondary stream. There is a night day switch there under CCD / DayNight switch parameters.
Check out post #101.
Relating to external sound (questions 1 & 2) look on your Hikvision cloud application (Smart phone app) for the options and volume controls). This is the first time I have heard from a user about an external sound from the doorbell based on the motion detector.
Check to make sure that the plastic film is removed from the camera lens. Here left the plastic film on the doorbell button.
For adjustments here utilize Hikvision's Batch Configuration program rather than iVMS. Under image there is a setting for the primary (2048X1536) and the secondary stream. There is a night day switch there under CCD / DayNight switch parameters.
Check out post #101.
I just tried doing the upgrade/reset as suggestd by @alexdelprete and this post
I successfully installed the newest Hik firmware. I can tell as the firmware now shows up as Firmware version V5.2.4 build 200321
I proceeded to step two Use Batch Config (from main screen) to Reset the config of the cam (check this screenshot)
I attempt to do this by going to System Configuration > Restore > And select the "complete restoration" box
Unfortunately after I do that, and click OK. I'm returned to the main screen and the status box is now Red and says "Configuration Failed"
Safe to say that it didn't do the full reset? It almost immediately drops back from the reset box to the main screen.
Have an RCA came from Mid 2019 (June) that was on EZVIZ FW 190708. and upgraded to the most recent HIK.
Any suggestions?
Also my batch config version looks slightly different (newer?) than that in the screenshot. Not sure if that is making any difference or what the deal is. It's 3.0.3.8 Build 20200318
Last edit/addition.
I see there is an Errors tab at the bottom with 3 errors (from the 3 times i tried to restore)
it states Error Type: Restoring Parameters Failed Details: Not Supported
I successfully installed the newest Hik firmware. I can tell as the firmware now shows up as Firmware version V5.2.4 build 200321
I proceeded to step two Use Batch Config (from main screen) to Reset the config of the cam (check this screenshot)
I attempt to do this by going to System Configuration > Restore > And select the "complete restoration" box
Unfortunately after I do that, and click OK. I'm returned to the main screen and the status box is now Red and says "Configuration Failed"
Safe to say that it didn't do the full reset? It almost immediately drops back from the reset box to the main screen.
Have an RCA came from Mid 2019 (June) that was on EZVIZ FW 190708. and upgraded to the most recent HIK.
Any suggestions?
Also my batch config version looks slightly different (newer?) than that in the screenshot. Not sure if that is making any difference or what the deal is. It's 3.0.3.8 Build 20200318
Last edit/addition.
I see there is an Errors tab at the bottom with 3 errors (from the 3 times i tried to restore)
it states Error Type: Restoring Parameters Failed Details: Not Supported
Attachments
Last edited:
It looks like my 2020 RCA HSDB2 is bricked after installing the 3-30-2020 Hikvision firmware. Just a red circle. Tried resetting and leaving power off overnight. I just received and installed the doorbell over the weekend and hadn't tried any other firmware. It was running RCA's v5.2.4 build 190124.
Welcome to the IPCAMTalk forum @bparrish.
Sorry to hear about your new RCA doorbell camera. Did you notice anything unusual when using the Batch Configuration program to upload the Hikvision Firmware?
You should be able to return the camera if you just purchased it.
Here started with a Nelly camera, updated the Nelly firmware then updated the Nelly firmware to the Hikvision firmware.
Started with EZViz application here and currently not connected to any of the iOS or Android apps in the cloud.
Rather just VPN to home and use a direct connect to the Doorbell camera these days.
Sorry to hear about your new RCA doorbell camera. Did you notice anything unusual when using the Batch Configuration program to upload the Hikvision Firmware?
You should be able to return the camera if you just purchased it.
Here started with a Nelly camera, updated the Nelly firmware then updated the Nelly firmware to the Hikvision firmware.
Started with EZViz application here and currently not connected to any of the iOS or Android apps in the cloud.
Rather just VPN to home and use a direct connect to the Doorbell camera these days.
Last edited:
I haven't been through the process before but looking back at the screenshot on page 101 it looks a little different than where I did it. Here's a screenshot from one of my outdoor Hikvision cams showing the upgrade screen I used:
The progress bar filled up and then that was it. No error messages or anything.
Were you logged in the camera with Admin using the Hikvision batch configuration program?
This is the upgrade screen in Batch Configuration you should see if you are logged in to the camera. It is very important that you are logged in with admin rights.
IE: Once logged in the feature set is different as it tuned to the specific camera.
This is the upgrade screen in Batch Configuration you should see if you are logged in to the camera. It is very important that you are logged in with admin rights.
IE: Once logged in the feature set is different as it tuned to the specific camera.
Yes, using the Batch Configuration 3.0.2.6. Pretty sure it was logged in. I had to add the camera and enter the credentials at that time. In those config screens I was playing with the BLC settings and they were working. And I had turned off the date/time overlay.
The app was connected but it wasn't running on my phone at the time. I was pulling RTSP to Blue Iris though. But I updated through Remote Configuration -> System Maintenance instead of the Upgrade button. Think that could have done it?
Just a guesstimate that maybe the cloud app continuously connected and or RTSP streaming locks some of the upgrading of firmware files.
The app was connected but it wasn't running on my phone at the time.
Once the doorbell is configured to the cloud app it remains connected whether you are using the app or not. There might be something in the app running that restricts the upgrade of firmware only to the vendor cloud stored firmware files. (well RCA firmware files only?)
1 - guessing the download went fine - right? You saw it.
2 - then the firmware unzips files in the camera OS - Maybe at this time it just will not write to running files??
3 - when it reboots then maybe it never completes the firmware installation.
Mentioning this because when I upgraded to the Hikvision firmware I was already not using the cloud app and the doorbell was no longer connected to it and I was not proactively streaming RTSP to my NVR or any application.
BTW one of the first things I did with the original firmware / Nelly camera was test the cloud connection then disconnect from it and not utilize any apps on my phones or tablets. Then I went to editing stuff on the Doorbell camera with the Batch Configuration program. Around this time did upgrade the firmware to a newer Nelly posted firmware with no issues. I even have two user accounts now set up on the camera. Both of the users are admin. If I do a back up here and look at the file there are pieces of my EZViz configuration in the file still which I would like to get rid of. I also see mobile profiles in the ONVIF configuration program but they are ghosted and I cannot change them.
Looking at the bin back up configuration file using a hex editor see some stuff there ezviz links, original ap ssid.
dev.ezviz7.com - 52.5.24.116 Amazon cloud
alarm.ezviz7.com - 34.234.180.196 Amazon cloud
litedev.us.ezvizlife.com - 35.174.95.139 Amazon cloud
See my original to EZViz login.
When I log in to EZViz and try to configure or add the camera application states it is no longer seeing the camera. This might be due to my PFSense Configuration of PFBlocker and other stuff.
Originally using the ONVIF editor did see an NTP link to China with time set to local Chinese time. I changed all of this stuff using the ONVIF editor to make it match what I configured in the Batch Configuration program.
Looking at internal pictures of the camera do see a JTAG port on it. You do not want to do this though.
MAYBE you can write the original RCA DAV bin file to the SD card and hit the reset on the camera to see if it loads the firmware bin file. I mean you have bricked the camera so you are returning it so it doesn't hurt to try this.
The app was connected but it wasn't running on my phone at the time.
Once the doorbell is configured to the cloud app it remains connected whether you are using the app or not. There might be something in the app running that restricts the upgrade of firmware only to the vendor cloud stored firmware files. (well RCA firmware files only?)
1 - guessing the download went fine - right? You saw it.
2 - then the firmware unzips files in the camera OS - Maybe at this time it just will not write to running files??
3 - when it reboots then maybe it never completes the firmware installation.
Mentioning this because when I upgraded to the Hikvision firmware I was already not using the cloud app and the doorbell was no longer connected to it and I was not proactively streaming RTSP to my NVR or any application.
BTW one of the first things I did with the original firmware / Nelly camera was test the cloud connection then disconnect from it and not utilize any apps on my phones or tablets. Then I went to editing stuff on the Doorbell camera with the Batch Configuration program. Around this time did upgrade the firmware to a newer Nelly posted firmware with no issues. I even have two user accounts now set up on the camera. Both of the users are admin. If I do a back up here and look at the file there are pieces of my EZViz configuration in the file still which I would like to get rid of. I also see mobile profiles in the ONVIF configuration program but they are ghosted and I cannot change them.
Looking at the bin back up configuration file using a hex editor see some stuff there ezviz links, original ap ssid.
dev.ezviz7.com - 52.5.24.116 Amazon cloud
alarm.ezviz7.com - 34.234.180.196 Amazon cloud
litedev.us.ezvizlife.com - 35.174.95.139 Amazon cloud
See my original to EZViz login.
When I log in to EZViz and try to configure or add the camera application states it is no longer seeing the camera. This might be due to my PFSense Configuration of PFBlocker and other stuff.
Originally using the ONVIF editor did see an NTP link to China with time set to local Chinese time. I changed all of this stuff using the ONVIF editor to make it match what I configured in the Batch Configuration program.
Looking at internal pictures of the camera do see a JTAG port on it. You do not want to do this though.
MAYBE you can write the original RCA DAV bin file to the SD card and hit the reset on the camera to see if it loads the firmware bin file. I mean you have bricked the camera so you are returning it so it doesn't hurt to try this.
Last edited:
Just an update to my question/issues:
I was finally able to reset my camera, Just not via the main screen > Restore > Complete Restoration. That continually failed.
I was able to open the Remote Configuration, go to the System Maintenance Section, then choose Restore Default Settings. After this my SSID was set back to Softap like expected. Not sure i got the full reset though, as it doesn't specifically say whether or not Restore Default Settings is the same as "complete restoration" I was then able to Reconnect via the softap SSID and start re configuring things.
I wonder if it's a difference between Batch Config versions or what that was throwing the error.
1 - main screen > Restore > Complete Restoration * this did not work
2 - open the Remote Configuration, go to the System Maintenance Section, then choose Restore Default Settings * This worked
Good news.
When you were doing #1 were you logged in the camera? What the camera configuration line ghosted or did it show the programming icon?
2 - open the Remote Configuration, go to the System Maintenance Section, then choose Restore Default Settings * This worked
Good news.
When you were doing #1 were you logged in the camera? What the camera configuration line ghosted or did it show the programming icon?
Replacement is on the way. I could try the SD card update while I wait. Do I put the RCA firmware file as it's named (HSDB2.dav) or do I need to rename it?
I was logged into the camera via Batch Config tool as I had just updated the firmware successfully and was able to verify that the FW version number had changed. And i was closely following PeteC's suggested steps...
I'm not sure i know what you mean when you are asking if the camera configuration line was ghosted or did it show the programming icon
I'm not sure i know what you mean when you are asking if the camera configuration line was ghosted or did it show the programming icon
Well when not logged in to the camera via Batch configuration the line is ghosted and when you are logged in the line and options are there to program the camera.
So you said you were logged in and I do not think the main screen / restore / complete restoration would have worked or attempted to work if you were not logged in.
This all relates to documenting your achievement in post #1010 which is going to also utilize @alexdelprete post # 3750 for the FAX post #101.
Thank you @Fiddelm3742.
Well when not logged in to the camera via Batch configuration the line is ghosted and when you are logged in the line and options are there to program the camera.
So you said you were logged in and I do not think the main screen / restore / complete restoration would have worked or attempted to work if you were not logged in.
This all relates to documenting your achievement in post #1010 which is going to also utilize @alexdelprete post # 3750 for the FAX post #101.
Thank you @Fiddelm3742.
Hi everyone, a couple of quick questions I hope someone can help with (I didn't find these in the 101):
- Has anyone yet found a way to get doorbell presses in ONVIF? Last I remember, only PIR was available, is this still the case? I already have a relay in place for doorbell activity, but capturing through MQTT may unlock other options.
- Has anyone discovered a way to externally control the blue status LED on the doorbell? Would be neat to be able to integrate this into home automation (i.e. if door is locked, turn on the LED)
alexdelprete
Getting comfortable
Unfortunately it seems the "Complete Restoration" option doesn't seem to work in all cases, I updated the guide to use "Partial Restoration", that should work and I think it does the same thing as the "Restore Default Settings" option in System Maintenance.
alexdelprete
Getting comfortable
Step 2 was the original reset procedure I wrote for the guide, but some users noticed that it didn't reset everything. So I thought about a more complete reset, but it seems it doesn't work for all users. So I modified the guide to use "Partial Restoration".
Attachments
alexdelprete
Getting comfortable
1. Unfortunately doorbell button press event seems not to be available in the ONVIF events of the camera. I asked someone who studied the APIs in this thread. Many users, including me, are yousing SAGE sensor to detect the press button event in our automation hubs, from there you can do whatever you want, also MQTT.
2. Not that I know of, but I might have missed some posts in the thread. The camera's fw is not really "open", and not so flexible.