Blue Iris not processing external triggers (Dahua/Andy cameras)

saltwater

Getting comfortable
Oct 6, 2019
503
643
Melbourne, Australia
This has been bothering me for quite a while now. My Blue Iris setup is not receiving any external triggers from my Dahua (Andy 5442) cameras. As of a few days ago, if I activated the 'Get ONVIF trigger events' I ended up with a yellow triangle symbol at the top of every sub-stream live-viewing window. I then noticed that the make of the cameras were all 'Generic/ONVIF' and when I then selected 'Dahua' the yellow triangle symbols disappeared. I thought I was onto a winner, but no, I'm still not getting any external trigger events. I've checked the SD card of one camera and I can confirm that the IVS settings set are in fact working and record to the SD card.

I've attached two screenshots of the relevant pages and below is a copy of the XLM of the configure page of ONVIF Events:

Code:
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:d="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsrf-bf="http://docs.oasis-open.org/wsrf/bf-2" xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2" xmlns:ter="http://www.onvif.org/ver10/error" xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:sc="http://www.w3.org/2003/05/soap-encoding">
    <s:Body>
        <s:Fault>
            <s:Code>
                <s:Value>s:Sender</s:Value>
                <s:Subcode>
                    <s:Value>ter:NotAuthorized</s:Value>
                </s:Subcode>
            </s:Code>
            <s:Reason>
                <s:Text xml:lang="en">Wsse authorized time check failed.</s:Text>
            </s:Reason>
        </s:Fault>
    </s:Body>
</s:Envelope>

From what I can gather from the code snippet above, the errors are related to time checks and some form of authorisation, but I've got no idea what I need to change. Needless to say, my system time is accurate to the second.

Can anyone shed any light on this?
 

Attachments

  • 2024-10-22 16_20_16-Network IP camera configuration.jpg
    2024-10-22 16_20_16-Network IP camera configuration.jpg
    74.6 KB · Views: 8
  • 2024-10-22 16_22_25-Driveway.jpg
    2024-10-22 16_22_25-Driveway.jpg
    65.4 KB · Views: 7
  • 2024-10-22 16_25_17-ONVIF Events.jpg
    2024-10-22 16_25_17-ONVIF Events.jpg
    89.2 KB · Views: 7
Switch it back to generic.

Usually after a few minutes the camera will calm down and the triangle goes away.

If it doesn't, in the camera GUI, Under Network > Access Platform, turn onvif authenticator off and that should fix the error.
 
  • Like
Reactions: saltwater
Switch it back to generic.

Usually after a few minutes the camera will calm down and the triangle goes away.
Thanks, it worked, it got rid of the yellow triangle and now I'm just waiting for a car to drive past, could be a while, it's a quiet street.
 
Unfortunately, I still have the same problem. On checking the log screen, a series of 'Event Subscriptions' constantly streaming in with the message code "Event Subscriptions: 00002efd" against all cameras.

To clarify what I've changed:

1. Changed cameras back to Generic/ONVIF (from Dahau)
2. Turned off - authentication
 
Are the events working, you are just getting that error?

It's a handshake issue and that is what turning off authentication is supposed to fix.

Try doing another find/inspect with BI now that the authentication is off.
 
  • Like
Reactions: saltwater
Thank you very much; that did the trick, and now receiving external alerts for the camera. Now I need to do the same for the remaining cameras.

UPDATE: Yes, for all cameras, Blue Iris now receives the external triggers.
 
Last edited: