Empiretech color 4k-t 3.6mm latest firmware - OnVif events not triggering

[speedway1213]

I setup tripwire on the color 4k-t, no matter what I do it wont trigger.
All my other color 4k-t cameras trigger, config/settings all the same.
Only diff is the latest color 4k-t comes with the latest firmware from Jan 2024. Others are all on firmware from 2023.
I dont want to downgrade unless this is a firmware issue, or perhaps a config issue I need to address in BI due to latest firmware?

 

[looney2ns]

Did you enable Smart Plan, prior to setting up IVS?

 

[th182]

Not to hijack this thread but I am having the same issue but with a new IPC-T22IR-ZAS (specs below). I ordered nine of these cameras, one to add to my system and eight for a BI setup I will be building for a friend. Hoping to get the ONVIF stuff resolved before I start unpacking all of the other cameras. I initially added this camera to my BI by copying from another existing camera. When I couldn't get it to recognize IVS triggers, I deleted the camera and added it from scratch. I know not checking the ONVIF in one of the configuration tabs has bit me before so I've gone through every tab several times. Monitoring the Events shows that BI is seeing them, it is just not reacting to them. Thanks in advance for the help! I know @looney2ns is a genius with BI so I have faith! haha!

Device Type: IPC-T22IR-ZAS
System Version: V2.840.0000000.14.R, Build Date: 2023-11-24
WEB Version: V3.2.1.1676618
ONVIF Version: 22.06(V2.0.1.80886)
Algorithm Version: 3.9.4
Security Baseline Version: V2.3

In the camera I have Smart Plan on with an IVS Intrusion zone. Blue Iris is seeing the ONVIF events but not triggering the camera. I have compared the camera settings several times to the others and all appear the same.

IVS Event Text from within BIs Trigger ONVIF monitor:

<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:tns1="http://www.onvif.org/ver10/topics" xmlns:tt="http://www.onvif.org/ver10/schema" xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2" xmlns:tev="http://www.onvif.org/ver10/events/wsdl" xmlns:wsa5="http://www.w3.org/2005/08/addressing" xmlns:sc="http://www.w3.org/2003/05/soap-encoding" xmlns:s="http://www.w3.org/2003/05/soap-envelope">
    <s:Header>
        <wsa5:Action>http://www.onvif.org/ver10/events/wsdl/PullPointSubscription/PullMessagesResponse</wsa5:Action>
    </s:Header>
    <s:Body>
        <tev:PullMessagesResponse>
            <tev:CurrentTime>2024-06-03T21:08:47Z</tev:CurrentTime>
            <tev:TerminationTime>2024-06-03T21:17:29Z</tev:TerminationTime>
            <wsnt:NotificationMessage>
                <wsnt:Topic Dialect="http://www.onvif.org/ver10/tev/topicExpression/ConcreteSet">tns1:RuleEngine/FieldDetector/ObjectsInside</wsnt:Topic>
                <wsnt:Message>
                    <tt:Message PropertyOperation="Changed" UtcTime="2024-06-03T21:08:47Z">
                        <tt:Source>
                            <tt:SimpleItem Value="VideoSource000" Name="VideoSourceConfigurationToken"/>
                            <tt:SimpleItem Value="Analytics000" Name="VideoAnalyticsConfigurationToken"/>
                            <tt:SimpleItem Value="IVS-1" Name="Rule"/>
                        </tt:Source>
                        <tt:Key>
                            <tt:SimpleItem Value="20154" Name="ObjectId"/>
                        </tt:Key>
                        <tt:Data>
                            <tt:SimpleItem Value="true" Name="IsInside"/>
                        </tt:Data>
                    </tt:Message>
                </wsnt:Message>
            </wsnt:NotificationMessage>
        </tev:PullMessagesResponse>
    </s:Body>
</s:Envelope>

And my relevant ONVIF rules:


And for completeness My Trigger, Alert, and camera configuration all showing ONVIF selected. I did find it interesting that in this camera the ONVIF source is "VideoSource000" whereas all my previous cameras is just "000." But that appears to match what ONVIF data is being sent.

 

[th182]

Update: I sent Ken some wireshark dumps of the ONVIF events and he indicated that this will be fixed in the next BI update. So I wasn't crazy afterall!

 

[polish.sausage]

Hi,
Have you gotten a resolution for this yet? I just got two of the cameras and am running into a similar issues where there's a trigger but no snapshots. It does record a video locally to SD though...
Thanks!
Damian

 

[speedway1213]

Turns out my issue was that I orientated the camera 90 degrees to the right, the tripwire only activated in a specific direction, so when I then tried the cam in normal orientation, the tripwire set off no problem. The tripwire in the cam itself had limitations.

 

[rdxny]

Turns out my issue was that I orientated the camera 90 degrees to the right, the tripwire only activated in a specific direction, so when I then tried the cam in normal orientation, the tripwire set off no problem. The tripwire in the cam itself had limitations.

I had the same issue where the 4kt would not trip much, or at all, in "corridor mode" (turn 90 degrees). My solution is to have another camera that sees the same area, but is horizontal, provide the triggers to the 4kt that is in corridor mode. (in the horizontal camera's alerts, have the camera provide an alert to the 4kt (Command: Trigger: Camera: (the 4kt) ). The reason to do that is to have the 4kt switch from its normal substream to main stream on an alert to get the better quality clip.