You can use example from readme and lock, the integration catch events from Dahua VTO so you will always get status even you unlock gate from DMSS or VTH.
1 Like
Maybe not exactly the right place to ask. Everything works. Integration. Events. The only thing is 2 way audio. When using DMSS i can hear the person but they can’t hear me. Somehow it worked for some time. I also have go2rtc/frigate connected to VTO via RTSP. Can this be an issue?
I was just reading the go2rtc docs for another use case. I seem to remember it saying that VTO only supports one audio feed to one endpoint at a time. So you cannot have a video stream (with audio) going through go2rtc, as well as feeding the audio through this integration. Maybe stop the go2rtc feed and re-check audio?
Read through that as well. But the sound from VTO is coming into the DMSS app. But not the other way round. But will try disconnecting VTO from all the feeds
Pardon my ignorance, very new to HA here. But how do I get my VTO2211 to show up as device on HA that I can interact with?
I have put in details inside my configuration.yaml from the first post, and also the locak example with call to open door service. I also save in the automation example.
This integration event based and doesn’t provide device interface into Home Assistant so if you are new to YAML you can try great rroller Dahua integration which is more user friendly because it’s setups from GUI and expose doorbell/sensors/command without any YAML templates.
Thank you. Will this other integration also expose the same features on my VTO2211?
is the dahuaVTO2MQTT method also similar, and provide the same features?
I think yes, maybe except this commands but I don’t think if you need them.
dahuaVTO2MQTT requires dedicated docker container when this and rroller integration it’s regular Home Assistant integrations.
Hi,
i have a problem with the configuartion.yaml senor Dahua VTO not working i recive this error:
- Invalid config for [template]: [host] is an invalid option for [template]. Check: template->sensor->0->host. (See /config/configuration.yaml, line 14).
- Invalid config for [template]: [platform] is an invalid option for [template]. Check: template->sensor->0->platform. (See /config/configuration.yaml, line 14).
template:
- sensor:
- platform: dahua_vto
name: Dahua VTO
host: 192.168.178.210
# timeout: TIMEOUT_HERE optional, default 10
# port: PORT_HERE optional, default 5000
username: username
password: pwd
scan_interval: 5
Any ideas
Thanks
Why you use template? Configuration should look like:
sensor:
- platform: dahua_vto
name: Dahua VTO
host: 192.168.178.210
# timeout: TIMEOUT_HERE optional, default 10
# port: PORT_HERE optional, default 5000
username: username
password: pwd
scan_interval: 5
Check this doc
can u help on which hardware u r running the FreePABX? I use Proxmox so have the option to run it in LCX or docker container or VM.
I am interested to know your yaml code.Also i see ur getting feed from frigate. which way are u using camera stream? ffmpeg or web rtc? i m intersted to know and learn how.
one issue i am facing is that i am able to hear voice from DMMS app to VTO speaker but when i speak on VTO , i dont hear anything on the DMMS , can u help hear?
I run free PBX as a VM in unRAID.
Just to share
The docs just give you basic backlight codes like door open and the formatting is hard to get hand on. So here is some investigation tested on VTO22xx
Like in the docs Status 8 generates just the door open event
- platform: event
event_type: dahua_event_received
event_data:
Code: BackKeyLight
Data:
State: 8
But if you want a more granular you can use a different approach
Door open via the exit button
- platform: event
event_type: dahua_event_received
event_data:
Code: AccessControl
Data:
Method: 5
Name: OpenDoor
Door open via RFID key
- platform: event
event_type: dahua_event_received
event_data:
Code: AccessControl
Data:
CardNo: XXX - This is where you put your key ID like 01X5575F (can be found in Dahua web interface or while listening for events on dahua in HA
Name: OpenDoor
I am lame on submitting pull requests so if someone can help feel free to use above
Was someone of you able to differentiate which button was pressed for installations with different buttons?
I am running a VTO2000 with different buttons. If i log the events if i press different buttons i am unfortunately not able to see any difference (see screenshot attached)
I pushed once the first button and later another button on the panel. I am running a SIP enabled firmware on the box and wan’t to execute different automations based on which button was pressed at the door panel.
I have a Dahua VTO 2202F. Firstly thanks very much for this integration, it is awesome. On a side note I also have Go2RTC configured with 2 way audio via the WebRTC card, which is also works well for Dahua VTO.
On my VTO I have it connected to ‘unlock’ a motorised gate, with a magnetic reed switch to detect open/close status. I send door unlock via dry contact from the VTO to control the gate. Gate status is generally detected correctly, except when I initiate the unlock from the VTO (rather than the using the gate remote or open/close manually).
When I unlock from VTO (using DMSS or this integration) I see the following:
VTO control
- Action: Pulse BackKeyLight: 8 (door unlock) 15:05:58
- Action: Pulse DoorStatus Relay: true Status: Close 15:05:59
- Action: Pulse DoorStatus Relay: true Status: Close 15:06:12
- Action: Pulse DoorStatus Status: Close 15:06:12
- Action: Stop Code: AlarmLocal 15:06:12
When using manual control of the gate
Open
- Action: Pulse DoorStatus Status: Open 15:31:59
- Action: Start Code: AlarmLocal 15:31:59
Close - DoorStatus: Relay: true Status: Close 15:32:34
- DoorStatus: Status: Close 15:32:34
- Action: Stop Code: AlarmLocal 15:32:34
It seems that the required unlock period of the VTO sends the closed status despite the condition of the reed switch. I’m using this as an open/close function while the VTO was designed for unlocking. Does anyone have a suggestion on how I can configure the VTO or somehow probe the status of the door status from the VTO?
Do you have something like VTO2000A-X? Looks like Invite messages doesn’t have any information which you can use to differentiate the buttons. In your setup users has VTHs or VTO call directly to users SIP soft phones?
With VTHs you can try to configure this integration for every VTH and detect buttons pressed by events from VTH.
Without VTHs you can try to get call notification directly from SIP Server using something like this.
Hope this helps.
Hi dice, how have you reached the goal of having 2way audio working?
I’ve tried every guide I found on internet but never worked.
Maybe you found something new. In my setup I’ve already frigate with custom go2rtc component so I’m very curious about getting it working.
Hi All.
I am new with this integration.
I have installed it from HACS and for some reason I don’t get the binary sensor entity of door unlock and door ring.
how can I add that?
Thanks.
hi guys, i’ve a vto3211 and 2 vth (1 2621 and 1 2421). There is a way with this integration to stop ring vth after f.e. 2/3 ring? setting has 15 seconds min to ring and it is too long.
Thanks