No change for call status for DS KV9503, have to poll it manually even after the last fw update.
That’s too bad 
Not all devices are creating those kind of events…
I’ve installed the Home Assistant Add-on: Hikvision Doorbell successfully 
and all besides the ringing function works great. I’m able to unlock the door and get a video stream to HA
I don’t have an indoor station or a SIP Server set up because I was reading that with the add-on there is “no need to setup complex SIP”
Where can I find instruction on how to configure my DS-KD8003 to call home assistant and see that the call state changes from Idel to Ringing?
An indoor for DS-KD8003 is mandatory to see the call status changing … if you dont have an indoor, you need to setup a SIP server like asterisk, you need to call something to get a ring event…
thank you @pergola.fabio, I appreciate the quick reply. Got it.
Where can I learn regarding a recommended SIP add-on and how to configure the DS-KD8003 to dial the SIP Server?
Well, there is an asterisk addon, it’s actually pre configured, so you can call a Lovelace card…, the only thing todo is the setup your device to asterisk …
But remember, it’s not a full proof solution, if your card is not active/registered, it doesn’t receive the call, and you get calling failed, but they are working on a new card , so it’s HA that’s registering and not the lovelaca card … that makes the call is always working , it’s on beta
thank you @pergola.fabio, I’ve set up the add-on and card. Any tips on how to configure the DS-KD8003 SIP settings to make sure it dials the server / I hope I’m doing it correctly?
That’s not correct, you setup your Doorstation as 100 and you call 100, that doesn’t work
100 is your lovelaca card, so calling 100 is correct, but you need to create an custom extension like 6001, using pjsip extension on port 5060… In the wiki there is an guide how to create extensions, then you call from example 6001 to 100
Hello,
I am trying to use the Hikvision Doorbell add-on with an Abus TVHS20001S system. The Abus system is identical to the Hikvision DS-KD8003.
I have set up the add-on with an external MQTT broker, and according to the protocol it seems to work fine.
Documentation:
‘After you have setup an MQTT broker, you can start Hikvision Doorbell. Each of you defined doorbell should be visible as a device under Settings → Devices & Services → Devices.’
Unfortunately I can’t find any devices or entities. I’m just familiarising myself with HomeAssitant, so maybe it’s a stupid question. I would be grateful for any help.
following the wiki, I’ve set up the Asterisk add-on, card and integration with the following configuration:
ami_password: <password>
auto_add: true
auto_add_secret: <password>
video_support: false
generate_ssl_cert: false
certfile: fullchain.pem
keyfile: privkey.pem
additional_sounds: []
mailbox: false
mailbox_port: 12345
mailbox_password: <password>
mailbox_extension: "100"
mailbox_google_api_key: ""
log_level: info
however I’m getting the following errors/warnings suspecting I have setup something incorrectly because I’m unable to connect the integration or register with the DS-JD8003 intercom
[Nov 22 14:07:59] WARNING[507]: config.c:2130 process_text_line: parse error: No category context for line 310 of /etc/asterisk/geolocation.conf
[Nov 22 14:07:59] ERROR[507]: res_sorcery_config.c:334 sorcery_config_internal_load: Contents of config file 'geolocation.conf' are invalid and cannot be parsed
[Nov 22 14:07:59] WARNING[507]: config.c:2130 process_text_line: parse error: No category context for line 310 of /etc/asterisk/geolocation.conf
[Nov 22 14:07:59] ERROR[507]: res_sorcery_config.c:334 sorcery_config_internal_load: Contents of config file 'geolocation.conf' are invalid and cannot
Nov 22 14:08:00] WARNING[507]: res_phoneprov.c:1249 get_defaults: Unable to find a valid server address or name.
[Nov 22 14:08:00] NOTICE[507]: res_smdi.c:1424 load_module: No SMDI interfaces are available to listen on, not starting SMDI listener.
[Nov 22 14:08:00] ERROR[507]: netsock2.c:96 ast_sockaddr_stringify_fmt: getnameinfo(): ai_family not supported
[Nov 22 14:08:00] ERROR[507]: ari/config.c:312 process_config: No configured users for ARI
When I try to connect the integration, I monitor the follow in the log:
[Nov 22 14:08:00] Asterisk Ready.
[Nov 22 14:18:31] NOTICE[617]: acl.c:784 ast_apply_acl_internal: Manager User ACL: Rejecting '10.0.1.150' due to a failure to pass ACL '(BASELINE)'
[Nov 22 14:18:31] NOTICE[617]: manager.c:3756 authenticate: 10.0.1.150 failed to pass IP ACL as 'admin'
[Nov 22 14:18:31] NOTICE[617]: manager.c:3790 authenticate: 10.0.1.150 failed to authenticate as 'admin'
[Nov 22 14:18:32] == Connect attempt from '10.0.1.150' unable to authenticate
Hmm, maybe your ACL is incorrect? You are maybe blocking the request?
not sure how to proceed… what do you mean by blocking / incorrect ACL?
any suggestion on what to check?
there is an ACL file in your asterisk folder, probably you need to configure it too
but uts best to join the discord channel, i dont use asterisk anymore, maybe some people can help your there … i want to keep this thread for hikvision, not asterisk/sip talk
1 Like
will do. tnx
Unfortunately not. It is possible that the add-on does not work with the Abus system either, but I cannot find any errors in the log.
The connection to the MQTT broker works and I can see in the log that the doorbell was rung, for example.
you can check with mqtt explorer, should be there, otherwhise addon doesnt start