New RCA HSDB2A 3MP Doorbell IP Camera

Glen Mark said:
Hey Chad, you used to prefer the RCA app. What changed?

I hate the lag in notifications on Android -- it impacts the ones I've tried -- RCA, EZVIZ, GUARDING VISION -- the last one I tried because I saw someone post under the RCA app that RCA recommended it to them. It doesn't seem to wake up for notifications any better than EZVIZ (the last one I was using) and it doesn't have doorbell config options, it doesn't have the anti-fish-eye zoom, and it plays no sound when someone presses the doorbell (you have to have the phone on your desk to see that someone rang the bell)

Pfff. Do Ring customers have these issues??
Click to expand...
From a bit of digging, the delayed notifications seem to be due to Android's over-zealous Doze functionality. But you can turn if off for indivual apps, but it's hidden. Here's some instructions:

it’s in Settings > Apps & notifications > Advanced > Special app access > Battery optimization. Simply find the app you want to exempt and tap to switch from “Optimize” to “Don’t optimize.”

I just set this off for EZVIZ so I'll see if I get these alerts in real time
 
  • Like
Reactions: Tony Chiaffredo
Glen Mark said:
Hey Chad, you used to prefer the RCA app. What changed?

I hate the lag in notifications on Android -- it impacts the ones I've tried -- RCA, EZVIZ, GUARDING VISION -- the last one I tried because I saw someone post under the RCA app that RCA recommended it to them. It doesn't seem to wake up for notifications any better than EZVIZ (the last one I was using) and it doesn't have doorbell config options, it doesn't have the anti-fish-eye zoom, and it plays no sound when someone presses the doorbell (you have to have the phone on your desk to see that someone rang the bell)

Pfff. Do Ring customers have these issues??
Click to expand...

Honestly I keep changing my mind. Each individual app update changes my opinion. I tried all of them again yesterday and now I am preferring the Guarding Vision which is what Nellys uses.

As for the LaView Connect app, it uses the same credentials as the rest, however the new LaView One app (new for this doorbell) seems to use it's own authentication system. I created a new account in that app but haven't added my doorbell to it yet. I am a little afraid to do that honestly and it seems like it wouldn't work because it wouldn't be sending the alerts or notifications to the correct cloud system due to that seemingly being baked into the firmware. Maybe that would get me to the LaView Firmware though, however if it uses a different cloud backend then would we even want that?
 
Nice find. I wonder if the camera is the Starlight in the RCA version. I couldn’t find mention of that anywhere. My RCA has exceptional night quality. I assume they are identical hardware.
 
From the spec sheet: Image sensor 1/2.8”3-Megapixel starlight sensor
https://www.laviewsecurity.com/files/datasheet/LV-PDB1630-U.pdf

The only thing I am bummed about is that it appears to only come with a white face plate.

Did you ever try connecting your RCA to the LaView Connect app? I am looking at LaView's NVR and a few IP cams... plus the doorbell. My goal is single app for live view of all cameras and recorded footage. I currently have a Nest Hello and 2 indoor IQ cams. They work great, but I am constantly going over my ISP bandwidth cap.
 
Yes, LaView Connect worked for me up until the point that I created a new account on the new LaView One app. It appears they do an authentication directory walk against their local system first then the other one for LaView Connect but for LaView One, they only Auth against their new system. However, adding my camera wasn’t possible without removing it from the other account. So regardless of what authentication system they are using, it appears they are still tied to the back end cloud for the serial number and how the communication works. So I didn’t want to mess with it. If someone buys a new RCA and wants to test it, there would be little risk. Also you possibly would get the new firmware that hopefully gets rid of the rca logo. Worst case, it has a LaView logo. The funny thing about these two authentication systems is I used the same email and password for both. But they clearly are different. So that definitely tells me they setup their own back end directory for LaView One with backend cloud being the same.
 
I could not find details like that for the RCA Security Doorbell specifically calling out what camera chip they are using in the doorbell.
 
  • Like
Reactions: flynreelow
flynreelow said:
Please keep us posted
Click to expand...
Getting ready to set this up. Does anyone want me to try to set up as LaView Connect or just go ahead and set it up as RCA ? Does anyone have a suggestion as to which firmware to run with and which service to test out and report back ?
 
I am interested in it being setting it up under LaView Connect. I am curious to see if it updates the RCA firmware to LaView.
 
Aocam said:
Getting ready to set this up. Does anyone want me to try to set up as LaView Connect or just go ahead and set it up as RCA ? Does anyone have a suggestion as to which firmware to run with and which service to test out and report back ?
Click to expand...
I'd be interested if you can test with setting it up with the "LaView One" app. I already know the "LaView Connect" app is very similar to RCA/Ezviz/etc app but I had to create a new identical account 3 weeks ago for the newer "LaView One" app as it would not accept credentials from my RCA/Ezviz/etc that is shared between HSDB1 and HSDB2.
 
Decided to that I had enough work for the day , and bench set up camera in my office.
No issue using LaView ONE app to register camera.
Interesting fact, I have DB1 installed and registered through Hik-connect app. Used the same email and pw - no conflicts. Created new LA account for me, found and registered camera
Found new firmware 0124 - and is currently downloading it to the camera.
What do you guys want me to upload here? I think someone was interested in "branding". Keep in mind - I am real newbee so let me know what you want me to test and upload here.
 
Next update. Testing with my phone (and I had one of my guys leave the room) hear a LOT of echo. Anything say to the camera, echos back with 1 second. DB1 did not do that.
 
If using the RCA firmware, there will be a RCA logo at the top left hand corner of the live view or recordings if connected to NVR. The firmware version looks to be same as the RCA HSDB2 v5.2.4 build 190124. I'm interested in the following if you happen to have Alexa devices in your test bed.

Does the ONE Halo doorbell camera support Alexa devices?
Yes, the ONE Halo is compatible with select Amazon Echo devices. For example, you can simply say ‘Alexa, show front door’ to display the ONE Halo camera feed on Echo show, Echo spot, Kindle Fire Tablet and other Alexa devices.
 
Aocam said:
Decided to that I had enough work for the day , and bench set up camera in my office.
No issue using LaView ONE app to register camera.
Interesting fact, I have DB1 installed and registered through Hik-connect app. Used the same email and pw - no conflicts. Created new LA account for me, found and registered camera
Found new firmware 0124 - and is currently downloading it to the camera.
What do you guys want me to upload here? I think someone was interested in "branding". Keep in mind - I am real newbee so let me know what you want me to test and upload here.
Click to expand...

Can someone who has the RCA cam (@Chadsturgill ) report what firmware version their cam is running?

@Aocam - Does your video image have the RCA logo burned in the upper left corner?
 
You must log in or register to reply here.
Top Bottom