I try everything, but still I can’t get the event to HA when pushing DS-KV6113 ring button. Only voice calling failed
I enable DEBUG mode and get only event when I press the security button on the other side.
2023-04-04 19:57:06.592][DBG] Alarm chan [0] recv timeout[2]!
2023-04-04 19:57:21.826 | DEBUG | event:_handle_callback:192 - Callback invoked from SDK
[2023-04-04 19:57:21.826][INF] Alarm[0] IP[10.10.1.178] data_len[568] alarm_len[568] status[430]
2023-04-04 19:57:21.830 | DEBUG | event:_invoke_handlers:166 - Invoking 2 handlers
2023-04-04 19:57:21.832 | INFO | mqtt:video_intercom_alarm:266 - Video intercom alarm TAMPERING_ALARM detected on Gate door bell
2023-04-04 19:57:21.833 | DEBUG | mqtt:handle_device_trigger:305 - Invoking device trigger {'name': 'tampering_alarm', 'type': 'alarm', 'subtype': 'tampering'}
2023-04-04 19:57:21.835 | INFO | event:video_intercom_alarm:109 - Video intercom alarm from Gate door bell
If you have calling failed, then there is something wrong with your Hikvision itself, not related to this addon…
Isn’t your Indoor station ringing? Or Hikconnect if running standalone?
Finally I found problem. Got from support DS-KV6113-WPE1(C) new Firmware and upgraded from V2.2.55 to V2.2.57.
1 Like
So what is ringing now? Hikconnect?
VCTGomes
April 6, 2023, 2:18am
328
So good news! And the call stop ringing when you answer it over webrtc?
Isapi doesn’t answer, you still need Todo that manually with reject/answer command, then start stream
1 Like
si458
April 11, 2023, 8:17am
330
is it normal to see hundreds of alarm chan [0] recv timeout[2]!
[2023-04-11 09:10:32.055][DBG] Alarm chan [0] recv timeout[2]!
[2023-04-11 09:11:07.103][DBG] Alarm chan [0] recv timeout[2]!
[2023-04-11 09:11:37.144][DBG] Alarm chan [0] recv timeout[2]!
[2023-04-11 09:12:07.166][DBG] Alarm chan [0] recv timeout[2]!
[2023-04-11 09:12:37.208][DBG] Alarm chan [0] recv timeout[2]!
[2023-04-11 09:13:02.232][DBG] Alarm chan [0] recv timeout[2]!
[2023-04-11 09:13:32.257][DBG] Alarm chan [0] recv timeout[2]!
[2023-04-11 09:14:02.292][DBG] Alarm chan [0] recv timeout[2]!
[2023-04-11 09:14:32.329][DBG] Alarm chan [0] recv timeout[2]!
[2023-04-11 09:15:02.360][DBG] Alarm chan [0] recv timeout[2]!
[2023-04-11 09:15:32.400][DBG] Alarm chan [0] recv timeout[2]!
[2023-04-11 09:16:07.438][DBG] Alarm chan [0] recv timeout[2]!
They are normal, it’s a listener, just turn off debug, if you don’t want to see it
1 Like
si458
April 11, 2023, 8:29am
332
i have turned off debug thats the problem?
log_level: INFO
sdk_log_level: INFO
Define “NONE” for SDK log level
2 Likes
si458
April 11, 2023, 8:40am
334
thanks, that worked a treat!
Indeed, will have a look into it
si458
April 11, 2023, 8:43am
336
also is the any chance of opensourcing up the docker image? would love to read the code on how it all works! dev branch haha
1 Like
VCTGomes
April 11, 2023, 9:47pm
337
Hi Fabio, what does it mean on Log?
2023-04-11 18:34:18.335 | INFO | event:video_intercom_alarm:109 - Video intercom alarm from doorbell
Hmm, not sure, probably some unknown event, are you running latest beta?
Also, when do you see it? And is it from indoor or outdoor?
1 Like
VCTGomes
April 13, 2023, 4:39pm
339
Yep. I’m on the last beta. I’m using only outdoor unit. I don’t know well what event did it.
hoicj
April 14, 2023, 6:27pm
340
@pergola.fabio n the new addon it is impossible to get the id of the key that opened the door?
this is a super cool feature
1 Like
It should be there already , there is an unlock log
hoicj
April 14, 2023, 8:39pm
342
yes, I saw that the key is in the logs, but in the previous version the key was in the sensor attributes (sensor.hikvision_door). From there, I could get the ID and compare it with the database, which would then send the key name to telegram. Can I do something similar in the new integration?
1 Like
VCTGomes
April 15, 2023, 3:43am
343
Hey Fabio, could you implement the {"CallSignal":{"cmdType":"hangUp"}} command to make the doorbell stops the call?
hangUp also seems better than Reject because it doesn’t says the non-available answer on doorbell too.
