New RCA HSDB2A 3MP Doorbell IP Camera

[Olddawg]

Is there a way to turn off the beep when it detects motion?

Yes it is in the app. if you want to turn off the beep at the doorbell Alarm Notification - Notification Sound Mode Mute. If you want to turn it off on your phone Alarm Notification - Silenced

 

[blahblahyoutoo]

thx, the wording was slightly ambiguous. I thought it would disable notifications on my phone.

 

[argus]

For those of you who who put the LaView firmware on the RCA doorbell (to gain ONVIF capability): does the RCA mobile app still work?

Yes RCA, EZVIZ and HIK Connect apps all working with the La View firmware. To use the LaView app I had to delete the camera from the other apps and register it with LaView but decided to go back to RCA on the phone and HIK Connect on the IPad because I have a HIK NVR

 

[flynreelow]

Yes RCA, EZVIZ and HIK Connect apps all working with the La View firmware. To use the LaView app I had to delete the camera from the other apps and register it with LaView but decided to go back to RCA on the phone and HIK Connect on the IPad because I have a HIK NVR

What did you like about the RCA app to make u change back from the LaView app.

 

[argus]

What did you like about the RCA app to make u change back from the LaView app.

I went back because of the device registration requirement, I couldn't have LaView on the phone and HIK Connect on the Ipad.

 

[camCanuck]

I use the EZVIZ app with the LaView firmware on the RCA camera. No issues.

 

[Chadsturgill]

Am I the only one that can’t login to either of the LaView apps with my ID. It works on all the other ones (RCA, EZVIZ, Uniden, Claire, Guarding Vision etc.but not LaView) keeps telling me invalid account. I’ve tried username, phone number and email. At one point in time I created a new account with the same email on LaView One because it would not take my EZVIZ account. Now I can’t get into LaView Connect either. I even deleted that new account with the same email address.

 

[Chadsturgill]

Okay figured out the LaView situation. Have to remove camera from old account first. Nothing special about their apps, so moved back.

As for Nelly's Firmware the latest is 5.2.4 Build 190625. Got it right from Nelly's.
Box

Flashing from LaView firmware to Nelly's caused me to need to reset the camera. This was a bit of a bear. Had to remove the camera from the app because it expected the Wifi being presented from the camera to be HSDB2_deviceserial when using RCA App. For EZVIZ it expected EZVIZ_deviceserial. For Guarded Vision it wanted HAP_device serial. Not until I removed the camera from the App/account was I able to add it back with the Guarding Vision app using what the camera was actually presenting which is "softap_deviceserial" For anyone stuck here the password is "softap_devicepw" This really hung me up for awhile. Even Nelly's was a bit stumped. I did some packet captures and I still can't find the URL for where it upgrades and I tried both the iphone IP and the camera IP. Neither showed me a check at that URL. However I did find a lot of OnVif details in the packet capture in the Nelly's firmware. Here is some of the decoded text from the UDP packet for the onvif stuff.

<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="XML Schema" xmlns:tt="http://www.onvif.org/ver10/schema" xmlns:tds="http://www.onvif.org/ver10/device/wsdl" xmlns:trt="http://www.onvif.org/ver10/media/wsdl" xmlns:timg="http://www.onvif.org/ver20/imaging/wsdl" xmlns:tev="http://www.onvif.org/ver10/events/wsdl" xmlns:tptz="http://www.onvif.org/ver20/ptz/wsdl" xmlns:tan="http://www.onvif.org/ver20/analytics/wsdl" xmlns:tst="http://www.onvif.org/ver10/storage/wsdl" xmlns:ter="http://www.onvif.org/ver10/error" xmlns:dn="http://www.onvif.org/ver10/network/wsdl" xmlns:tns1="http://www.onvif.org/ver10/topics" xmlns:tmd="http://www.onvif.org/ver10/deviceIO/wsdl" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl" xmlns:wsoap12="http://schemas.xmlsoap.org/wsdl/soap12" xmlns:http="http://schemas.xmlsoap.org/wsdl/http" xmlns:d="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsadis="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wstop="http://docs.oasis-open.org/wsn/t-1" xmlns:wsrf-bf="http://docs.oasis-open.org/wsrf/bf-2" xmlns:wsntw="http://docs.oasis-open.org/wsn/bw-2" xmlns:wsrf-rw="http://docs.oasis-open.org/wsrf/rw-2" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsrf-r="http://docs.oasis-open.org/wsrf/r-2" xmlns:trc="http://www.onvif.org/ver10/recording/wsdl" xmlns:tse="http://www.onvif.org/ver10/search/wsdl" xmlns:trp="http://www.onvif.org/ver10/replay/wsdl" xmlns:tnsn="http://www.eventextension.com/2011/event/topics"><env:Header><wsadis:MessageID>urn:uuid:NOT SURE IF THIS IS UNIQUE TO ME SO I OBFUSCATED IT FROM HERE</wsadis:MessageID>
<wsadis:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsadis:To>
<wsadis:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Hello</wsadis:Action>
<d:AppSequence InstanceId="NOT SURE IF THIS IS UNIQUE TO ME SO I OBFUSCATED IT FROM HERE" MessageNumber="0"/>
</env:Header>
<env:Body><d:Hello><wsadis:EndpointReference><wsadis:Address>urn:uuid:NOT SURE IF THIS IS UNIQUE TO ME SO I OBFUSCATED IT FROM HERE</wsadis:Address>
</wsadis:EndpointReference>
<d:Types>dn:NetworkVideoTransmitter tdsevice</d:Types>
<d:Scopes>onvif://www.onvif.org/type/video_encoder onvif://www.onvif.org/Profile/Streaming onvif://www.onvif.org/type/audio_encoder onvif://www.onvif.org/hardware/HSDB2 onvif://www.onvif.org/name/HSDB2 onvif://www.onvif.org/location/</d:Scopes>
<d:XAddrs>http://MY DEVICE IP ADDRESS/onvif/device_service</d:XAddrs>
<d:MetadataVersion>10</d:MetadataVersion>
</d:Hello>
</env:Body>
</env:Envelope>

 

[camCanuck]

What's the advantage of Nelly's over the newer LaView? Seems like theirs may be a little custom based on the required reset and separate cloud account.

 

[flynreelow]

What's the advantage of Nelly's over the newer LaView? Seems like theirs may be a little custom based on the required reset and separate cloud account.

Was kind of wondering the same, as I believe the LaView firmware also has Onvif, and the Substream (correct me if im wrong) ??

 

[camCanuck]

It does. My RCA on LaView has ONVIF, substream and no logo.

 

[JSnP]

. I did some packet captures and I still can't find the URL for where it upgrades and I tried both the iphone IP and the camera IP. Neither showed me a check at that URL.

I've never seen my RCA check that usdownload.ezvizlife url; I suspect it doesn't ever go there unless it is downloading a new version.

So I don't think you would see the URL in a packet capture unless you had an older version of the Nelly Firmware and upgraded through their app (ezviz app?) if that is how Nelly users do it.

 

[Chris Taylor]

The various apps seem so similar, yet there are key features missing from some that are present in others. I keep going back to the RCA app because it as a 'Call Log' that shows date/time and picture of who pushed the button. EZVIZ, Hik-Connect, and Guarding Vision don't seem to have this log. I found some of the apps (Laview, Hik-Connect) squish the video to a rectangle while others (RCA, EZVIZ) keep the aspect ratio, which keeps people from looking like Stewey from Family Guy. I was able to log into some of the other apps using the credentials I created for the RCA app, but some of the them made me create new credentials, which then required me to delete the camera from the other account in order to add it to the new one. Nelly's is the only one I haven't installed yet.

 

[flynreelow]

Laview has the same call log and doesn't seem to squish the video as you described.

 

[Chris Taylor]

Installed Laview's firmware (build 190716) on the RCA hardware and then removed the 'Generic RTSP' camera from my NVR (QVR Pro) and added a 'Generic ONVIF' camera in its place. The video feed added seamlessly. It took me several tries to get the rtsp url correct to get the old version of the camera added, whereas the onvif added itself the first time with a lot less fields to fill in. That was an improvement.

But... I was hoping the onvif feed would allow me to receive motion events so I could set my NVR to record on motion instead of all the time, but QVR Pro doesn't seem to recognize the camera as a motion detector. Is it the feed from the camera or do I just need to change how the camera is added inside the NVR? Are y'all getting motion events out of the camera on the onvif feed?

 

[David L]

Okay figured out the LaView situation. Have to remove camera from old account first. Nothing special about their apps, so moved back.

As for Nelly's Firmware the latest is 5.2.4 Build 190625. Got it right from Nelly's.
Box

Flashing from LaView firmware to Nelly's caused me to need to reset the camera. This was a bit of a bear. Had to remove the camera from the app because it expected the Wifi being presented from the camera to be HSDB2_deviceserial when using RCA App. For EZVIZ it expected EZVIZ_deviceserial. For Guarded Vision it wanted HAP_device serial. Not until I removed the camera from the App/account was I able to add it back with the Guarding Vision app using what the camera was actually presenting which is "softap_deviceserial" For anyone stuck here the password is "softap_devicepw" This really hung me up for awhile. Even Nelly's was a bit stumped. I did some packet captures and I still can't find the URL for where it upgrades and I tried both the iphone IP and the camera IP. Neither showed me a check at that URL. However I did find a lot of OnVif details in the packet capture in the Nelly's firmware. Here is some of the decoded text from the UDP packet for the onvif stuff.

<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="XML Schema" xmlns:tt="http://www.onvif.org/ver10/schema" xmlns:tds="http://www.onvif.org/ver10/device/wsdl" xmlns:trt="http://www.onvif.org/ver10/media/wsdl" xmlns:timg="http://www.onvif.org/ver20/imaging/wsdl" xmlns:tev="http://www.onvif.org/ver10/events/wsdl" xmlns:tptz="http://www.onvif.org/ver20/ptz/wsdl" xmlns:tan="http://www.onvif.org/ver20/analytics/wsdl" xmlns:tst="http://www.onvif.org/ver10/storage/wsdl" xmlns:ter="http://www.onvif.org/ver10/error" xmlns:dn="http://www.onvif.org/ver10/network/wsdl" xmlns:tns1="http://www.onvif.org/ver10/topics" xmlns:tmd="http://www.onvif.org/ver10/deviceIO/wsdl" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl" xmlns:wsoap12="http://schemas.xmlsoap.org/wsdl/soap12" xmlns:http="http://schemas.xmlsoap.org/wsdl/http" xmlns:d="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsadis="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wstop="http://docs.oasis-open.org/wsn/t-1" xmlns:wsrf-bf="http://docs.oasis-open.org/wsrf/bf-2" xmlns:wsntw="http://docs.oasis-open.org/wsn/bw-2" xmlns:wsrf-rw="http://docs.oasis-open.org/wsrf/rw-2" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsrf-r="http://docs.oasis-open.org/wsrf/r-2" xmlns:trc="http://www.onvif.org/ver10/recording/wsdl" xmlns:tse="http://www.onvif.org/ver10/search/wsdl" xmlns:trp="http://www.onvif.org/ver10/replay/wsdl" xmlns:tnsn="http://www.eventextension.com/2011/event/topics"><env:Header><wsadis:MessageID>urn:uuid:NOT SURE IF THIS IS UNIQUE TO ME SO I OBFUSCATED IT FROM HERE</wsadis:MessageID>
<wsadis:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsadis:To>
<wsadis:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Hello</wsadis:Action>
<d:AppSequence InstanceId="NOT SURE IF THIS IS UNIQUE TO ME SO I OBFUSCATED IT FROM HERE" MessageNumber="0"/>
</env:Header>
<env:Body><d:Hello><wsadis:EndpointReference><wsadis:Address>urn:uuid:NOT SURE IF THIS IS UNIQUE TO ME SO I OBFUSCATED IT FROM HERE</wsadis:Address>
</wsadis:EndpointReference>
<d:Types>dn:NetworkVideoTransmitter tdsevice</d:Types>
<d:Scopes>onvif://www.onvif.org/type/video_encoder onvif://www.onvif.org/Profile/Streaming onvif://www.onvif.org/type/audio_encoder onvif://www.onvif.org/hardware/HSDB2 onvif://www.onvif.org/name/HSDB2 onvif://www.onvif.org/location/</d:Scopes>
<d:XAddrs>http://MY DEVICE IP ADDRESS/onvif/device_service</d:XAddrs>
<d:MetadataVersion>10</d:MetadataVersion>
</d:Hello>
</env:Body>
</env:Envelope>

So with all the onvif.org references you would think it would be listed as a registered device on onvif.org but I can't find LaView's or Nelly's...
https://www.onvif.org/conformant-products/

 

[flynreelow]

It does. My RCA on LaView has ONVIF, substream and no logo.

Just put on the LaView Firmware on my RCA doorbell. Onvif and Sub stream work great... but I still have the RCA logo. Not a huge deal as it doesnt cover up anything i need.

 

[David L]

Just put on the LaView Firmware on my RCA doorbell. Onvif and Sub stream work great... but I still have the RCA logo. Not a huge deal as it doesnt cover up anything i need.

So you may try loading EZVIZ first, turn on Logo, then load LaView's and hopefully it will turn it off:

Update...

Switched to LaView firmware and ONVIF is up and running with Synology SS (I was previously using RTSP).

My RCA logo is still gone, maybe because I turned it on with the EZVIZ firmware first?

 

[Chris Taylor]

Do any of these various firmwares provide the ability to control video settings like brightness? The overhang over my front door provides enough shade so that everyone that approaches is backlit by the daylight behind them resulting in most of the recordings being of silhouettes rather than detailed faces.

 

[flynreelow]

If you open it up in IVMS4200 you have access to change anything you need regarding the picture...

Do any of these various firmwares provide the ability to control video settings like brightness? The overhang over my front door provides enough shade so that everyone that approaches is backlit by the daylight behind them resulting in most of the recordings being of silhouettes rather than detailed faces.