I see it’s connecting to 2 doorbells? You only have 1 right?
I have two. The main one which it is installed outside (Doorbell) and another one (Doorbell_2) I connected just to do tests with. I would like to try the RS485 interface to see whether connecting both devices through such port can do something.
However, the manual marks the doorbell RS485 port as RESERVED, and there is nothing related to such port in the web interface (it does in the fingerprint reader) so I guess the port is there for a future implementation. Same happens with the SD CARD slot for these doorbells. I guess you are aware that SD slot is there but you can do nothing with it.
Ah ok, and are you sure your HA instance can connect to the device? Is your HA in the same IP range as the doorbell?
Yes. All devices are in the same network/subnet.
And if you just configure 1 doorbell, does that work?
Or maybe try rebooting it? Maybe since you are connected to the webinterface, it only allows a limited connection?
Just tried and it happens the same:
2025-04-15 17:18:22.983 | INFO | __main__:main_loop:102 - Failed to connect to the device, retrying again in 15 seconds...
2025-04-15 17:18:26.793 | DEBUG | config:load_mqtt_config:129 - Loading MQTT configuration from supervisor
2025-04-15 17:18:26.794 | DEBUG | config:mqtt_config_from_supervisor:36 - Requesting MQTT service configuration to supervisor
2025-04-15 17:18:26.802 | INFO | sdk.utils:loadSDK:44 - Using OS: Linux with architecture: x86_64
loop[2] find 2 mac and 1 ip
2025-04-15 17:18:26.943 | INFO | doorbell:authenticate:84 - Connected to doorbell: Doorbell
2025-04-15 17:18:26.944 | ERROR | __main__:main_loop:100 - Error while logging into Lector_Huellas: Failed to connect to the device. The device is off-line, or connection timeout caused by network. Error code: 7
2025-04-15 17:18:26.944 | INFO | __main__:main_loop:102 - Failed to connect to the device, retrying again in 15 seconds...
2025-04-15 17:18:41.996 | INFO | sdk.utils:loadSDK:44 - Using OS: Linux with architecture: x86_64
2025-04-15 17:18:42.012 | INFO | doorbell:authenticate:84 - Connected to doorbell: Doorbell
2025-04-15 17:18:42.013 | ERROR | __main__:main_loop:100 - Error while logging into Lector_Huellas: Failed to connect to the device. The device is off-line, or connection timeout caused by network. Error code: 7
2025-04-15 17:18:42.013 | INFO | __main__:main_loop:102 - Failed to connect to the device, retrying again in 15 seconds...
Perhaps this specific device does not handle ISAPI commands like doorbells do?
The addon is using the SDK on port 8000, it’s not isapi… Is that port open on your device? Maybe it’s another port? Or maybe it doesn’t allow sdk
By the way, I can ping the doorbell from HASS Terminal:
➜ ~ ping 192.168.0.74
PING 192.168.0.74 (192.168.0.74): 56 data bytes
64 bytes from 192.168.0.74: seq=0 ttl=64 time=0.422 ms
64 bytes from 192.168.0.74: seq=1 ttl=64 time=0.593 ms
64 bytes from 192.168.0.74: seq=2 ttl=64 time=0.309 ms
64 bytes from 192.168.0.74: seq=3 ttl=64 time=0.430 ms
Check if port 8000 is used on your device, maybe there is no SDK for it
Ah , and connecting to 72 doesn’t work either?
It’s a device with 2 IP addresses?
No, no. .72 is the doorbell. I checked just to see what a working device responded to the port check. The reader is the .74.
Sorry, I don’t understand, the addon needs to connect to the doorbell, the .72 is an Hikvision device, right?
.72 is the doorbell, which it is been always working fine with the addon. Now, I am trying to connect the fingerprint reader to HASS as well (just trying to see I can log events with the addon). I just included its web admin credentials and IP to the addon config (the .74 one). The .71 is the indoor screen:
All devices are Hikvision’s.
But I understand that your addon is for doorbells only, so I cannot connect any other devices type to it, is this correct?
That’s correct:-)
Ok. I guess I will have to live with it or try to find a way to link the reader to the doorbell, and see whether I can log accesses through the doorbell. Thanks anyway for your time!
1 Like
Hello Fabio
I’ve installed the new version for the -B version
Now, Call State sensor is not working anymore, do you have any idea ?
Thanks
Call status changed to :
{
“CallStatus”: {
“status”: “ring”
}
}
when checking with ISAPI command
Are you using alarm input to check if ringing? If yes, then on this version there’s maybe no more alarm related to…
Yes indeed, the call event is gone on those new firmware, don’t know if it’s a bug or on purpose… best to contact Hikvision for it ?
hell gonna downgrade that shit asap 
But first I need to test one trick, in KD8003 we can setup second relay to be enabled when someone is calling, if it’s being detected by your plugin, I will use this state instead 
Alarms inputs are read, but all 4 physical AI are the same in MQTT?
Thanks