only Hikvision resellers/partners, they need to create the ticket with Hikvision
Hikvision releases a fix/custom firmware, if it works/tested, then they will release it later in newer firmware official
2.2.3
only Hikvision resellers/partners, they need to create the ticket with Hikvision
Hikvision releases a fix/custom firmware, if it works/tested, then they will release it later in newer firmware official
2.2.3
ok but how can I have the same firmware youāre using? can you share it?
i dont have the custom yet , but the official ones, you can just download here;
the only thing not working right now is the Callstatus, the command for open door works
http://www.hikvisioneurope.com/uk/portal/?dir=portal/Product%20Firmware/Hikvision/Access%20Control%20%26%20Video%20Intercom/Video%20Intercom/Second%20Generation%20Video%20Intercom/Security2.0
edit: pay attention, if you upload from a verry old to new firmware, its then you need todo a factory reset, so you need to setup everything again , its written in firmware release notes too ā¦
Hi, could you post any pictures/schematics/information of how youāve attached this please? Iām thinking of also attaching an ESP to my Hikvision intercom so I can capture the button press without triggering the Hikvisionās automatic call to HikConnect.
hey ; its just 2 cables
from intercom the NO1/COM or NO2/COM , i have the 9310 as intercom, it has 2 output relays
on the ESP, just use an random input pin and the GND
thats all
binary_sensor:
- platform: gpio
pin:
number: D6
mode: INPUT_PULLUP
inverted: True
name: Doorbell
but if you have a 8113 or other model, then you dont need an esp, you can do a ISAPI call to get the callstatus, so no extra hardware neededā¦ 8003 doesnt work yet
Thanks,
I have the KV6113 so unfortunately it looks like the ISAPI wouldnāt work. The KV6113 has a relay, but that seems to be for door control so I donāt think itās triggered on pressing the call button?
ESP / relay solution is applicable to indoor stations, not to the KV6113
If you have an indoor station like DS-KH6320 or DS-KH9310, you can check the wiring scheme on the below doc
https://www.use-ip.co.uk/datasheets/HikvisionDS-KH6320-WTE1InstallationGuide.pdf
I have 1 generation Video Intercom. In this i can setu time for relay only the same for one and second relay. Tell meā¦ In second generation Video Intercom yopu can setup each time for first relay and each time for second relay ?
yes, i can define times for each relay
Is there anyone from Italy in this thread using indoor stations DS-KH8350-ā¦ or DS-KH6320-ā¦ or DS KH8520-ā¦?
Iām having wrong Italian translations using latest firmware 2.1.10
Iām using the DS-KH6320-WTE1 with the same firmware, there are only a couple of menu items in german, the rest is fully Italian.
Not a real issue in my case
Thanks, same here. Not a big deal, just checking if others were having the same issue.
i see in rls notes from 8003 that there are some translations fixes, maybe too for other devices
Any idea why I canāt open the door using:
curl -i --digest -u admin:xxxxxx -X PUT -d "<RemoteControlDoor><cmd>open</cmd></RemoteControlDoor>" http://192.168.1.xxx/ISAPI/AccessControl/RemoteControl/door/1
Iām able to get capabilities and event status but on the door open call I get
HTTP/1.1 401 Unauthorized
Date: Thu, 25 Mar 2021 18:23:40 GMT
Server: webs
Content-Length: 235
Connection: close
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store
Pragma: no-cache
WWW-Authenticate: Digest qop="auth", realm="DS-2BAFC16B", nonce="NWZkZGM4NzBkNGViYzRiMzQ2ZmI3ZWJiNWY0YmRkYzk=", stale="false", opaque="", domain="::"
Content-Type: application/xml
HTTP/1.1 400 Bad Request
Date: Thu, 25 Mar 2021 18:23:40 GMT
Server: webs
Content-Length: 40
Connection: close
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store
Pragma: no-cache
Content-Type: application/xml
Iām using firmware 2.2.13 build 210129
What does
curl --digest -u admin:xxx http://192.168.x.x/ISAPI/VideoIntercom/capabilities
return?
Maybe your firmware doesnāt support it?!
<isSupportRemoteOpenDoor>true</isSupportRemoteOpenDoor>
should be true!
<?xml version="1.0" encoding="UTF-8"?>
<VideoIntercomCap version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<isSupportDeviceId>true</isSupportDeviceId>
<isSupportOperationTime>true</isSupportOperationTime>
<isSupportRemoteOpenDoor>true</isSupportRemoteOpenDoor>
<isSupportKeyCfg>true</isSupportKeyCfg>
<isSupportAlarmUploadCfg>true</isSupportAlarmUploadCfg>
<isSupportSendCardCfg>true</isSupportSendCardCfg>
<isSupportCardSectorCheck>true</isSupportCardSectorCheck>
<isSupportDeviceLanguageCfg>true</isSupportDeviceLanguageCfg>
<isSupportAlarmControlByPhone>false</isSupportAlarmControlByPhone>
<isSupportWorkStatus>true</isSupportWorkStatus>
<isSupportSystemSwitchCfg>true</isSupportSystemSwitchCfg>
<isSupportPrivilegePassword>true</isSupportPrivilegePassword>
<isSupportPrivilegePasswordStatus>true</isSupportPrivilegePasswordStatus>
<isSupportSubModules>true</isSupportSubModules>
<isSupportCallCfg>true</isSupportCallCfg>
<isSupportRingBackTone>true</isSupportRingBackTone>
<isSupportPhoneCfg>true</isSupportPhoneCfg>
<isSupportElevatorControlCfg>true</isSupportElevatorControlCfg>
<isSupportSecurityMode>true</isSupportSecurityMode>
<isSupportDeviceCommunication>true</isSupportDeviceCommunication>
<isSupportKeyCfgPlanTemplate>true</isSupportKeyCfgPlanTemplate>
</VideoIntercomCap>
should work, are you trying the curl from SSH or from windows? i noticed a difference too with authentication, on windows, the digest didnt work
Hi guys,
anyone got this working with a DS-KV8202?
Iām on V1.5.1, it seems to refuse all the HTTP connections.
Thanks