Error 10 is a timeout? Not sure why, is your HA on same subnet as the doorbell? Same IP range? Maybe try to reboot the device?
Hi, Sorry for my late reply.
I’ve been slow in testing cause I’m no expert to all this.
Having the beta running, the Caller info button goes disabled after first press.
I’ve also changed around some parameters in door station configuration to see if something would change.
As far as i can see, no matter what button i press, i get same result, in logs and in ivms.
Here’s the relevant app log
INFO | mqtt:video_intercom_alarm:454 - Doorbell ringing, button press from button: 10010100000, updating sensor
Do you want me to do some specific test?
No problem. No need to press caller info button within HA…
This nr you see in log, 10010100000, does it change when you call another indoor station with another button on your outdoor… Or is it always that same number?
@pergola.fabio, Ciao.
I had this add-on working for months, I have a new HAOS install. After install this add-on again, I get a ERROR.
2026-02-08 12:12:27.144 | ERROR | main:main_loop:100 - Error while logging into : Failed to connect to the device. The device is off-line, or connection timeout caused by network. Error code: 7
Im sure I have the right IP, User and Password. Port not filled in, but when using Port 8000, still same ERROR.
for some reason everything changed in the new HAOS, the fields etc in the add-on are different, but I think I have the same config like before.
Error 7 , device is offline? Maybe a network issue? 
The doorbell is online, I can log in on the webpage, on my phone and on my indoor station I see the doorbell as well.
Always the same, invariable upon wich of the 4 buttons is being pressed on the sole door statio I have. I have no indoor monitors, just ha.
This number seems to be floor/unit/building.
I have no rooms configured, should I? And where to?
Ah, that’s maybe why, no I need someone who has actually multiple indoor stations, with a dedicated button on the outdoor
1 Like
same subnet, not vlan (yet).
just rebooted few times
Just tried to ping the camera ip, that works:
root@pve:~# ping 192.168.20.30
PING 192.168.20.30 (192.168.20.30) 56(84) bytes of data.
64 bytes from 192.168.20.30: icmp_seq=1 ttl=63 time=0.681 ms
64 bytes from 192.168.20.30: icmp_seq=2 ttl=63 time=0.792 ms
64 bytes from 192.168.20.30: icmp_seq=3 ttl=63 time=0.667 ms
64 bytes from 192.168.20.30: icmp_seq=4 ttl=63 time=0.947 ms
64 bytes from 192.168.20.30: icmp_seq=5 ttl=63 time=0.702 ms
64 bytes from 192.168.20.30: icmp_seq=6 ttl=63 time=0.661 ms
64 bytes from 192.168.20.30: icmp_seq=7 ttl=63 time=1.47 ms
64 bytes from 192.168.20.30: icmp_seq=8 ttl=63 time=0.744 ms
64 bytes from 192.168.20.30: icmp_seq=9 ttl=63 time=0.894 ms
64 bytes from 192.168.20.30: icmp_seq=10 ttl=63 time=0.749 ms
^C
— 192.168.20.30 ping statistics —
10 packets transmitted, 10 received, 0% packet loss, time 9193ms
rtt min/avg/max/mdev = 0.661/0.830/1.472/0.232 ms
sorry, no id 
your HA is also on 192.168.20.x ?
No, it’s on 192.168.10. …
It always worked, I have the camera’s on there on subnet, but there is no firewall routing or something.
Unfortunately I didn’t quite get there yet. I can unmute my mic in the advanced camera card now and the sound starts to flow to the doorstation from my mobile phone. But I’m not getting any sound from the doorstation, even though the microphone LED on it signals that it is active when I pick up the call.
I tried setting up the doorbell as a generic camera in home assistant, that al works fine.
So the doorbell is not offline, so you have tips to debug it further?
hmm, not sure whats going on
Just tried the stand alone container, then I get the doorbell in mqtt > home assistant 
1 Like
Hi @pergola.fabio , thank you for providing this add-on!
I’m using a DS-KV9503 and an indoor villa station.
Currently I only receive incoming call events from the indoor villa station.
Can I support you to get the incoming call event from the doorbell DS-KV9503 itself?
Incoming evens on indoor? That normallybdoesnt work, you need to poll it manually…
The outdoor doesn’t provide a ring? Some doorstations do that indeed, there is a manually poll you can use , or press manually the call status button
Some more testing, I’ll try to summarize:
Outdoor station: KV8113-WME1(C)
Indoor station: just HA
I have the outdoor station set to call my HA and it indeed receives the event and the call status changes to “ringing” when I press the button on the outdoor station.
I can start the communication from HA to KV8113, but no the other way around (even though KV8113 does signal that its microphone is in use).
When I try to answer, hangup or reject the call on HA, I get
Error while answering call with ISAPI: ('Error while calling ISAPI /ISAPI/VideoIntercom/callSignal?format=json', 11, 'The data sent to the device is illegal, or the data received from the device error. E.g. The input data is not supported by the device for remote configuration.')
When I try to initiate TwoWayAudio via PUT /ISAPI/System/TwoWayAudio/channels/1/open I get
Error while invoking ISAPI endpoint: ('Error while calling ISAPI /ISAPI/System/TwoWayAudio/channels/1/open', 25, 'Failed to modify device parameters.')
@pergola.fabio a few questions that would help me get my head around this:
- Does this indicate that my scenario will not work without the indoor station?
- Does it make sense for me to try the SIP setup? I was checking the documentation there and it also seems to assume scenario with the indoor station.
- Is there any other way to get this to work without the indoor station?
- And if not, will a simple, screenless one such as KH6000 do the trick?
Thank you!
If somebody pushes the button on the doorbell (DS-KV9503) it doesn’t show up in the logs.
It only triggers an event from the indoor villa station:
2026-02-10 13:18:27.656 | INFO | event:isapi_alarm:131 - Isapi alarm from HikvisionIndoorStation
2026-02-10 13:45:34.412 | INFO | event:isapi_alarm:131 - Isapi alarm from HikvisionIndoorStation
Other events from the doorbell are collected, like these onces:
2026-02-10 17:17:21.158 | INFO | mqtt:video_intercom_event:404 - Video intercom event authentication_log detected on doorbell
2026-02-10 17:17:21.158 | INFO | mqtt:handle_device_trigger:530 - Invoking device trigger automation{'name': 'authentication_log', 'type': 'event', 'subtype': 'authentication log'}
2026-02-10 17:17:21.159 | INFO | event:video_intercom_event:109 - Video intercom event from doorbell
I’d like to create automations, like capturing a snapshot if somebody rings the bell.
Where can we get deeper into it to support the DS-KV9503 as well?