Hi boys & girls,
I've been looking forward for my shipment containing plenty of stuff (thanks @EMPIRETECANDY for the great offer & price!), containing lots of IPC, NVR and the aforementioned intercom kit.
In this post, I'm going to try to describe, as objective possible, the pros and cons from the experience so far. I will include the instructions I have used for my setup, as it may help other users to find their way throughout their installation.
Comments & suggestions, do not hesitate to reach out!
Enjoy the reading!
CC.
CHAPTER 1: Packaging
Many of you have already ordered stuff from @EMPIRETECANDY , it was a brand new experience for me, but was worth the shot! All materials arrived in a preciously packaged and secured shipment. Nothing to complain on! Every cm³ was used, not a lot of waste.
CHAPTER 2: Unboxing
As I couldn't wait to assemble everything, I didn't grab pictures. What I can say: even the aluminium fronts of the VTO2000A doorbell have a plastic protective cover, all camera domes have a plastic too. The VTO really looks professional! The VTH1550CH screen is white with touch screen (also with good protective cover), it does also exist in aluminium (grey) for those who want.
CHAPTER 3: Use case
So in our particular case, I aimed for a "VILLA" installation through UTP (not a 2-wire, watch out when ordering that you pick the correct ones!), with 2 VTO's and 1 VTH. One VTO will be attached to the (electronic) gate, the other one at the front door. Which means that the architectural design comes down to:
In brief bill of material for this use case:
- 1* VTH1550CH
- 1* VTNS1060A "special" PoE switch
- 2* VTO2000A
Finally, to wallmount these VTO's on the concrete walls, I did add two VTOB108 "enclosures" for the final touch.
If you do not mount the VTNS switch into your electricity outlet, do not forget to add the power supply!!!
CHAPTER 4: Installation
There are different configuration manuals, depending on the model/version of the VTH. I got a version 3.1 which is different than the version 4.0. In short: you connect the first VTO by UTP to the VTNS switch, it gets the 192.168.1.110 default IP address. UTP connect the VTH to the VTNS switch, it gets 192.168.1.109 address. I opted to configure everything through the VTH, but you can also use Dahua toolbox (with VDPConfig) to configure it from your PC. But read the warning message below in Chapter 5: configuration! First impression: nice VTH screen, good resolution, VTO: LED light behind the name is tag is ... BRIGHT!!!
CHAPTER 5: Configuration
As my second VTO would conflict with the first VTO, I tried my configuration first with 1 VTO and 1 VTH, in the OOTB subnet. So first thing to do, is to configure the VTO on the VTH. Press "Project Settings" on the VTH, and you are prompted for a password. Apparently, depending on which version, you have to choose between 012345, 123456, 002236 or 888888. In my case, it was the latter. Verify the network settings (under <>NET), and press "search devices". It will scan the subnet and find the "defaulted" VTO. Press "ADD" and it receives a green icon. That was easy!
Press the ring button, and you'll get immediate video screen on the VTH with the option to hang up, or pick up. Sound & video are OK for a doorbell.
Then the more complicated bit: adding the second VTO. So you need to either shutdown the first VTO, or change that one to another IP (but then the link with the existing VTO breaks). I went for the first path, turned off the first VTO, attached the second one, and used the Webservices GUI login (admin/admin) to get to the configuration screen. In there, I changed the IP to 192.168.1.111.
Adding the VTO as second ringer in VTH worked but no connection could be made. It took me a while to figure out that with a 1+ VTO setup, each ringer needs to have a UNIQUE ID! Login in the webservices GUI, and go to LAN CONFIG and change the VTO No# to something differently than the first VTO:
With these settings, all works fine, each ringer can ring the VTH, and you can pickup or dismiss.
With the Dahua Toolbox (VDPConfig), you can always verify the network settings, and IP configuration. What I did try, is change the default passwords. DO NOT TRY THIS!!! For an unknown reason, my copy-pasted password from my vault did not get pushed through correctly, and I had to factory reset the VTO. Unlike the Dahua NVR or IPC, there is NO PASSWORD RESET CAPABILITY!!! For the VTO, you have to press 5 consecutive times the "intrusion detection switch" (keep note that the alarm will go on and off until you hear a distinct *beep*, which means your VTO is factory reset and the admin/admin combo works again).
CHAPTER 6: i/gDMSS
As we are in 2018, and an internet doorbell wouldn't be an internet doorbell, next step: mobile device. I tried both iOS and Android. It seemed that "doorbell" push notifications should work on the lite versions too, but as of beginning this week, the "plus" versions are for free, so no doubt to upgrade immediately to the plus version. Adding the VTO devices by IP gives you immediately "live view", with capability to electronically open the lock, and open a video communication towards the VTO. So far so good!
Then you have to go to the Alarm Manager, and turn on "notifications" for each of the VTOs.
Ringing the VTO gives a push notification, opening it gives an overlay screen with GREEN and RED button (pick-up & dismiss).
But then, it ... stops... working ... Clicking the green button gives a turning wheel, with in the end an error message with something like "talk has ended" (which disappears very quickly).
CHAPTER 7: upstream integration
I had choosen the VTH1550CH because it is also able to connect additional IPC's to the screen. Even an NVR as I found somewhere on the forum here. Testing this is easy: go to configuration, and press: "Add IPC". Choose Type (IPC, NVR, ... ) at right hand, entering IP address, port numbers, user and password. Easy peasy. But also here, after 6 characters, the keyboard seems to get stuck. As my NVR password is 12 characters long... No success here. In some thread, I've seen people having issues with VTO and no sound when passwords are longer than 6 characters. Maybe this thing is linked to the same configuration bug.
CHAPTER 8: Conclusion & wrap-up
So summing up my experience till today:
POSITIVE:
- great design!
- solid manufacturing!
- VTNS switch can potentially built in in electricity closets
- separate UTP network for the intercom kit
NEGATIVE:
- password troubles: setting it in VDPConfig is no go
- password troubles: no longer than 6 chars for adding an IPC/NVR (to be investigated more)
- VTH1550 does NOT have a Webservices GUI
- different versions of VTH devices (leading to tons of different default passwords)
- i/gDMSS bugs bugs bugs.
I've been looking forward for my shipment containing plenty of stuff (thanks @EMPIRETECANDY for the great offer & price!), containing lots of IPC, NVR and the aforementioned intercom kit.
In this post, I'm going to try to describe, as objective possible, the pros and cons from the experience so far. I will include the instructions I have used for my setup, as it may help other users to find their way throughout their installation.
Comments & suggestions, do not hesitate to reach out!
Enjoy the reading!
CC.
CHAPTER 1: Packaging
Many of you have already ordered stuff from @EMPIRETECANDY , it was a brand new experience for me, but was worth the shot! All materials arrived in a preciously packaged and secured shipment. Nothing to complain on! Every cm³ was used, not a lot of waste.
CHAPTER 2: Unboxing
As I couldn't wait to assemble everything, I didn't grab pictures. What I can say: even the aluminium fronts of the VTO2000A doorbell have a plastic protective cover, all camera domes have a plastic too. The VTO really looks professional! The VTH1550CH screen is white with touch screen (also with good protective cover), it does also exist in aluminium (grey) for those who want.
CHAPTER 3: Use case
So in our particular case, I aimed for a "VILLA" installation through UTP (not a 2-wire, watch out when ordering that you pick the correct ones!), with 2 VTO's and 1 VTH. One VTO will be attached to the (electronic) gate, the other one at the front door. Which means that the architectural design comes down to:
In brief bill of material for this use case:
- 1* VTH1550CH
- 1* VTNS1060A "special" PoE switch
- 2* VTO2000A
Finally, to wallmount these VTO's on the concrete walls, I did add two VTOB108 "enclosures" for the final touch.
If you do not mount the VTNS switch into your electricity outlet, do not forget to add the power supply!!!
CHAPTER 4: Installation
There are different configuration manuals, depending on the model/version of the VTH. I got a version 3.1 which is different than the version 4.0. In short: you connect the first VTO by UTP to the VTNS switch, it gets the 192.168.1.110 default IP address. UTP connect the VTH to the VTNS switch, it gets 192.168.1.109 address. I opted to configure everything through the VTH, but you can also use Dahua toolbox (with VDPConfig) to configure it from your PC. But read the warning message below in Chapter 5: configuration! First impression: nice VTH screen, good resolution, VTO: LED light behind the name is tag is ... BRIGHT!!!
CHAPTER 5: Configuration
As my second VTO would conflict with the first VTO, I tried my configuration first with 1 VTO and 1 VTH, in the OOTB subnet. So first thing to do, is to configure the VTO on the VTH. Press "Project Settings" on the VTH, and you are prompted for a password. Apparently, depending on which version, you have to choose between 012345, 123456, 002236 or 888888. In my case, it was the latter. Verify the network settings (under <>NET), and press "search devices". It will scan the subnet and find the "defaulted" VTO. Press "ADD" and it receives a green icon. That was easy!
Press the ring button, and you'll get immediate video screen on the VTH with the option to hang up, or pick up. Sound & video are OK for a doorbell.
Then the more complicated bit: adding the second VTO. So you need to either shutdown the first VTO, or change that one to another IP (but then the link with the existing VTO breaks). I went for the first path, turned off the first VTO, attached the second one, and used the Webservices GUI login (admin/admin) to get to the configuration screen. In there, I changed the IP to 192.168.1.111.
Adding the VTO as second ringer in VTH worked but no connection could be made. It took me a while to figure out that with a 1+ VTO setup, each ringer needs to have a UNIQUE ID! Login in the webservices GUI, and go to LAN CONFIG and change the VTO No# to something differently than the first VTO:
With these settings, all works fine, each ringer can ring the VTH, and you can pickup or dismiss.
With the Dahua Toolbox (VDPConfig), you can always verify the network settings, and IP configuration. What I did try, is change the default passwords. DO NOT TRY THIS!!! For an unknown reason, my copy-pasted password from my vault did not get pushed through correctly, and I had to factory reset the VTO. Unlike the Dahua NVR or IPC, there is NO PASSWORD RESET CAPABILITY!!! For the VTO, you have to press 5 consecutive times the "intrusion detection switch" (keep note that the alarm will go on and off until you hear a distinct *beep*, which means your VTO is factory reset and the admin/admin combo works again).
CHAPTER 6: i/gDMSS
As we are in 2018, and an internet doorbell wouldn't be an internet doorbell, next step: mobile device. I tried both iOS and Android. It seemed that "doorbell" push notifications should work on the lite versions too, but as of beginning this week, the "plus" versions are for free, so no doubt to upgrade immediately to the plus version. Adding the VTO devices by IP gives you immediately "live view", with capability to electronically open the lock, and open a video communication towards the VTO. So far so good!
Then you have to go to the Alarm Manager, and turn on "notifications" for each of the VTOs.
Ringing the VTO gives a push notification, opening it gives an overlay screen with GREEN and RED button (pick-up & dismiss).
But then, it ... stops... working ... Clicking the green button gives a turning wheel, with in the end an error message with something like "talk has ended" (which disappears very quickly).
CHAPTER 7: upstream integration
I had choosen the VTH1550CH because it is also able to connect additional IPC's to the screen. Even an NVR as I found somewhere on the forum here. Testing this is easy: go to configuration, and press: "Add IPC". Choose Type (IPC, NVR, ... ) at right hand, entering IP address, port numbers, user and password. Easy peasy. But also here, after 6 characters, the keyboard seems to get stuck. As my NVR password is 12 characters long... No success here. In some thread, I've seen people having issues with VTO and no sound when passwords are longer than 6 characters. Maybe this thing is linked to the same configuration bug.
CHAPTER 8: Conclusion & wrap-up
So summing up my experience till today:
POSITIVE:
- great design!
- solid manufacturing!
- VTNS switch can potentially built in in electricity closets
- separate UTP network for the intercom kit
NEGATIVE:
- password troubles: setting it in VDPConfig is no go
- password troubles: no longer than 6 chars for adding an IPC/NVR (to be investigated more)
- VTH1550 does NOT have a Webservices GUI
- different versions of VTH devices (leading to tons of different default passwords)
- i/gDMSS bugs bugs bugs.
))
. Yesterday I tried to connect a IPC HFW1320S to my VTO and VTH but only 6 characters are allowed, but the IPC requires at minimum 8 characters..
