I'd have answered at 3 AM when I was awake earlier, but I successfully resisted the urge to open the laptop.Too Funny, I was just screen capping same pic right when you posted this message My suggestion was going to be the same.
I'd have answered at 3 AM when I was awake earlier, but I successfully resisted the urge to open the laptop.Too Funny, I was just screen capping same pic right when you posted this message My suggestion was going to be the same.
Love this Forum, you guys ROCK!!!I'd have answered at 3 AM when I was awake earlier, but I successfully resisted the urge to open the laptop.
So it is important to know what firmware you presently have before upgrading. I would be sure and upgrade to 190708 in the EZVIZ App before loading any other firmware.
For EZVIZ owners (ONLY); if you plan to install/upgrade your firmware to LaView's firmware you NEED to be sure and follow these steps: First Check your firmware in your App under Settings. If you have build 190304 DO NOT install LaView's firmware (If you do you will end up with a RCA Logo). If have the 190304 build you will NEED to update your firmware to EZVIZ build 190708 first. Next; with the 190708 build installed/confirmed go to Batch Config. Tool (Remote Configuration/Image/Video Display) check to see if the Logo is checked ON, if so, you will need to uncheck it Off before installing/upgrading to LaView's firmware.
There are many reason this Doorbell Rocks!!! Here is another one:
We Tested Ring’s Security. It’s Awful
Ring lacks basic security features, making it easy for hackers to turn the company's cameras against its customers.www.vice.com
So if you don't have build 190708 then you can load it like you would LaView or Nelly's in Batch Config. Tool. Just Do Not upgrade from your old firmware version (I assume 190304) to LaView or Nelly's.Thanks! I think I was still on the older FW although I told the app to look for updates multiple times, so maybe that's why the initial update didn't go thru.
AmenI am a very ardent advocate of taking your home automation and security camera functions off the cloud. The one stupidest thing you can do is to rely on the cloud to store your security camera footage. There is no way this can be secure and efficient so all these nest/ring etc are complete nonsense to me.
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?Ken responded late Wednesday afternoon. He's got access to the doorbell and will be researching it soon.
Not that I am aware of.Are there any change logs for any of these firmware? (thx for posting)
Me too, we must have the same notes. Only reason I did not put it in the 101 is I personally tried it and could not get it to work. Have you got it to work?@David L
I looked through the 101, and noticed in my doorbell notes started awhile back, I had this information on Google Home setup from @xaudiblex :
I ordered the EZviz DB1 verision of this camera for $89 the other day. It just came in and I love it! I did a firmware update and it supports RTSP as well as google assistant. To get google assistant to work, you have to disable the Image Encrypt feature and link ezviz to your Google home as a device. Camera should show up after you resync it. Now I can say, hey google, show me the front door.
Using my Andriod phone I can connect via wifi to the DoorBell using the SID of softap_Dnnnnnnn and the Verification code on the DB. When I use a browser on the phone I get a 404 when connecting to the Doorbell at 192.168..8.1 which looks to be the default IP of the Doorbell. If I knew the path to the configuration I might be able to manually set it up.
VIZ firmware.
I found a way around this. If you login utilizing LaView SSID and password, you can change the SSID and password to match the original EZVIZ SSID and password.
Me too, we must have the same notes. Only reason I did not put it in the 101 is I personally tried it and could not get it to work. Have you got it to work?
I do not have any problem putting this in the 101, I just cannot personally verify it works. Was hoping for a few more people to verify that is works instead of just one user. Most all of what is in the 101 has many user verifications.
When I try to Link I get a message that quickly goes by saying Linking your EZVIZ account, but when I check to see if it is Linked it does not show up in my Linked Accounts, resyncing several times does not help. So I go back and try again and I get the Authorize message, but Authorizing does nothing. I am not sure what I am missing. Again, not discrediting @xaudiblex just would like a few more users to confirm it works. Thank You giomania...
Google Home App, in adding new device below are my screens, there is an EZVIZ Login screen too I just did not include it here.
View attachment 52607View attachment 52603View attachment 52608
At least you got EZVIZ linked to your Google Home. Does it show in your Linked Devices?For me, I had never been able to get my RCA HSDB2A doorbell discovered by Google Home even though I can successfully linked the accounts between Ezviz and Google. I tried many times the past couple of months and Google Home can detect all my other Ezviz compatible cameras but not my RCA doorbell. I've been focusing on Amazon Alexa as I now have a couple Echo Show 8 but get same failure results. That is why I'm thinking my RCA(maybe by serial number) is excluded in the Hikvision(Ezviz) cloud backend as I'm running non-RCA FW and still can't get past this roadblock on both Google Home and Amazon Alexa.