How to trigger with a 2nd profile + 2nd motion zone

[markn62]

Within one camera configuration in Trigger I've added profile 2 with a zone B mask for a separate area to detect in a similar way as zone A but only motion in zone A works. in Record I set profile 2 to sync with profile 1. And in Alert I set profile 2 with motion zones as =B. Is there additional settings needed to get a second masked area to trigger? The Help PDF isn't providing an answer. Only talks about using zones in fancier crossing fashion A>B, etc.

[BruceH]

You could try making a clone of the camera and configure it to trigger differently!

[IAmATeaf]

CLoning is the way I would do this. For profiles a cam can only have 1 profile active at any one time as far as I know so you would need to flick the cam over to the other profile in which case it won’t obey the other profile.

[Pogo]

Clone it. Zone A on both cams with different triggers, etc. No profile nonesense involved.

Don't overthink it. Butt simple.

[Pogo]

General zone for basic motion triggering of the main camera..., primarily night time activity, but obviously grabs daytime stuff as well. No alert with this configuration. I record 'clips only' with Blue Iris in this instance, but also record 24/7 to an analog DVR with this camera for redundancy.

Zones A.jpg (114.22 KiB) Viewed 2366 times

Ingress trigger for alerts using a clone of the main camera. 99.9% effective with nearly zero nuisance alerts with several methods available including Amcrest Surveilance Pro (via the local DVR p2p) and Pushover for push alerts. Re-trigger time and max duration are set to record anything that comes in until it leaves within a 6 minute window. Works perfectly.

Honic Clone Motion Zone.jpg (228.79 KiB) Viewed 2366 times

Perimeter intrusion example; Notice the size of the pixels in the last two examples. There a lots of em. 1080p analog camera main stream..., on purpose. The first is the 352x240
sub.

Perimeter Intrusion.jpg (170.71 KiB) Viewed 2363 times

[markn62]

How is an ingress trigger done? I only see edge vector, gaussian and simple. Which are you using in example #2. I'm trying to add to what looks much like your example #1 with example #2.
How do you do example #1 with 24/7 recording no alert, and example #2 momentary with alert when both are in zone A? I tried putting example#2 in zone B and it doesn't work.

[markn62]

Clone it. Zone A on both cams with different triggers, etc. No profile nonesense involved.

Don't overthink it. Butt simple.

How do you clone, add the camera twice? Would take up another viewport in the mobile app and use more CPU, no? Why don't multiple zones with different record/alert actions work?

[Pogo]

How is an ingress trigger done? I only see edge vector, gaussian and simple.

12 pixels as a 'zone'; call it a 'poor man's tripwire'. 'Simple' is my algorithm of choice across the board. 'Ingress trigger' was simply in reference to driveway 'ingress'.

I'm trying to add to what looks much like your example #1 with example #2. I tried putting example#2 in zone B and it doesn't work.

I struggled with this at first also. A zone needs to be contiguous to correctly respond to a trigger setting. May just be a thin line of pixes needed to achieve two distinctly different areas, but multiples of the same zone don't work as one would expect and is a futile exercise at best. Adding more zones can also be a challenge until one realizes there's only one trigger to go around..., as in each zone does not have it's own trigger simultaneously independent of all other zones..., unless this feature has been recently added. (There is significant discussion about this in the 'Feature Request' thread.)

How do you do example #1 with 24/7 recording no alert, and example #2 momentary with alert when both are in zone A?

The main camera is example #1. #2 is a clone of #1. #2 is wiped of all original #1 zone and trigger settings which are then simply replaced by the new 'trip wire' settings. Again, butt simple and much easier than fighting with all the multiple zones and profiles nonsense.

A clone is simply a copied (and renamed) BI config file for an existing camera's streams and configuration, including IP/hardware address and user credentials. Very little CPU overhead is being consumed by the clone as the stream(s) have already been decoded by BI for the master's configuration and are simply replicated for the clone. Hence no additional CPU consumption of any consequence.

Once the clone configuration is esablished as its own entity in Blue Iris, you can change virtually any transfrerred main camera setting to whatever suits the purpose of the clone. It's its own independent camera now (for the most part) with the exception of the main camera's core configuration settings as mentioned above. Simply wipe it clean of all trigger, record, alert, schedule, whatever other settings that may be held over from the main camera and start from scratch to create the functionality desired.

As for the 24/7 recording, the particular camera in this case is a high quality analog camera running through an Amcrest pentibrid DVR completely independent of Blue Iris intially. This is the 24/7 redundancy recording medium for the camera. So how do I get it into Blue Iris to do all this other stuff? Add the DVR to BI just like adding a single camera and simply identify any or all cameras by their DVR channel number and create another identical DVR entry with new channel number in BI for each additional camera you want to add. There are a few minor considerations on how this can be achieved, but it's a pretty trivial process regardless of an nuances encountered.

As for different triggers associated with the differnt Zone 'A's, that's what the clone is all about.

[jrbeddow]

Huh, even though I get some of the functionality of using clone cameras (separate zones and alerts), I still don't find them at all useful, maybe someone can explain what I'm not seeing here.

If all you are doing is getting alerts (and recording is disabled on the clone camera), then wouldn't that require you to go back to the original (main/source) camera to review and watch the timeline footage if an alert is received from the clone? This completely breaks my workflow: I get my alerts pushed to me via the Pushover app, I then click the UI3 link, which opens the alert clip directly from my phone (yes, I have an always available VPN connection to home). Having to manually go back to review every alert by reviewing the original camera timeline footage seems like a giant step backwards.

Sure, I could enable all the recording features on the clone camera, but then it really is consuming massively more hard drive space and general computer resources (defeating the "low-resource" argument). What did I not understand here? Clones seem to be often proposed as a magic bullet, solving all sorts of common scenarios.

[Pogo]

What did I not understand here?

The very purpose of creating a clone..., and maybe more importantly, that the clone is completely independent from the original camera in all aspects except hardware, IP address and user credentials-- basically another camera pointing at the same exact scene using the same decoded stream(s) as the parent camera. This obviously opens up many more options to customize and duplicate zones, triggers, alerts, schedules..., whatever may augment the original camera's settings or limitations to create a more effective setup for a given situation.

Apologies for neglecting an important part of how this all works for anyone else not seeing the forest for the trees, but the very creation of the clone entry in Blue Iris also requires a new camera name which in turn creates a new and completely independent filename and database entry for the clone. This is how/where the independence is achieved.

As for Pushover utilization with a cloned camera, use it any way that suites your purpose. Set up whatever triggers you want for whatever alerts you want completely independent of the parent..., or to link to the parent stream only under certain circumstances, or to a completely different camera if you like. The magic is in the macros, there.

Any triggers, alerts or clips from the clone will be independent of the parent in both the Clip Viewer and Timeline simply by virtue of the clone's independent identity by filename and db entry.

Storage allocation and management of a clone is whatever you want it to be. Mine generates a short clip and single jpeg for each alert. No biggie.