Determine what caused alarm

Forum for questions and support relating to the 1.30.x releases only.
Post Reply
Thomas007
Posts: 8
Joined: Wed Sep 20, 2017 10:33 am

Determine what caused alarm

Post by Thomas007 » Thu Dec 14, 2017 8:18 am

I have Monitors with multiple zones. When I get an alarm, I sometimes wonder what caused the alarm - which zone, and which part of the image.
How do I see that?

From what is stated in the userguide, it seems that Blobs are shown with the configured color, but I don't use blobs (yet), as I want to use blobs as a last resort, because of the additional processing overhead. So I use AlarmedPixels instead.


BR Thomas

PacoLM
Posts: 964
Joined: Wed Dec 02, 2009 9:55 pm
Location: Spain

Re: Determine what caused alarm

Post by PacoLM » Fri Dec 15, 2017 7:28 am

Hi Thomas,

With OPTIONS::CONFIG::CREATE_ANALYSIS_IMAGES you have the option to get a visible way to know which caused the event and where.
http://zoneminder.readthedocs.io/en/sta ... onfig.html

Hope it helps!
PacoLM

mini-ITX system (6 IPCams - Ubuntu14.04 - ZM1.31.1)

Thomas007
Posts: 8
Joined: Wed Sep 20, 2017 10:33 am

Re: Determine what caused alarm

Post by Thomas007 » Fri Dec 15, 2017 8:49 am

Hi Paco.

That options is already checked.

When studying the frames marked as alarm frames, all I see is one thin red line, as a box, around the entire frame (captured image). So I cannot see which of the zones caused the motion detection.

BR Thomas

PacoLM
Posts: 964
Joined: Wed Dec 02, 2009 9:55 pm
Location: Spain

Re: Determine what caused alarm

Post by PacoLM » Fri Dec 15, 2017 9:06 am

It should only make the shape of the changed area, you may need to play with the settings.

mini-ITX system (6 IPCams - Ubuntu14.04 - ZM1.31.1)

snake
Posts: 67
Joined: Sat May 21, 2016 2:20 am

Re: Determine what caused alarm

Post by snake » Sat Dec 16, 2017 2:05 am

One option which is not related to zones but will help you to 'determine what caused alarm' is if you use ZMTrigger. You can specify the source of zmtrigger in its packet (see /usr/bin/zmtrigger.pl on debian). This means you could have multiple hardware devices; let's say a PIR, a laser diode sensor, and maybe a reed switch on a window. Each would be watching different areas. When you send the packets from these devices, there is a spot to specify the source. So it would be possible then to specify "Front hallway Laser" or "PIR" or "Window Reed" on each device. Yes they can all point to the same monitor ID (camera).

User avatar
knight-of-ni
Posts: 2070
Joined: Thu Oct 18, 2007 1:55 pm
Location: Shiloh, IL

Re: Determine what caused alarm

Post by knight-of-ni » Sat Dec 16, 2017 1:40 pm

Thomas007 wrote:
Fri Dec 15, 2017 8:49 am
Hi Paco.

That options is already checked.

When studying the frames marked as alarm frames, all I see is one thin red line, as a box, around the entire frame (captured image). So I cannot see which of the zones caused the motion detection.

BR Thomas
That means blob detection is not turned on under the motion settings for the camera.
Visit my blog for ZoneMinder related projects using the Raspberry Pi, Orange Pi, Odroid, and the ESP8266
All of these can be found at https://zoneminder.blogspot.com/

rockedge
Posts: 767
Joined: Fri Apr 04, 2014 1:46 pm
Location: Connecticut,USA
Contact:

Re: Determine what caused alarm

Post by rockedge » Sat Dec 16, 2017 9:01 pm

When you send the packets from these devices, there is a spot to specify the source. So it would be possible then to specify "Front hallway Laser" or "PIR" or "Window Reed" on each device. Yes they can all point to the same monitor ID (camera).
by adding a "%Q" to the end of the Timestamp like this example :%N - %d/%m/%y %H:%M:%S %Q this will display a cause or source sent by the string going to zmTrigger.pl on the stream view.

Code: Select all

$monitor|on = 1;
$extTriggerx = "$monitor|on+120|255|motion sensor|FrontDoor|motion sensor";

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests