We do not have a full comparison but the 101 lays out some of the differences. It depends on what you are looking for. The EZVIZ supports Alexa and Google, the LaView only supports Alexa. Certain brands come with different covers. Here is a small chart...neuro said:
Does anyone have a link to a comparison between all of these cameras? I've been trying to follow this thread, and have had my eyes set on Nelly's version, but wasn't sure why everyone is using other brands.
Normally the power kit is needed when you have a chime, it helps regulate the power between the DB and the chime. Without a chime most install the fuse...Yeah found that but could do with knowing what pin goes where.
Edit, and whilst your here, i do not have a chime so when i put the power kit in i wire it in series, then i basically put the sage wires to the same connections, sage in parallel to the power kit?
Cheers
Yeah we have GV too. When we got rid of our landline we got an OBi200 and a free (local) phone number from Google Voice. Nice to have free VoIP phone. Since we have a Panasonic (Link2Cell) system, it was easy to connect. So for those who don't know how the Link2Cell works, you connect your cell phones to the system via Bluetooth and when you get a call on your Cell Phone, all the Panasonic phones ring, so you don't have to carry your Cell Phone throughout your house. Also you get Text announcements too, only the announcement, it does not read your text for you. We have our wireless handsets all over the house, yet we still miss calls, haha, old age I guess , or call screening since the system announces names from your cell phone contacts (Or you can setup separate contacts on the system).just this to sort then on to curl/soap maybe, would like to get the answer doorbell bit in the settings to work on a geofence
Are you writing about shutting off the answer doorbell bit by using curl / soap to trigger an on and off of the application running on your smart phone while concurrently doing Geofence?
Here utilize multiple hard wired sensors in home for occupation related automation events. (combo PIR/Microwave and 180 degree ceiling sensors).
The automobiles have long range RFID tags which trigger events while parked in garage or driveway. The tags do not drain the batteries in the automobiles.
I did this mostly because I shut off my phones while at home.
I do use GV to transfer all calls to the house phones plus the Panasonic phone system allows for two cellular phones to be connected via Bluetooth for voice and messaging.
Found out though that Google voice is not available outside of the US.
bookmarked! This is awesome, thank you!We do not have a full comparison but the 101 lays out some of the differences. It depends on what you are looking for. The EZVIZ supports Alexa and Google, the LaView only supports Alexa. Certain brands come with different covers. Here is a small chart...
View attachment 62743
View attachment 62742
This has been discussed in the past: in my personal experience, the power kit is always needed, strange power related issues happened with or without the chime...the power kit stabilizes things. Without the power kit the SAGE didn't work in my case. I also installed the fuse. Rock solid with this setup.Normally the power kit is needed when you have a chime, it helps regulate the power between the DB and the chime. Without a chime most install the fuse...
Unless I am missing something here with the Sage...
If you have not already seen these links, maybe these will help you:
⦁ Sage Sensor - TechBill - alexdelprete - TechBill (Sage with SmartThings)
I wonder why they did not implement the power kit in the DB, since it seems to be a must.This has been discussed in the past: in my personal experience, the power kit is always needed, strange power related issues happened with or without the chime...the power kit stabilizes things. Without the power kit the SAGE didn't work in my case. I also installed the fuse. Rock solid with this setup.
Yes or if BI could do it via curl, that would be the ideal solution for me, BI geofence works well, i do have smartthings but only for the Sage db and Alexa, i don't know enough about it all myself and would't know were to start, i do curl my cams for day/night settings and that was a stretch.just this to sort then on to curl/soap maybe, would like to get the answer doorbell bit in the settings to work on a geofence
Are you writing about shutting off the answer doorbell bit by using curl / soap to trigger an on and off of the application running on your smart phone while concurrently doing Geofence?
I guess it would not have this nice slick appearance. Its one of the smallest, best looking doorbells around I think.I wonder why they did not implement the power kit in the DB, since it seems to be a must.
Also space and cost probably. This camera has an unbeatable price/performance ratio, IMHO. There are overpriced doorbells which force you to subscribe expensive cloud services. But obviously intended audience is not the hobbyst like us. Not everybody likes or knows how to do these things, it requires a little bit of IT and electronic knowledge. Not for "apple users" let's say.I guess it would not have this nice slick appearance. Its one of the smallest, best looking doorbells around I think.
Which I did after each firmware change even if I did the reset none of the firmware I tried were able to let me activate WDR on anything under CCD menu without have the config tool crashing and not saving the changeIf you upgrade to another vendor's firmware, you should reset config, otherwise there are a number of small problems like the one you mentioned. WDR works perfectly.
First time I read about this problem in this thread. The only thing other users complained about WDR was that it was grayed out, and that's because BLC was on, they're mutually exclusive options. Is it the only option that crashes your Batch Config?Which I did after each firmware change even if I did the reset none of the firmware I tried were able to let me activate WDR on anything under CCD menu without have the config tool crashing and not saving the change
In the ivms-4200 soft the CCD menu is not there so no way to try to enable WDR and in EZVIZ studio I can see the cam no problem but there's no way to really configure it like with config tool or ivms-4200 unlees there is and I just missed itBatch Config Tool? Have you tried the iVMS-4200 software (I use the legacy version 2)? Also you may try EZVIZ PC Studio.
I tried from my laptop and from my BI vm same thing it craches. I tried to play with WDR, BLC, exposure, white balance, DNR all make the client to close itself or stays open with this error:First time I read about this problem in this thread. The only thing other users complained about WDR was that it was grayed out, and that's because BLC was on, they're mutually exclusive options. Is it the only option that crashes your Batch Config?
Did you try from a different PC? Which Batch Config version? A crash could mean that after the WDR change and save, the camera responds with malformed data that is not managed by the app.
Figure out the problem I downloaded version 3.0.2.6 version of config tool and now I was able to enable WDR under CCD menu. There's something in version 3.0.3.8 I guees that is not compatible with the DB1 doorbellI tried from my laptop and from my BI vm same thing it craches. I tried to play with WDR, BLC, exposure, white balance, DNR all make the client to close itself or stays open with this error:
View attachment 62763
version of sotware is 3.0.3.8, firmware tried are EZVIZ 191211/200220 and HIK 200321
That error message confirms what I wrote in my previous post: the app receives incorrect data from the device. That's because the underlying data structure is messed up. I think you didn't really reset the camera, it can happen.I tried from my laptop and from my BI vm same thing it craches. I tried to play with WDR, BLC, exposure, white balance, DNR all make the client to close itself or stays open with this error:
View attachment 62763
version of sotware is 3.0.3.8, firmware tried are EZVIZ 191211/200220 and HIK 200321
Great. I didn't even know 3.0.3.8 existed. Probably data structure for newer models/cams has changed. Stick to 3.0.2.6.Figure out the problem I downloaded version 3.0.2.6 version of config tool and now I was able to enable WDR under CCD menu. There's something in version 3.0.3.8 I guees that is not compatible with the DB1 doorbell