I loaded this up on a test computer - are you getting any ONVIF triggers in BI? None of the ONVIF triggers are firing for me now.It looks like we might be able to ignore vehicle triggers and keep only people triggers.
I've trying to experiment, but currently I cannot actually change the setting. The OK button is not working.
This is a Dahua 5442T-ZE
View attachment 160591
EDIT: Got it set by directly editing the registry. But so far its not working as anticipated (but my N is only 1).
View attachment 160595
They're still working for me.I loaded this up on a test computer - are you getting any ONVIF triggers in BI? None of the ONVIF triggers are firing for me now.
Yes, I can confirm a couple of issues with this update after testing. The OK button doesn't work as you pointed out. Also, the iOS app home screen is broken. Rolled back to the latest stable version.It looks like we might be able to ignore vehicle triggers and keep only people triggers.
I've trying to experiment, but currently I cannot actually change the setting. The OK button is not working.
This is a Dahua 5442T-ZE
View attachment 160591
EDIT: Got it set by directly editing the registry. But so far its not working as anticipated (but my N is only 1).
View attachment 160595
Yes I also started to get Event errors from a camera that uses IVS rules as well.While this is hopefully leading to the ability to be able to select which IVS rule you want to do what, at this time either the coding is undecipherable or the ability to have actions happen based on IVS rule isn't here yet.
For example, with an NVR you can create an IVS rule that will trigger a recording but not alert you, and then an IVS rule when the person gets closer to have it alert you.
In BI, it doesn't acknowledge the different IVS rules and simply sends a BI trigger. I don't think this update is there yet. You can see it based on human or vehicle, but not per IVS rule.
The new ONVIF Events Manager dialog appears to be prepopulated with 15 default (standard?) events.While this is hopefully leading to the ability to be able to select which IVS rule you want to do what, at this time either the coding is undecipherable or the ability to have actions happen based on IVS rule isn't here yet.
For example, with an NVR you can create an IVS rule that will trigger a recording but not alert you, and then an IVS rule when the person gets closer to have it alert you.
In BI, it doesn't acknowledge the different IVS rules and simply sends a BI trigger. I don't think this update is there yet. You can see it based on human or vehicle, but not per IVS rule.
<s:Body>
<tev:PullMessagesResponse>
<tev:CurrentTime>2023-04-21T16:49:21Z</tev:CurrentTime>
<tev:TerminationTime>2023-04-21T16:50:31Z</tev:TerminationTime>
<wsnt:NotificationMessage>
<wsnt:Topic Dialect="http://www.onvif.org/ver10/tev/topicExpression/ConcreteSet">tns1:RuleEngine/LineDetector/Crossed</wsnt:Topic>
<wsnt:Message>
<tt:Message PropertyOperation="Changed" UtcTime="2023-04-21T16:49:20Z">
<tt:Source>
<tt:SimpleItem Value="00000" Name="VideoSourceConfigurationToken"/>
<tt:SimpleItem Value="00000" Name="VideoAnalyticsConfigurationToken"/>
<tt:SimpleItem Value="IVS-5" Name="Rule"/>
</tt:Source>
<tt:Key>
<tt:SimpleItem Value="310311" Name="ObjectId"/>
</tt:Key>
<tt:Data>
<tt:SimpleItem Value="false" Name="State"/>
</tt:Data>
</tt:Message>
</wsnt:Message>
</wsnt:NotificationMessage>
</tev:PullMessagesResponse>
</s:Body>
No, no changes.Glad you are starting to figure this out!
My cams are not triggering external in 5.7.5. If I rollback they trigger.
Did you do anything to the cam settings other than just updated?