So I gather a simple reset of the unit would not of worked? Or did you not want to go through the setup again?
New RCA HSDB2A 3MP Doorbell IP Camera
- Thread starter fleece
- Start date
So did your unit just lose it's WiFi network settings or did you change something in the Batch Config. Tool that may have caused this? Awesome fix though...
Found this:
EZVIZ Support - Creating Easy Smart Homes
Welcome to EZVIZ support. From product support to FAQ and download center, we will help you with your EZVIZ products.
usservice.ezvizlife.com
How to setup EZVIZ devices with Alexa Echo Show?
EZVIZ skills for Alexa currently work only with the following EZVIZ cloud cameras: Mini, Mini O, Mini Plus, Mini 360 Plus, Mini Trooper, Husky and Husky dome. Before connecting to Amazon Echo Show, log in to your EZVIZ App and go to the Camera Settings. Look for the “Image Encryption” and tap to turn it off. Change the name of your camera. Ensure that you select a suitable name for your camera, such as “baby room camera” or “front door camera.” Please ensure that you are configuring the EZVIZ skills correctly. Follow the steps below to properly configure EZVIZ skills with your Alexa app;
1. Log into your Alexa app
2. From the menu options choose skills
3. Type EZVIZ on the search bar, locate EZVIZ and enable the skill
4. Enter your EZVIZ username/password to authorize Alexa to access your EZVIZ account
5. Tap the “Discover devices” tab to allow Alexa discover all your EZVIZ device
6. Go back to menu list and select smart home, under devices you should see all your EZVIZ devices under devices
Please ensure that you have decent internet connection speed both for the Echo show and the EZVIZ device you have linked up with your Alexa. We do recommend that you maintain at least 1 Mbps upload speed per EZVIZ device on your network
These the same steps for Ezviz/Laview/Imou/Dmss based off Hikvision's instructions. I've been using this instruction successfully since Spring for my other Ezviz compatible cameras like Mini 360 Plus (Annke)variant, Mini O (Annke)variant, etc as they get discovered by Ezviz Alexa skills and also with Ezviz Google Home. Only doorbell is undiscoverable for some reason.Found this:
EZVIZ Support - Creating Easy Smart Homes
Welcome to EZVIZ support. From product support to FAQ and download center, we will help you with your EZVIZ products.
How to setup EZVIZ devices with Alexa Echo Show?
EZVIZ skills for Alexa currently work only with the following EZVIZ cloud cameras: Mini, Mini O, Mini Plus, Mini 360 Plus, Mini Trooper, Husky and Husky dome. Before connecting to Amazon Echo Show, log in to your EZVIZ App and go to the Camera Settings. Look for the “Image Encryption” and tap to turn it off. Change the name of your camera. Ensure that you select a suitable name for your camera, such as “baby room camera” or “front door camera.” Please ensure that you are configuring the EZVIZ skills correctly. Follow the steps below to properly configure EZVIZ skills with your Alexa app;
1. Log into your Alexa app
2. From the menu options choose skills
3. Type EZVIZ on the search bar, locate EZVIZ and enable the skill
4. Enter your EZVIZ username/password to authorize Alexa to access your EZVIZ account
5. Tap the “Discover devices” tab to allow Alexa discover all your EZVIZ device
6. Go back to menu list and select smart home, under devices you should see all your EZVIZ devices under devices
Please ensure that you have decent internet connection speed both for the Echo show and the EZVIZ device you have linked up with your Alexa. We do recommend that you maintain at least 1 Mbps upload speed per EZVIZ device on your network
I waited trying this on my RCA HSDB2A variant until after Summer because Ezviz didn't promise ONVIF or Alexa until their newer FW was released after Q2. However, even with newer FW including the latest one I upgraded to in early October from Laview doesn't seem to allow my RCA HSDB2A doorbell from being discoverable by Alexa and Google Home. Ezviz support says wait for new app update to see if it fixes it but still fails even with latest Ezviz app V4.0.4.1217 that I upgraded to yesterday.
No, the doorbell doesn't even show up in list of linkable devices like my other ezviz compatible camera variants.
Account linking is successful in both Google Home and Alexa as my other devices show up fine and I can say "show xxx" and view their live feed to that camera. Since the doorbell hardware inert are supposed to be similar between all the variants and only slight differences in mobile app/FW, you'd think my RCA HSDB2A unit should be detectable in Alexa and Google Home UNLESS Ezviz excluded my RCA doorbell S/N from traversing thru their Ezviz<->Alexa/Google gateway. I'm crossing my fingers it's just user error on my part so hopefully someone else with an RCA variant can confirm success with Ezviz Alexa Skills.
rafale
Pulling my weight
The unit reset itself without me interacting with it. I just didn't know what the new password was. Resetting the unit seems to reset everything except for the admin user password, the activations code (which are supposed to be the same but may not be) and the serial number. Each firmware generates its own default SSID and wifi password based on the serial number and the activation code when you reset them.
The big warning on the 101 should be to never change the admin passcode by "activating" using the hikvision softwares because they do not allow you to take it back to match the activation code. This is not reversible and will require some hoop jumping in the future because the mobile app are restricting what the SSIDs can be and they also expect the admin password and the activation code to be the same.
Last edited:
Do you mind writing up a warning for me to put in the 101. I have read ya'lls messages but don't know how to put it in a Warning.
Thank You,
David
rafale
Pulling my weight
Warning should read like this:
When loading batch configuration for the first time and your doorbell is discovered, it will show as "not activated" under security. Do not click the "activate" function button. It will force you to set a new admin password on the device which, for any hikvision camera, is part of the normal setup process but will confuse the mobile apps for the doorbell. More generally do not change the admin password in iVMS or Batch configuration. It is not reversible and cannot be reset either by factory settings reset or firmware reload.
When loading batch configuration for the first time and your doorbell is discovered, it will show as "not activated" under security. Do not click the "activate" function button. It will force you to set a new admin password on the device which, for any hikvision camera, is part of the normal setup process but will confuse the mobile apps for the doorbell. More generally do not change the admin password in iVMS or Batch configuration. It is not reversible and cannot be reset either by factory settings reset or firmware reload.
Last edited:
So, Ken asked if I could get any API documentation for the DB1. I searched the net and didn't find anything specific, but did find a couple of e-mail addresses to try. First one, techsupport.usa@hikvision.com and their response:Ken took a quick look last night, and discovered what we already know. There's no HTTP/port 80 web server running on this doorbell.I've offered to purchase one and have it sent to Ken for hands-on, but still waiting to hear back from him. He's a busy man, it's the holidays, and it's a Hikvision doorbell camera. You didn't think this was going to happen quickly and easily, did you?
Well, duh. I know EZVIZ is all marketing and no tech, the tech is at Hikvision. That's why I asked Hikvision.Hikvision said:
Sent the same request for API documentation to techsupport@ezvizlife.com and this was their response:
Okay dude, you can't even spell 'our' correctly, you left a period off, and you admit you have nothing technical to offer. Techsupport? Really?!?EZVIZLife said:
Vaguely reminiscent of the original Hikvision first gen doorbell "It doesn't support RTSP."
Hex edit the software, there are the RTSP paths/URLs embedded within.
VF is gonna go fishing with binwalk and a hex editor at home tonight.
Last edited:
rafale
Pulling my weight
Looking forward to see what you find out. Try maybe to use a packet tracer like wireshark with an android VM. I used that to intercept and reproduce app commands to control some air filters before... Assuming that the app commands are local when the camera is on the local network, it should work.
Added to 101, Thank You rafale, I changed it a bit and will probably/eventually move it to another area on the 101. Just want to find a different word instead of "confuse"
rafale
Pulling my weight
Added to 101, Thank You rafale, I changed it a bit and will probably/eventually move it to another area on the 101. Just want to find a different word instead of "confuse"
How about "disrupts future re-inclusions/configuration through the mobile apps"
Ken suggested Android, but I don't have any Android devices at home.
(Well, there's this one tablet, but it's pretty crappy, and I'd rather not mess with it.)
Sounds good to me. So I included your original message Link with your name at the end in the 101. If you want go an edit your original so if someone clicks the link there is no "confusion"
there is that word Thanks a million for this Warning, it will help new owners not make this mistake...
Last edited:
rafale
Pulling my weight
I am thinking android because... you actually don't need a device. You can run it in a virtual machine on a PC... And on the same PC setup wireshark so you can see the packets go in and out from the android app.
The best Android emulators for PC and Mac of 2024
We talk a lot about emulating PC experiences on our phones, but what about putting phones on PC? Let's look at the best Android emulators.
www.androidauthority.com
I did this a while ago. Had to refresh my memory.
Last edited:
There is a lot of Great post here early on. I remember reading about API and SDK and even someone writing a C Code but this is way over my head...Thank you for your work on this...