[SOLVED] Need some help adding a Dahua DH-VTO2201F Doorbell video camera to BlueIris

A

Airbag888

n3wb
Sep 20, 2021
17
11
Mauritius
Hi Guys,

I've been trying to add this camera for the better part of the past week (on and off) without success..
I put in the credentials + IP in BlueIris, have it do the scan/inspect and it comes up with a mainstream/substream path but all I get is socket error 10054...
I should add it's connected successfully to a VTH monitor in the house
I'm putting some screenshots that may help understand the current config .. would be grateful for some assistance :)


DH-VTO2201F config:

1659972695097.png

VTH config only mentions VTO Ip address and username/password

BI captures (sorry done with the phone)

1659973014842.png

1659973105656.png

The output from the free Onvif discovery tool:
1659973221245.png
 
Last edited:
Redacting you actual internet address and MAC address is a good idea. Your local LAN addresses are meaningless and are used by everyone so there is no need to redact them at all, and they can provide some clues to your problem. The VTO needs to be on the same subnet as your BI computer for BI to be able to find it so knowing those two addresses is critical. It would also help to have a basic sketch of your network layout, showing router, switches, BI machine and VTO locations on it.
 
Last edited:
  • Like
Reactions: TonyR
sebastiantombs said:
Redacting you actual internet address and MAC address is a good idea. Your local LAN addresses are meaningless and are used by everyone so there is no need to redact them at all, and they can provide some clues to your problem. The VTO needs to be on the same subnet as your BI computer for BI to be able to find it so knowing those two addresses is critical. It would also help to have a basic sketch of your network layout, showing router, switches, BI machine and VTO locations on it.
Click to expand...
Alright, I thought so but also saw a lot others redact local IPs

Basically all are on the 192.168.0.0 network. VTO is 0.200, BI is 0.251, VTH is 0.197
Everything is under the same vlan, same switch basically.
I can ping the VTO from the BI machine and BI actually finds something when doing the 'inspect/scan'

So
Router (192.168.0.1)
|
|
POE Switch ------BI (192.168.0.251)
|\
| \_VTH (192.168.0.197)
VTO (192.168.0.200)

All cat6, all can talk to each other
 
Here's what mine shows after a find/inspect and is configured.

VTO video settings.JPG
 
It's on a segregated LAN, second NIC. There are two daisy chained, 16 port, PoE switches handling all the cameras.

Are you seeing video when in the GUI of the VTO?
 
sebastiantombs said:
It's on a segregated LAN, second NIC. There are two daisy chained, 16 port, PoE switches handling all the cameras.

Are you seeing video when in the GUI of the VTO?
Click to expand...
Yes I have a video feed

On the VTO network tab are you using transmission mode 1 or 2? Are you able to open the RTSP feed on VLC for example too?

1659988124113.png
 
I'm using mode 2 on the TCP/IP settings. I haven't bothered with VLC, using BI exclusively since the cameras are segregated to a totally different and unreachable IP scheme from the regular LAN.
 
Just for laughs, I went in and tried VLC and it streams fine to VLC as well.
 
do you have any skills using Wireshark program?
and who gives you that socket error? Blue Iris or the camera?
 
where did you buy the VTO & VTH?
I am using a 4.50000 firmware. You have 4.511.19...
if all else fails, could go backwards on firmware.
 
This is what my VTO2202F-P is running -

VTO firmware version.JPG
 
  • Like
Reactions: Airbag888
Holbs said:
where did you buy the VTO & VTH?
I am using a 4.50000 firmware. You have 4.511.19...
if all else fails, could go backwards on firmware.
Click to expand...
Thanks for your input.. I could try wireshark with some guidance.

As for the buyer, it was a link I got on a youtube video (I found it around here) but then had to settle for another seller as the original one did not ship to my country.. My firmware version apparently is the latest but of course latest isn't always greatest
I'm a bit weary of bricking the unit though as outside of BI it's working perfectly with the VTH at present.. I was hoping it was an oversight in config on my part..
Any other software I can use other than BI or VLC to try and connect to the VTO's RTSP
 
So I found out what the issue was... major facepalm moment incoming..

Screenshot below for clarity

1660034978886.png

So yes, RTSP over TLS was enabled.. (I can't remember if this was on by default or if I enabled it at some point) That's all it took

I hope this helps someone down the line.
Not sure if a thread can be marked as solved or if I can just update the title with a [SOLVED] prefix

Again thank you everyone involved :)


Next Up on my todo:
1. Connecting my 5 Atom cameras (similar hardware to Wyze) over RTSP :D
2. Beginning to use facial recognition solutions
3. Upgrading my hardware (believe it or not I got 9 cams (7x 8Mpx + 1x 4Mpx + 2Mpx Doorbell) running on a J1900 miniPC sipping 10W at peak load with CPU at 50% - of course substream only
 
  • Like
Reactions: CanCuba, sebastiantombs and Holbs
You must log in or register to reply here.
Top Bottom