Hikvision Doorbell / Videointercom integration

[Manfred1]

Hi everyone,

I have a problem sending reject command to stop ringing. Please take a look here:

Hikvision Doorbell addon "reject" API function doesn't work on DS-KV8113-WME1(C)

Hi, I am using a Hikvision door station DS-KV8113-WME1(C) running firmware V2.2.78 and 3 Hikvision indoor stations DS-KH6320-WTE1 running firmware V2.2.100. 1 indoor station is configured as a main station connected to the door station and 2 indoor stations are extension stations connected to the main station. To integrate Hikvision devices into Home Assistant I use the Hikvision Doorbell addon version 3.0.22. [Screenshot 2025-06-10 003005] I tried to get following automation working to au…

[damiano1 (Damiano)]

Hi I have the same issue, I have a magnetic sensor and need access the status of AI1 to check if the door is open/close. What I can do? Thanks!

[damiano1 (Damiano)]

Hi Joao, did you find a solution? I need to access the status of AI1 too. Bye

[pergola.fabio]

i have looked into these before, but grabbing the status of the outputs on outdoor doesnt work on my outdoor panel, only indoor…

In my integration i added an ISAPI helper , you can send commands to it like:

PUT /ISAPI/SecurityCP/control/outputs/0?format=json {"OutputsCtrl":{"switch":"open"}}

POST /ISAPI/SecurityCP/status/outputStatus?format=json {"OutputCond":{"maxResults":2,"outputModuleNo":0,"searchID":"1","searchResultPosition":0}}

example:

action: text.set_value
target:
  entity_id:
    - text.ds_kd8003_isapi_request
    - text.ds_kh9510_isapi_request
data:
  value: >-
    POST /ISAPI/SecurityCP/status/outputStatus?format=json
    {"OutputCond":{"maxResults":2,"outputModuleNo":0,"searchID":"1","searchResultPosition":0}}

Make sure the entity is enabled (disabled by default), also enable debug in addon to see output, or look at the attributes of the entity

[pergola.fabio]

also found these, alltough the GET command doesnt display the state:

- GET /ISAPI/System/IO/capabilities
- GET /ISAPI/System/IO/outputs/1
- PUT /ISAPI/System/IO/outputs/<ID>/trigger <IOPortData><outputState>high</outputState></IOPortData>
- PUT /ISAPI/System/IO/outputs/<ID>/trigger <IOPortData><outputState>low</outputState></IOPortData>

or 'INPUTS' as equivalent

Maybe there is another command ? all info is in the attached isapi docs in first post …

[damiano1 (Damiano)]

Thanks Fabio, I’ll try your suggestions. However I haven’t an hikvision indoor panel , I only have a villa door station DS-KV8413-WME1. Are you saying your method doesn’t work in my case?

[pergola.fabio]

no idea, trial and error

[damiano1 (Damiano)]

If I understand, using for instance ```
“POST /ISAPI/SecurityCP/status/outputStatus?format=json {“OutputCond”:{“maxResults”:2,“outputModuleNo”:0,“searchID”:“1”,“searchResultPosition”:0}}”
if success, I should get in the attributes a result like the one I can see in your screenshot for kh_9510. Unfortunately I always get empty attributes using all the ISAPi commands you suggested. I suppose the Doorbell is not replying with any information…

[pergola.fabio]

Yeah, it doesn’t work either on my outdoor

[damiano1 (Damiano)]

No luck… I tried everything… Fabio, let me just understand: if I buy an Hikvison panel, like for instance DS-KH9510-WTE1(B) I’ll will able to read in HA the status of the AN1 input present on the Outdoor station through the panel? OT: Do you know if I can run Home assistant companion app on this panel?

[pergola.fabio]

my addon reads indeed the zone event, alltough it doesnt know the state, but if you define a zone like gas leak, and it open/closes, this will be an event indeed in the addon

also a01 / com01 can be openened from the addon

HA doesnt run on it, its way to slow android device

[damiano1 (Damiano)]

Thanks Fabio. You mean your addon reads the zone event only on the indoor panel, right? Anyway, thanks for your valuable work, I sent you a contribution a couple of days ago. Bye

[pergola.fabio]

yes, only zone events on indoor, i dont think the zone inports on outdoor actually work, never tried it , maybe …
i only use locks on the output relays on outdoor

[Joao-Sousa-71 (Joao Sousa)]

Yes I did. I was able to install the magnetic switch and iin fact an event is created every time the door is open. It is just an event without any Payload. as you can see here:

With this event it is posible to create a trigger sensor that will be something like this:

- trigger:
    - platform: mqtt
      topic: hmd/device_automation/bell_outdoor_101/door_not_closed_0/state        
  binary_sensor:
    - name: 'gate_door_exterior_status'
      unique_id: gate_door_exterior_status
      icon: mdi:door
      device_class: door      
      state: >
        true
      attributes:
        last_event: "{{ now().isoformat()}}"         

Now, there is a drawback since the event is only fired when the door is open, but unfortunately there is no other (new) event when the door is closed after.
Because of that I had to change the reed switch from a NO (normally open) to a NC (normally close ) and invert the behaviour. So, when the door is closed for the intercom is Open and that will allow a a new trigger since by open the door it will close the magnetic switch that will open again after close the phisical door and fire an new event. It is a bit tricky but it works very well…

Here is the sensor code:

# Sensor to check the real statos of the Outside Door Gate
- trigger:
    - platform: state
      entity_id: switch.sonoff_1000911d6f
      to:
        - 'on'
    - platform: state
      entity_id: switch.bell_outdoor_101_door_relay_0
      to:
        - 'on'
    - platform: mqtt
      topic: hmd/device_automation/bell_outdoor_101/door_not_closed_0/state        
  binary_sensor:
    - name: 'gate_door_exterior_status'
      unique_id: gate_door_exterior_status
      icon: mdi:door
      device_class: door      
      state: >
         {% if trigger.platform == 'state' %}
           {% if trigger.to_state.entity_id == 'switch.sonoff_1000911d6f' or trigger.to_state.entity_id == 'switch.bell_outdoor_101_door_relay_0' %}
             true
           {% endif %}  
         {% else %}
           false
         {% endif %}
      attributes:
        last_event: "{{ now().isoformat()}}"     

[iorifly (Renato Barbosa)]

Hello, how are you?

I’m trying to create an automation so that when my doorbell rings, I receive an image on Telegram. However, my sensor stays on “ringing” even though nothing is happening. When I ring it, after a while it goes back to IDLE, but then it shows “ringing”. What’s going on?

My model: DS-kv6113

my log

> 2025-06-13 21:58:53.033 | INFO     | event:video_intercom_event:109 - Video intercom event from Porteiro
> 2025-06-13 21:58:53.034 | INFO     | mqtt:update_door_entities:303 - Door 1 unlocked by 4856545650565554505200 , updating sensor and device trigger
> 2025-06-13 21:58:53.034 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '4856545650565554505200'}}
> 2025-06-13 21:58:59.023 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 21:58:59.084 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 21:58:59'}}
> 2025-06-13 21:59:05.535 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 21:59:05.536 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 21:59:05'}}
> 2025-06-13 21:59:11.455 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 21:59:11.455 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 21:59:11'}}
> 2025-06-13 21:59:18.056 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 21:59:18.056 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 21:59:18'}}
> 2025-06-13 21:59:24.002 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 21:59:24.002 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 21:59:24'}}
> 2025-06-13 21:59:30.551 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 21:59:30.551 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 21:59:30'}}
> 2025-06-13 21:59:37.116 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 21:59:37.117 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 21:59:37'}}
> 2025-06-13 21:59:42.953 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 21:59:42.953 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 21:59:42'}}
> 2025-06-13 21:59:49.508 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 21:59:49.508 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 21:59:49'}}
> 2025-06-13 21:59:55.317 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 21:59:55.317 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 21:59:55'}}
> 2025-06-13 22:00:01.501 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:00:01.501 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:00:01'}}
> 2025-06-13 22:00:07.884 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:00:07.884 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:00:07'}}
> 2025-06-13 22:00:13.777 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:00:13.777 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:00:13'}}
> 2025-06-13 22:00:20.243 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:00:20.244 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:00:20'}}
> 2025-06-13 22:00:26.088 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:00:26.088 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:00:26'}}
> 2025-06-13 22:00:33.263 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:00:33.264 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:00:33'}}
> 2025-06-13 22:00:38.500 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:00:38.500 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:00:38'}}
> 2025-06-13 22:00:45.030 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:00:45.030 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:00:45'}}
> 2025-06-13 22:00:50.988 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:00:50.988 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:00:50'}}
> 2025-06-13 22:00:57.515 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:00:57.515 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:00:57'}}
> 2025-06-13 22:01:03.521 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:01:03.521 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:01:03'}}
> 2025-06-13 22:01:10.038 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:01:10.038 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:01:10'}}
> 2025-06-13 22:01:16.091 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:01:16.091 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:01:16'}}
> 2025-06-13 22:01:22.571 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:01:22.571 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:01:22'}}
> 2025-06-13 22:01:28.469 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:01:28.469 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:01:28'}}
> 2025-06-13 22:01:34.993 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:01:34.993 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:01:34'}}
> 2025-06-13 22:01:41.512 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:01:41.512 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:01:41'}}
> 2025-06-13 22:01:47.397 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:01:47.397 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:01:47'}}
> 2025-06-13 22:01:53.759 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:01:53.759 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:01:53'}}
> 2025-06-13 22:01:59.882 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:01:59.882 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:01:59'}}
> 2025-06-13 22:02:06.322 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:02:06.322 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:02:06'}}
> 2025-06-13 22:02:12.828 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:02:12.829 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:02:12'}}
> 2025-06-13 22:02:18.780 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:02:18.780 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:02:18'}}
> 2025-06-13 22:02:24.738 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:02:24.738 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:02:24'}}
> 2025-06-13 22:02:31.258 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:02:31.258 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:02:31'}}
> 2025-06-13 22:02:37.776 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:02:37.776 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:02:37'}}
> 2025-06-13 22:02:43.487 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:02:43.488 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:02:43'}}
> 2025-06-13 22:02:50.758 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:02:50.758 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:02:50'}}
> 2025-06-13 22:02:56.817 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:02:56.817 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:02:56'}}
> 2025-06-13 22:03:03.125 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:03:03.125 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:03:03'}}
> 2025-06-13 22:03:08.767 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:03:08.767 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:03:08'}}
> 2025-06-13 22:03:14.752 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:03:14.752 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:03:14'}}
> 2025-06-13 22:03:21.435 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:03:21.435 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:03:21'}}
> 2025-06-13 22:03:27.275 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:03:27.275 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:03:27'}}
> 2025-06-13 22:03:33.805 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:03:33.805 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:03:33'}}
> 2025-06-13 22:03:39.673 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:03:39.673 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:03:39'}}
> 2025-06-13 22:03:46.200 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:03:46.200 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:03:46'}}
> 2025-06-13 22:03:51.855 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:03:51.855 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:03:51'}}
> 2025-06-13 22:03:58.380 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:03:58.380 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:03:58'}}
> 2025-06-13 22:04:04.104 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:04:04.104 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:04:04'}}
> 2025-06-13 22:04:10.628 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:04:10.629 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:04:10'}}
> 2025-06-13 22:04:16.397 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:04:16.397 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:04:16'}}
> 2025-06-13 22:04:22.919 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:04:22.919 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:04:22'}}
> 2025-06-13 22:04:28.653 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:04:28.653 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:04:28'}}
> 2025-06-13 22:04:35.180 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:04:35.180 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:04:35'}}
> 2025-06-13 22:04:40.861 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:04:40.861 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:04:40'}}
> 2025-06-13 22:04:47.382 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:04:47.382 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:04:47'}}
> 2025-06-13 22:04:53.126 | INFO     | event:motion_detection:98 - Motion detected from Porteiro
> 2025-06-13 22:04:53.126 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'motion_detection', 'type': 'Motion detected', 'subtype': 'motion_detection', 'payload': {'motion_detected': '2025-06-13 22:04:53'}}
> 2025-06-13 22:04:59.644 | INFO     | event:video_intercom_event:109 - Video intercom event from Porteiro
> 2025-06-13 22:04:59.644 | INFO     | mqtt:update_door_entities:303 - Door 1 unlocked by 4857484956525048535400 , updating sensor and device trigger
> 2025-06-13 22:04:59.644 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '4857484956525048535400'}}
> 2025-06-13 22:05:05.397 | INFO     | event:video_intercom_event:109 - Video intercom event from Porteiro
> 2025-06-13 22:05:05.397 | INFO     | mqtt:update_door_entities:303 - Door 1 unlocked by 494848505348535153500 , updating sensor and device trigger
> 2025-06-13 22:05:05.397 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '494848505348535153500'}}
> 2025-06-13 22:05:11.914 | INFO     | event:video_intercom_event:109 - Video intercom event from Porteiro
> 2025-06-13 22:05:11.915 | INFO     | mqtt:update_door_entities:303 - Door 1 unlocked by 4856545650565554505200 , updating sensor and device trigger
> 2025-06-13 22:05:11.915 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '4856545650565554505200'}}
> 2025-06-13 22:05:17.720 | INFO     | event:video_intercom_event:109 - Video intercom event from Porteiro
> 2025-06-13 22:05:17.798 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'illegal_card_swiping_event', 'type': 'event', 'subtype': 'illegal card_swiping event', 'payload': {'control_source': '51565652555600'}}
> 2025-06-13 22:05:24.246 | INFO     | event:video_intercom_event:109 - Video intercom event from Porteiro
> 2025-06-13 22:05:24.246 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'illegal_card_swiping_event', 'type': 'event', 'subtype': 'illegal card_swiping event', 'payload': {'control_source': '51565652555600'}}
> 2025-06-13 22:05:29.997 | INFO     | event:video_intercom_event:109 - Video intercom event from Porteiro
> 2025-06-13 22:05:29.997 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'illegal_card_swiping_event', 'type': 'event', 'subtype': 'illegal card_swiping event', 'payload': {'control_source': '51565652555600'}}
> 2025-06-13 22:05:36.524 | INFO     | event:video_intercom_event:109 - Video intercom event from Porteiro
> 2025-06-13 22:05:36.525 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'illegal_card_swiping_event', 'type': 'event', 'subtype': 'illegal card_swiping event', 'payload': {'control_source': '51565652555600'}}
> 2025-06-13 22:05:42.233 | INFO     | event:video_intercom_event:109 - Video intercom event from Porteiro
> 2025-06-13 22:05:42.233 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'illegal_card_swiping_event', 'type': 'event', 'subtype': 'illegal card_swiping event', 'payload': {'control_source': '51565652555600'}}
> 2025-06-13 22:05:48.753 | INFO     | event:video_intercom_event:109 - Video intercom event from Porteiro
> 2025-06-13 22:05:48.753 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'illegal_card_swiping_event', 'type': 'event', 'subtype': 'illegal card_swiping event', 'payload': {'control_source': '51565652555600'}}
> 2025-06-13 22:05:54.418 | INFO     | event:video_intercom_event:109 - Video intercom event from Porteiro
> 2025-06-13 22:05:54.418 | INFO     | mqtt:handle_device_trigger:490 - Invoking device trigger automation{'name': 'illegal_card_swiping_event', 'type': 'event', 'subtype': 'illegal card_swiping event', 'payload': {'control_source': '51565652555600'}}

[iorifly (Renato Barbosa)]

The beta version seems to have solved my problem!!