BI Does Not Switch Active Zone Map on Schedule

[tommygun]

First, the “setup”. I think I have a relatively simple Blue Iris setup using only 8 cameras and a simple Schedule that only involves 4 profiles. I have had it running for years and “tune” it as necessary, but I am new to the forum.

The 4 profiles are 1-Home at Night, 2-Away, 6-Dawn/Dusk, 7-Home Day.

I have set a few cameras up with Zone Maps to eliminate false triggers like from a car’s headlight splash onto the driveway at night, or when the wind swings the pool umbrella wildly.

I recently replaced my driveway camera and defined separate Zone Maps for different Profiles that switch according to times defined on the Master Schedule. I do not have any cameras using schedule override.

Also, I do not currently use any defined Zones other than Zone A in any Zone Maps, as all I am looking for is plain motion in a defined area.

During the fine tuning of Trigger behavior, I have reason to edit something in the “Motion Sensor” dialog box, and when I open it, I see the VERY handy “Active Zone map:” descriptor at the bottom of the dialog box.

Almost always, it tells me that the Active Zone Map is “\Motion\x” with “x” being the number that corresponds to the current Profile (minus 1 of course).

But, every so often, with the system running “normally” I will get a trigger from my Driveway camera with the corresponding Alert. When I look to see what Profile is currently running it IS the correct one for the current time on the Master Schedule. Replaying the clip shows that the trigger was from within an area that should be blacked out on the Zone Map for that Profile. In other words, an area that I drew on the Zone Map as inactive for the current Profile.

So, I pull up the Motion Sensor dialog box and to my surprise the “Active Zone map:” designator says “None”.


It is as if, when the Profile changed according to the Schedule, the Active Zone map for this camera did not change along with the Profile change and has gotten lost. If I manually force a different Profile from the main window and then restart the correct Profile (the one the Schedule calls for currently) and then re-enter the “Motion Sensor” dialog box, it NOW shows the correct “Active Zone map:” and the Trigger now behaves correctly, not alerting on the Zone Map’s inactive areas.
Some additional information.

I have never noticed this on any other camera. They all switch Zone Maps as the Profile changes if they are programmed with different Maps for certain Profiles.

I do not use complex trigger functions, only Motion. No I/O, OnVIV, etc.

I have only noticed this since I replaced that Driveway camera, as it has greater area coverage and “sees” the street requiring inactive areas in certain Profiles. The old camera had its entire field of view active, as it could not see the street, only the driveway, and never needed to have alternate Profiles.

Can anyone help explain why that camera will sometimes “lose” its “Active Zone map;” and show it as “None”?

[TimG]

That's a new one for me ! I don't use profiles, but I checked my cameras, and they all show \Motion although it takes a second for it to populate.

Have you emailed Support about this ? Could be a bug.

[tommygun]

I have not contacted support yet because I thought maybe that it's something I have overlooked in my setup and don't want to bother them if it's a noobie error. I figured I'd try here first with so many people on here having vastly more complex systems than I have, maybe someone has experience with this.

[TimG]

Every installation is different, and your requirements may vary a lot from other users. Do send an email to Support, as it may speed up the process.

[MikeBwca]

I tried to 'mess up' one of my cameras to see if I could get the same result. Unfortunately, I couldn't.

It may be that one of your profiles is causing this. Switch to each of the profiles and check to see if one of them says 'None'.

[tommygun]

I tried to 'mess up' one of my cameras to see if I could get the same result. Unfortunately, I couldn't.

It may be that one of your profiles is causing this. Switch to each of the profiles and check to see if one of them says 'None'.

Thanks for trying. I looked at all the profiles and they all populate the "Active Zone map:" field properly when manually switched. It seems as if it only misses the switch over when it's running on its schedule.