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
When using manual control of the gate
Open
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
Hello,
This integration is more technical then others, you should implement all this sensors in yaml configuration, here the example of lock, here the example of doorbell ring.
Hello,
You can cancel VTO call and it’s stops ringing all VTH’s. I use it to stop ring when door was opening, before this I will need to press end call on VTH.
# Cancel VTO Call
service: dahua_vto.send_command
data:
entity_id: sensor.dahua_vto
method: console.runCmd
params: {'command': 'hc'}
event: false
Do you know if stoping the ringing also prevents the “The person you are trying to reach is unavailable” voice message on the door station?
I was able to mute / change all the sounds of the door station except this one and it is really annoying…
I don’t remember this voice message, but maybe because I have this settings on VTO:
The “Voice Prompt Sound” is the only one I still have active because otherwise there is no sound when you press the doorbell button.
I disabled all others and even uploaded an empty sound for all available sound-types.
Even cancelling the call results in the voice prompt, the only way to prevent it is to take the call
I see, I disable “Voice Prompt Sound” because user hear the doorbell sound from VTH installed inside but close to the door.
If you have VHT, you can send ac command to accept the call (same way as hc command in example but you should define new instance of integration connected to VTH), here the list of commands from VHT.
Thank you for the information.
I dont have a VTH, only the VTO, as I am using my phone and in future maybe a wallpanel with HA in kiosk browser (using the SIP addon / integration).
Can this command be sent from HA as well?
If you will use SIP server for calls from VTO you should look for command to accept and cancel call of this SIP server, I think this will be possible but you need to check it with SIP addon/integration.
As much as I know the VTO has an internal SIP-Server which is used by default.
In Home Assistant I am only using the doorbell events to trigger notifications (with multiroom audio and phone notification with snaptshot).
So I am not (yet) using the SIP addon and was just wondering if it is possible to send accept / cancel call command using the dahua integration
Yes, you can send cancel call command to VTO, but VTO doesn’t have accept call command. If you will manage to connect your SIP client/addon to VTO internal SIP server you probably will be able to send accept call command to this client (accept call it’s a client command).
I am planning to use SIP integration but a while back, before I had my real installation, I tested it and never got it to work. I even had to reset my Dahua as I managed to completly destroy my config.
So I currently lack motivation to finaly try this out 
Anyways, thanks for the information, maybe I’ll try that SIP integration again and use it to fix this annoying message 