Heyo,
I have my new ZM working now. Anyhow, one thing that would likely be quite handy to more than just myself, is a delayed "arming" option.
Right now, I start zoneminder, then leave the house.. at which point I receive several alarm emails and pages... as ZM has dutifully caught me snooping about my house
If there was a delayed arming mechanism, one could at least arm ZM, then leave, and have it come on 5 minutes later....
Just a thought...
perhaps for the next version... ?
It's easy enough to create a script to start ZM or use the run states.
Something like:
will do. You can cange the STATE= to a run state instead of start if you have any of those saved in zm. I'll build on this to make it more functional but that should do to get you what you want.
Regards,
Corey
Something like:
Code: Select all
#!/bin/sh
#----------------------------------------------------------------------------
# USAGE: ./zm-arm n
#
# DESCRIPTION: For delayed arming of zm
# OPTIONS: Time in seconds n
# REQUIREMENTS: ZoneMinder
#
# AUTHOR: Corey DeLasaux
# VERSION: 0.1
# CREATED: 2/14/2005 18:45:00 PM PDT
#=============================================================================
ZM_CONFIG="/etc/zm.conf"
STATE = start
if [ -f $ZM_CONFIG ]; then
. $ZM_CONFIG
else
echo "ERROR: $ZM_CONFIG not found."
exit 1
fi
DELAY=$1
command="$ZM_PATH_BIN/zmpkg.pl"
echo "Delayed ZoneMinder arming in progress"
sleep $DELAY
$command $STATE
exit 0
Regards,
Corey
I'm interested in the arming-disarming , more for wether or not to send an SMS/MMS/Mail/External alarm outside.
The recording itself should continue 24/24- 7/7 .
Imagine a shop. During daytime you'd still wish to record activity (for whenever a robbery or other stuff occurs).
But you don't want SMS/MMS/Mail to be send during cam activity.
In order to use an arm/disarm functionality you might :
-use event triggering on cams towards script in ZM
-point in that script to flag file
To arm / disarm , you then just need to alter to script or the flag file.
That way ,you'll have a real arm/disarm ,without the whole ZM to stop during daytime.
But this brings us to the real feature request behind this : job scheduler !
No more messing around with scripts , only config files.
Then sending commands from the ZM interface towards the job scheduling machine. This is the professional way of working.
example of a very nice job scheduler : http://jobscheduler.sourceforge.net/oso ... ion_en.htm
The recording itself should continue 24/24- 7/7 .
Imagine a shop. During daytime you'd still wish to record activity (for whenever a robbery or other stuff occurs).
But you don't want SMS/MMS/Mail to be send during cam activity.
In order to use an arm/disarm functionality you might :
-use event triggering on cams towards script in ZM
-point in that script to flag file
To arm / disarm , you then just need to alter to script or the flag file.
That way ,you'll have a real arm/disarm ,without the whole ZM to stop during daytime.
But this brings us to the real feature request behind this : job scheduler !
No more messing around with scripts , only config files.
Then sending commands from the ZM interface towards the job scheduling machine. This is the professional way of working.
example of a very nice job scheduler : http://jobscheduler.sourceforge.net/oso ... ion_en.htm