5.7.5 - April 20, 2023 - Onvif updates

[jaydeel]

That is so strange. I rollback and it works. I update and it doesn't. I have rebooted and deleted and added the camera and still nothing.

Still testing with only the Dahua 180?
Can you try another Dahau cam your test rig?

 

[wittaj]

Yeah, I have been trying the 5442-ZE all morning and nothing.

 

[jaydeel]

Even after repeating Find/Inspect after updating?

Never mind... I missed that you already rebooted and deleted and added the camera.

 

[wittaj]

Yeah all the normal tricks didn't work.

 

[wittaj]

I even deleted BI and downloaded the latest version and set up a test camera new and still nothing. But I roll back to the last stable version and it starts working.

 

[105437]

OK, this is starting to make sense.

Here's an example ...
XML output for a line-crossing event on my 5442.

    <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>

Note in the 'RuleEngine/LineDetector/Crossed' NotificationMessage that the 'Source' entry 'Rule' has the value 'IVS-5'.

This aligns with my IVS setup in the camera. I triggered the camera for this event by crossing line IVS-5.

View attachment 160642

How do you capture the XML output from the camera?

 

[jaydeel]

How do you capture the XML output from the camera?

It's exposed in the new BI ONVIF Events Manager dialog.

 

[105437]

It's exposed in the new BI ONVIF Events Manager dialog.
View attachment 160655

Okay, thanks. I rolled back since the "OK" button isn't working.

 

[wittaj]

It's exposed in the new BI ONVIF Events Manager dialog.
View attachment 160655

What is weird is I see something similar on this screen yet they don't trigger

 

[wittaj]

I updated to 5.7.5.1 and still no ONVIF triggers.

Ticket to support sent in.

 

[jaydeel]

Ditto for the 'OK' button.

Ticket sent as well.

 

[105437]

Ditto for the 'OK' button.

Ticket sent as well.

Ken just told me 5.7.5.2 is on its way to fix the OK button.

 

[Tinman]

I figured out that by having a "inactive cam" in profile 1, (which in my setup I do) this is causing BI to puke when trying to access Staus/cameras. On my profile 7 all my cams are active and the issue goes away.

Sent note to support.

Update: 5.7.5.2 fixes my issue

 

[jaydeel]

The General tab now shows a status for the GetEVents thread.

From the help PDF...

The GetEvents thread status/error code is now visible on the General tab as well ​

and will cause a yellow caution on the camera window if in an error state.​

 

[wittaj]

The General tab now shows a status for the GetEVents thread.

From the help PDF...

The GetEvents thread status/error code is now visible on the General tab as well ​

and will cause a yellow caution on the camera window if in an error state.​

View attachment 160671

My Get Events says OK, but still no triggers LOL

 

[jaydeel]

Arghhh!

 

[wittaj]

Yep I am at a total loss. Revert back and it works, update and it stops. And I do not see anything that would be the source of not working.

Hopefully Ken has an idea because I have tried all the tricks I know.

 

[Vettester]

Hopefully Ken has an idea because I have tried all the tricks I know.

Hmmm... I just tried this and it seems to be working.

 

[wittaj]

Hmmm... I just tried this and it seems to be working.

View attachment 160686

Rub it in LOL

It is bizarre - everything looks right and the fact that I can rollback and it works is puzzling for sure.

 

[Vettester]

I'm on the latest version of BI 5.7.5.2.