can you also test the call status? so you can get the event when someone presses the doorbell?
that doesnt work yet on 8003 , new firmware is coming to fix that
Yes, call status work correctly.
curl -i --digest -u admin:xxx http://192.168.x.x/ISAPI/VideoIntercom/callStatus?format=json
HTTP/1.1 401 Unauthorized
Date: Thu, 04 Mar 2021 15:22:38 GMT
Server: webs
Content-Length: 0
Connection: close
X-Frame-Options: SAMEORIGIN
Pragma: no-cache
Cache-Control: no-cache
WWW-Authenticate: Digest qop="auth", realm="DS-69A1EF7E", nonce="YTE1N2E4MGZmMjgzYThhMDc3NWU0NDk2MWZiNzYwMGM=", stale="false", opaque="", domain="::"
Content-Type: application/json
HTTP/1.1 200 OK
Date: Thu, 04 Mar 2021 15:22:38 GMT
Server: webs
Content-Length: 42
Connection: close
X-Frame-Options: SAMEORIGIN
Pragma: no-cache
Cache-Control: no-cache
Content-Type: application/json
{
"CallStatus": {
"status": "idle"
}
}
1 Like
can you also test when you actuall press the doorbutton? the issue wit 8003 is that it stays idle, the status doesnt change
Yes Fabio. I confirm that the status has changed correctly
perfect 
, now you can make automations/notifications when someone pressed the doorbutton
Fabio
just to let you know on KV8113 there are a couple of RTSP streams available
It seems main stream can be reached in several ways
Main stream 1920x1080p 25fps, 2Mbps
rtsp://user:[email protected]:554/Streaming/Channels/101
Sub Stream 704x576p, 25fps, 512Kbps,
rtsp://user:[email protected]:554/Streaming/Channels/102
sub stream is lighter and might be better in terms of performance for external motion detection platforms (Motion or Zoneminder)
Ok, I’ll update threadstart later
Hi to all,
continue the search for events for this product
With command:
curl --digest -u admin:xxx http://192.168.x.x/ISAPI/System/IO/inputs
I receive the list of input
<?xml version="1.0" encoding="UTF-8"?>
<IOInputPortList version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<IOInputPort version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<id min="1" max="4">1</id>
<name>AI1</name>
<IOUseType>doorStatus</IOUseType>
</IOInputPort>
<IOInputPort version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<id min="1" max="4">2</id>
<name>AI2</name>
<IOUseType>doorStatus</IOUseType>
</IOInputPort>
<IOInputPort version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<id min="1" max="4">3</id>
<name>AI3</name>
<IOUseType>openDoor</IOUseType>
</IOInputPort>
<IOInputPort version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<id min="1" max="4">4</id>
<name>AI4</name>
<IOUseType>disable</IOUseType>
</IOInputPort>
</IOInputPortList>
I would like to read the status of a magnet connected to input 1 but the command
curl --digest -u admin:xxx http://192.168.x.x/ISAPI/System/IO/inputs/1/trigger
don’t return any result.
Any suggestions?
You want to know if the door opened?
Yes Fabio. I connected a magnetic sensor to the mailbox, so i know if there is any mail 
to the mailbox? i though you had a doorbell
anyway, i try out this commands later on my doorbell too
@pergola.fabio How do you know that a new firmware for the 8003 is coming soon?
Can you post a link?
i reported this bug to service desk, they said it will be fixed in new firmware coming probably Q2
including also SIP fixes, i am ready running a beta release for SIP testing
Yes Fabio.
curl --digest -u admin:xxx http://192.168.x.x/ISAPI/System/IO/inputs/1/status
but it return only this
<?xml version="1.0" encoding="UTF-8"?>
i have bad url format
but i need to check later, i have some new ISAPI documents, those are old commands
i did to the partner where i purchased from, they created a ticket for me
indeed, hikvision doesnt support direct customers
1 Like
Lucky you! My partner does not do that…
Can I use you to report issues I found, either on my outdoor station (DS-KD8003-IME1) and indoor station (DS-KH8350-WTE1) ? 
And hopefully get a new firmware version fixing them?