Hi, this thread is all about the possibility to integrate commands in HA, Local commands, but i also now added commands for Cloud, based on HikConnect APP, see below
Confirmed devices : DS-KV8413, KD8003 and DS-KV8113 KV8213 DS-KV6113
What is working so far …
Video Stream rtsp:
rtsp://user:[email protected]:554/ch1/main/av_stream
rtsp://user:[email protected]:554/Streaming/Channels/101
rtsp://user:[email protected]:554/Streaming/Channels/102
rtsp:/user:[email protected]:554/cam1/h264
ISAPI command : Open a door / Relay
To open an electrical door (relay 1 or 2)
curl -i --digest -u admin:xxx -X PUT -d '<RemoteControlDoor><cmd>open</cmd></RemoteControlDoor>' http://192.168.0.xx/ISAPI/AccessControl/RemoteControl/door/1
ISAPI command : Doorpress event
To capture a doorpress event for 8003 owners : (custom firmware is needed)
curl -i --digest -u admin:xxxx http://192.168.0.70/ISAPI/VideoIntercom/callStatus?format=json&channelType=tripartitePlatform
for other models:
curl -i --digest -u admin:xxx http://192.168.x.x/ISAPI/VideoIntercom/callStatus?format=json
Should give as output : “idle” , “ring” , “onCall”
{
"CallStatus":{
"status": "idle"
}}
Based on :
Example Rest Sensor
- platform: rest
name: Doorbell Status
authentication: digest
username: admin
password: <password>
scan_interval: 1
resource: http://192.168.0.XXX/ISAPI/VideoIntercom/callStatus?format=json
value_template: "{{ value_json.CallStatus.status }}"
NEW STUFF : HikConnect integration
With Fiddler i made a trace from the HikConnect app, making below sensors possible with easy REST commands… below is confimed working on a DS-KD8003 , maybe the commands are different for other models, so can you guys test so i can maybe add it for other models too?
What i did… I installed Fiddler on my desktop PC for tracing my android. Make sure remote clients is enabled in fidler, also enable htts tracking and install the certificate on android too… Remember, tracing https doesnt work anymore for android 7.0 and newer and also IOS 11 for apple, so i started android on an emulator, i used LDPlayer V3 , thats using android 6.0
ok, when tracing is succesfull, you should see stuf like below screenshot :
based on that i created a Hikconnect login sensor, i am still playing with the scan_interval, i think it needs to be around a day, then the system does a logout , so the sessionid changes, needed for other commands… adapt below header info as seen your fiddler, also the payload is from the “Textview” tab Fiddler, copy pasted that long string
- platform: rest
name: hikconnect_login
scan_interval: 86400
resource: "https://apiieu.hik-connect.com/v3/users/login/v2"
headers:
customno: #Fiddler header
appChannel: "hikvision"
Content-Type: "application/x-www-form-urlencoded"
featureCode: #Fiddler header
lang: "en-US"
clientVersion: #Fiddler header
appId: "HikConnect"
sessionId: ""
clientType: #Fiddler header
clientNo: #Fiddler header
areaId: #Fiddler header
netType: "WIFI"
osVersion: #Fiddler header
method: POST
payload: account= #Fiddler Textview
value_template: "Hikconnect Login"
json_attributes:
- loginSession
Restart HA, and test if this is working? Now some fun stuf 
I created a sensor that gives the callhistory, you can change the pageSize from 1 to 15 to get more call history…
- platform: command_line
command: >
curl
--header "sessionId: {% if state_attr('sensor.hikconnect_login', 'loginSession') != None %}{{ state_attr('sensor.hikconnect_login', 'loginSession').sessionId }}{% endif %}"
"https://apiieu.hik-connect.com/v3/calling/listByUser?leastTime=&msgStatus=-1&pageSize=1"
name: hikconnect_last_calltime
scan_interval: 60
value_template: "Last Calltime"
json_attributes:
- data
The next sensor gives a callstatus, the callstatus changes offcourse when someone actually presses the doorbell or when you pickup … you need to change the serial of your device in the url, i had to use mine from my indoor panel…
- platform: command_line
command: >
curl
--header "sessionId: {% if state_attr('sensor.hikconnect_login', 'loginSession') != None %}{{ state_attr('sensor.hikconnect_login', 'loginSession').sessionId }}{% endif %}"
"https://apiieu.hik-connect.com/v3/devconfig/v1/call/XXXXXXXXX/status"
name: hikconnect_callstatus
scan_interval: 5
value_template: "Call Status"
json_attributes:
- data
The sjhell command below is to actually open the door, also change serial here
shell_command:
hikconnect_open_door: >
curl -X PUT
--header "sessionId: {{ state_attr('sensor.hikconnect_login', 'loginSession').sessionId }}"
"https://apiieu.hik-connect.com/v3/devconfig/v1/call/QXXXXXX/1/remote/unlock?srcId=1&lockId=0&userType=0"
## Variant based on ISAPI Cloud : curl -X POST --header "sessionId: {{ state_attr('sensor.hikconnect_login', 'loginSession').sessionId }}" --data "apiKey=100044&channelNo=1&deviceSerial=QXXXXXX&apiData=PUT /ISAPI/AccessControl/RemoteControl/door/1%0D%0A<RemoteControlDoor><cmd>open</cmd><channelNo>1</channelNo><controlType>monitor</controlType><password></password></RemoteControlDoor>" "https://apiieu.hik-connect.com/v3/userdevices/v1/isapi"
The sessionID , i think it expires after about 20-24 hours, so you set the scan interval of the hikconnect login to 10 hours, or use below automation , that checks for example if there is a callhistory, if no callhistory, it means the sensor failed, and it will execute the login sensor again
- alias: Hikconnect Relogin
initial_state: 'on'
trigger:
- platform: state
entity_id: sensor.hikconnect_last_calltime
condition:
- condition: template
value_template: >
{{not state_attr('sensor.hikconnect_last_calltime', 'data') }}
action:
- service: homeassistant.update_entity
entity_id: sensor.hikconnect_login