quick question, do you have an indoor station ?
For Linux, the second command doesnât work with my 6113, but if I change it to this, it works:
curl -i --digest -u admin:xxxx -d '{"CallSignal":{"cmdType":"hangUp"}}' -H "Content-Type: application/json" -X PUT http://192.168.64.99/ISAPI/VideoIntercom/callSignal?format=json
Hi, thnx for feedback , but it seems its only supported in 6113 atm , the command still fals
btw, do you have an indoor station?
I do have an indoor station.
hey @jpet @giangi
you guys have the 8003 , right?
Iâm finally getting a 200 message with command below!!! but i need to figure out the correct payload, there is a devindex and callnr and sessionid that needs changingâŚ
curl -i --digest -u admin:xxx -d "PAYLOAD" -H "Content-Type: application/json" -X PUT http://192.168.0.70/ISAPI/VideoIntercom/callSignal?format=json
use this PAYLOAD:
{
"CallSignal": {
"cmdType": "hangUp",
"sessionId": "test",
"src": {
"periodNumber": 1,
"buildingNumber": 1,
"unitNumber": 1,
"floorNumber": 1,
"roomNumber": 1,
"devIndex": 1,
"communityNumber": "test",
"callNumber": "12312312311",
"unitType": "villa"
},
"target": {
"periodNumber": 1,
"buildingNumber": 1,
"unitNumber": 1,
"floorNumber": 1,
"roomNumber": 1,
"devIndex": 1,
"communityNumber": "test",
"callNumber": "12312312311",
"unitType": "indoor"
}
}
}
@pergola.fabio Hereâs the nodered module output for the hangUp command. I tried all three cases, ringing, on call and no call in progress.
"hikvisionUltimateDoorbell: Error hangUp clientGenericRequest.fetch error:Error response: Bad Request"
(and btw, if you select import, top right in the nodered interface, you can paste in the string in the hikvision ultimate documentation to get a complete example of the commands)
yes, indeed, i tried too , the payload for our 8003 is different, see my post above, that json payload works, we need more info in that json then 6113 owners
that nodered is built for 6113 devices, not 8113 or 8003
not working for me, on KV6113 with firmware V2.1.5.
It says âsuccessfully injected: hang upâ but it still ringing
good catch with the json @pergola.fabio. this is the smallest payload that still returns 200 OK but doesnât work for me (keeps ringing)
{"CallSignal":{"cmdType":"hangUp","src":{"periodNumber":1,"buildingNumber":1,"unitNumber":1,"floorNumber":1,"roomNumber":0}}}
yeah, dont understand either
but i think the hangUp is wrong
iâm now using the cloud commands trough hikconnect, that works
but hangUp doesnt work either there
hangUp only works if you first send an âanswerâ command , otherwise there is nothing to hangup
reject/cancel as cloud command works for me
have you tried first use the âanswerâ and then hangup?
or ârejectâ or answer?
one of these :
[ârequestâ, âcancelâ, âanswerâ, ârejectâ, âbellTimeoutâ, âhangUpâ, âdeviceOnCallâ]
and are you also sure about the roomNumber? because in the json i supplied there is a source and a target
maybe the source = 0 , and target = 1 ?
because if i look in IVMS, my indoor station is roomNumber 1
No, just the outdoor unit
Iâm running the latest firmware. Do you have model (B)?
Model: DS-KV6113-WPE1(B)
Firmware: V2.2.53
yes, maybe the command only succeeds when there is only an outdoor station
I think we need a different payload when there is also an indoor station involved⌠because in the payload we are now sending, there is a source and a target defined , we now atleast get a 200 response, but we need to find the correct combination
do you have an indoor? and revision B ?
No, DS-KV6113-WPE1, without B
No, DS-KV6113-WPE1, without B.
I have only the outdoor unit.
what response do you get with the curl?
Just 200 OK
both commands?
try to play with the payload
{"CallSignal":{"cmdType":"hangUp","src":{"periodNumber":1,"buildingNumber":1,"unitNumber":1,"floorNumber":1,"roomNumber":0}}}
maybe play with roomnr
also with : hangUp / cancel / reject
i think hangUp only works, when the call has been answered, maybe you need reject or cancel?
on my case ds-kd8003 , i dont have it working yet , wife is getting annoyed here from all the testing :s