I have a setup of 4 Tapo C520WS cameraes. They are ONVIF compliant and have AI detection that can distinguish between cars, persons and pets. Which works pretty well.
Which cannot been said about Blue Iris. Sometimes a cat 5 meters away can trigger, other times a person at 2 meter distance does not trigger.
In all it's more or less useless.
It is possible to let the cameras trigger recording in Blue Iris?
Triggering is very unreliable
Re: Triggering is very unreliable
I'm assuming you are not using CodeProject AI here.
Yes, BI5 can listen for ONVIF commands from cameras and if they are compatible can use it as a trigger. Please see Help file for details (Url is in my signature) and ask as many questions as you like.
Yes, BI5 can listen for ONVIF commands from cameras and if they are compatible can use it as a trigger. Please see Help file for details (Url is in my signature) and ask as many questions as you like.
Forum Moderator.
Problem ? Ask and we will try to assist, but please check the Help file.
Problem ? Ask and we will try to assist, but please check the Help file.
Re: Triggering is very unreliable
Many thanks. I'm not using CodeProject AI.
Have tried to follow the help-document. Assume the problem is how to set up the ONVIF events.
The XML display always shows this code:
GetEvents status toggles between "OK" and "error 00002f78".
All the the preconfigured settings are marked enable. (green V-symbol)
Have tried to follow the help-document. Assume the problem is how to set up the ONVIF events.
The XML display always shows this code:
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:hikxsd="http://www.onvifext.com/onvif/ext/ver10/schema" xmlns:hikwsd="http://www.onvifext.com/onvif/ext/ver10/wsdl" xmlns:tptz="http://www.onvif.org/ver20/ptz/wsdl" xmlns:tan="http://www.onvif.org/ver20/analytics/wsdl" xmlns:trp="http://www.onvif.org/ver10/replay/wsdl" xmlns:timg="http://www.onvif.org/ver20/imaging/wsdl" xmlns:tdn="http://www.onvif.org/ver10/network/wsdl" xmlns:tev="http://www.onvif.org/ver10/events/wsdl" xmlns:trt="http://www.onvif.org/ver10/media/wsdl" xmlns:tmd="http://www.onvif.org/ver10/deviceIO/wsdl" xmlns:tds="http://www.onvif.org/ver10/device/wsdl" xmlns:tns1="http://www.onvif.org/ver10/topics" xmlns:ter="http://www.onvif.org/ver10/error" xmlns:tt="http://www.onvif.org/ver10/schema" xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2" xmlns:wsrfr="http://docs.oasis-open.org/wsrf/r-2" xmlns:wstop="http://docs.oasis-open.org/wsn/t-1" xmlns:wsrfbf="http://docs.oasis-open.org/wsrf/bf-2" xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:xmime="http://tempuri.org/xmime.xsd" xmlns:wsa5="http://www.w3.org/2005/08/addressing" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:chan="http://schemas.microsoft.com/ws/2005/02/duplex" xmlns:wsdd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding" xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope">
<SOAP-ENV:Body>
<tev:PullMessagesResponse>
<tev:CurrentTime>2024-03-14T16:06:57Z</tev:CurrentTime>
<tev:TerminationTime>2024-03-14T16:14:02Z</tev:TerminationTime>
</tev:PullMessagesResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
All the the preconfigured settings are marked enable. (green V-symbol)
Last edited by Tapo on Thu Mar 14, 2024 7:01 pm, edited 1 time in total.
Re: Triggering is very unreliable
The trick with that window is to save it just as the ONVIF command appears as it will reset after a few seconds. It took me some time 
I then found a similar (but not quite the same) trigger in the list below the window, and copied and altered it to suit. It is very powerful and configurable, but difficult to figure out !
I then found a similar (but not quite the same) trigger in the list below the window, and copied and altered it to suit. It is very powerful and configurable, but difficult to figure out !
Forum Moderator.
Problem ? Ask and we will try to assist, but please check the Help file.
Problem ? Ask and we will try to assist, but please check the Help file.
Re: Triggering is very unreliable
When the Onvif command is sent by the camera, the xml will change and show the command. After a few seconds it will refresh and show the default info.
As I said, it took me some time. You need an able assistant to trigger the camera, and you stop the xml refreshing when it updates.
As I said, it took me some time. You need an able assistant to trigger the camera, and you stop the xml refreshing when it updates.
Forum Moderator.
Problem ? Ask and we will try to assist, but please check the Help file.
Problem ? Ask and we will try to assist, but please check the Help file.
Re: Triggering is very unreliable
For example, I captured My Reolink video doorbell being pressed (Onvif command = "Visitor") and the relevant text from the xml is shown here:
It resets after a few seconds, so you have to see the required text and stop the page refreshing.
I found it difficult to use compared to the Homeseer ONVIF plug in - which just seemed to pluck them out of fresh air - but the BI5 method is incredibly powerful, as it doesn't assume a standard command is being used.
I ended up with this:
Where I added the label "OnvifVisitor" which I use in Alerts that can only fire when a valid ONVIF doorbell press is detected.
Looking at that, I needed to change the Attribute text in my Onvif Event to PropertyOperation="Changed".<wsnt:Topic Dialect="http://www.onvif.org/ver10/tev/topicExp ... eDetector/Visitor</wsnt:Topic>
<wsnt:Message>
<tt:Message PropertyOperation="Changed" UtcTime="2024-01-21T11:45:45Z">
It resets after a few seconds, so you have to see the required text and stop the page refreshing.
I found it difficult to use compared to the Homeseer ONVIF plug in - which just seemed to pluck them out of fresh air - but the BI5 method is incredibly powerful, as it doesn't assume a standard command is being used.
I ended up with this:
- Screenshot 2024-03-15 182608.png (43.24 KiB) Viewed 5288 times
Where I added the label "OnvifVisitor" which I use in Alerts that can only fire when a valid ONVIF doorbell press is detected.
Forum Moderator.
Problem ? Ask and we will try to assist, but please check the Help file.
Problem ? Ask and we will try to assist, but please check the Help file.
Re: Triggering is very unreliable
...
Last edited by MikeBwca on Fri Apr 05, 2024 11:05 am, edited 1 time in total.
Re: Triggering is very unreliable
There are a few possibilities here:
1. The camera may not be able to send out ONVIF commands.
2. You could look at the cameras own menu to see if you have to enable it to send out ONVIF commands.
Both of those could prevent the xml showing any changes. I'm assuming you have:
3. Set the camera up with BI5's "Find/inspect" so BI5 has set up ONVIF correctly.
4. On the same page you have "Get ONVIF trigger events" ticked.
5. BI5 camera trigger tab has "ONVIF/camera events" ticked.
If all of those are OK, then you would see “GetEvents: Ok” on the camera General page. This is my Reolink doorbell camera:
But you have stated that "Get events" shows OK then an error message. I suggest having a look at the camera with Onvif device manager. Log in to it with the camera user/pw and look for ONVIF events to see if they exist and don't show errors. For my Reolink doorbell camera it showed this:
Which proved which ONVIF events were available. As I mentioned earlier though, if all of the above is working, the xml changes only for a few seconds and you have to grab it by unchecking "Auto refresh" under the xml.
1. The camera may not be able to send out ONVIF commands.
2. You could look at the cameras own menu to see if you have to enable it to send out ONVIF commands.
Both of those could prevent the xml showing any changes. I'm assuming you have:
3. Set the camera up with BI5's "Find/inspect" so BI5 has set up ONVIF correctly.
4. On the same page you have "Get ONVIF trigger events" ticked.
5. BI5 camera trigger tab has "ONVIF/camera events" ticked.
If all of those are OK, then you would see “GetEvents: Ok” on the camera General page. This is my Reolink doorbell camera:
- getevents.png (20.4 KiB) Viewed 5269 times
But you have stated that "Get events" shows OK then an error message. I suggest having a look at the camera with Onvif device manager. Log in to it with the camera user/pw and look for ONVIF events to see if they exist and don't show errors. For my Reolink doorbell camera it showed this:
- odm.png (131.68 KiB) Viewed 5269 times
Which proved which ONVIF events were available. As I mentioned earlier though, if all of the above is working, the xml changes only for a few seconds and you have to grab it by unchecking "Auto refresh" under the xml.
Forum Moderator.
Problem ? Ask and we will try to assist, but please check the Help file.
Problem ? Ask and we will try to assist, but please check the Help file.
Re: Triggering is very unreliable
Got an assistant. The camera triggers by AI and save recordings, but the the only XML received by BlueIris is what I posted above.TimG wrote: ↑Fri Mar 15, 2024 11:21 am When the Onvif command is sent by the camera, the xml will change and show the command. After a few seconds it will refresh and show the default info.
As I said, it took me some time. You need an able assistant to trigger the camera, and you stop the xml refreshing when it updates.