I hope its not a game over yet 
First I need to check if newer indoor stations are compatible with my doorbell DS-KB8112. It is quite a troublesome model where many things don’t even work as advertised.
I’m also thinking to dig a bit more into other SIP tools/opensips and see if it can inject RTP-streams
Yeah, my goal was indeed to manually inject video in the RTP , by converting for example the rtsp with ffmpeg, but seems I was alone on internet that wanted to do this, so I gave up and created the baresip approach and injecting the rtsp video as a conference user…
But I want to help getting this stuff to work!!
Opensips has some great tools to manipulate sip, I used that first to send the XML needed for Hikvision…
But later on, I was just wrong, it was not needed if I added the SN manually with ivms (new models)
The script approach is indeed for older models , basically doing the same thing as opensips
But didn’t find a way or didn’t searched hard enough to manipulate the RTP
Hi Fabio, many thnx again for your add-on to get my doorbell working (DS_KV6113) with HA !
Below you find my yaml tekst:
alias: deurbel aan
description: ""
trigger:
- platform: state
entity_id:
- sensor.hikvision_callstatus
condition: []
action:
- service: media_player.play_media
target:
entity_id: media_player.nesthub2692
data:
media_content_id: media-source://media_source/local/deurbel2.mp3
media_content_type: audio/mpeg
metadata:
title: deurbel2.mp3
thumbnail: null
media_class: music
children_media_class: null
navigateIds:
- {}
- media_content_type: app
media_content_id: media-source://media_source
- delay:
hours: 0
minutes: 0
seconds: 1
milliseconds: 0
- service: tts.google_translate_say
data:
entity_id: media_player.nesthub2692
message: Er staat iemand voor de deur
language: nl
cache: true
mode: single
One question I still have is how to integrate your callsignal service you noted in the starting point of this post. I see the lines to send the callsignal command to my outdoor station… But where do I have to put these lines ? Just into the configuration.yaml or in a separate file ? Do I have to save this as a service…I’m pretty lost here…hope you help me out here…still learning. I have a Zigbee sensor at the door that should trigger this callsignal command (same solution as you have)
By the way: I have just opened a Paypal account for some sponsoring for your appreciated work 
Hi, thnx for donation, I just received
What I do, I just put the service in a script, and I trigger the script from an automation of my door sensor
Actually it’s the same as you do with the call sensor, when it goes to “on” you just fire an service
Do you have an indoor station? Then in the addon put the Ip of your indoor station on the second IP option… If no indoor station, just setup the same IP again of your outdoor
FIY:
For the users (like me) that are using the ISAPI command : Doorpress event rest sensor using digest authentication (http://192.168.0.70/ISAPI/VideoIntercom/callStatus?format=json&channelType=tripartitePlatform`) this has stopped working with the versions 2023.x.x
There is already a issue open and you can find it here:
Hey, are you this user? You created this?
Hi Fabio,
Something like this:
alias: Deurbel drukker uit bij beweging in hal
description: ""
trigger:
- platform: state
entity_id:
- binary_sensor.tz3000_nss8amz9_ts0202_iaszone
condition: []
action:
- service: script.bel_uit
data: {}
mode: single
And the script “bel uit” should be like this:
alias: bel uit
sequence:
- service: hassio.addon_stdin
data:
addon: a53439b8-hikvision-sdk
input: reject
mode: single
icon: mdi:doorbell-video
Just a double check with you
correct!! or just include the service directly in the automation
the script is only usefull, if you want to trigger with another automation or switch or button or whatever, then for example if the addon name changes , you only need to modify it once
Nope. I’ve been too lazy to create a repo 
Didn’t realise someone already put in the effort to integrate it with mqtt. Would have saved me some time 
hehe, indeed
I would like ti step away too. I have HA running in a Synology Docker container. Is there any chance to use the Hikvision SDK for instance in another docker container?
Thanks.
Most likely have updated to version 2023.x.
Check here:
yes, someone else created a script based on mqtt , so no addon needed
I will give it try then! Hope that works with the DS-KV6113 and DS-KV8113.
make sure to create a docker based on debian or a supported OS , not the synology OS
A Raspberry PI should do the work. In would prefer to use the Synology but I understand the SDK doesn’t work on the architecture.
yes, it works now, i have received an internal SDK for testing, it works on Aarch64
Only works on EulerOS, look at my dockerfile
FROM openeuler/openeuler
grab from here
correct!! or just include the service directly in the automation. The script is only usefull, if you want to trigger with another automation or switch or button or whatever, then for example if the addon name changes , you only need to modify it once
Hi Fabio, sorry. I have integrated your callsignal service and the corresponding yaml was approved by you ;-), but it isn’t working.
After the doorbell button is pushed and the Google Nest is ringing nicely, the calling of the doorbell should stop when my Zigbee motion sensor nearby the door (binary_sensor.tz3000_nss8amz9_ts0202_iaszone) detect motion and call the service (script bel_uit).
So when some one opens the door the doorbell should stop calling.
Is it possible that it is not working because I use the Zigbee motion sensor also in an another automation (switching light on after sunset) ?
have you tried just the service to actually see if its working? you can test it in service developer tools
then ring the bell, and then send the reject command
my automation is like:
- alias: Deur open reject call
initial_state: 'on'
trigger:
- platform: state
entity_id: binary_sensor.openclose
from: 'off'
to: 'on'
action:
service: script.reject_call
with script:
reject_call:
alias: Deur open reject call
sequence:
- service: hassio.addon_stdin
data:
addon: aff2db71_hikvision_sdk
input: reject