I have worked to complement zmtrigger.pl with news options: (ZoneMinder released 1.22.3)
â€¢ Enabled and Disabled monitors
â€¢ Change function monitors (except None)
â€¢ Execute filters previously saved.
â€¢ Now monitors have identified by Name and not by Id number.
The format of triggers used by zmtrigger.pl is as follows "<name>|<action>|<namefilter>|<score>|<cause>|<text>|<showtext>" where
â€¢ 'name' is the name of the ZM monitor. Case sensitive.
â€¢ 'action' is 'on', 'off', 'cancel', â€˜showâ€™, â€˜enableâ€™, â€˜disableâ€™, (â€˜Monitorâ€™, â€˜Modectâ€™, â€˜Recordâ€™ , â€˜Mocordâ€™, â€˜Nodectâ€™) and â€˜filterâ€™ where 'on' forces an alarm condition on, 'off' forces an alarm condition off and 'cancel' negates the previous 'on' or 'off'. The â€˜showâ€™ action merely updates some auxiliary text which can optionally be displayed in the images captured by the monitor. Ordinarily you would use 'on' and 'cancel', 'off' would tend to be used to suppress motion based events. Additionally 'on' and 'off' can take an additional time offset, e.g. on+20 which automatically 'cancel's the previous action after that number of seconds. The â€˜enableâ€™ monitor is enabled state and â€˜disableâ€™ monitor is disabled state. All functions except None (â€˜Monitorâ€™, â€˜Modectâ€™, â€˜Recordâ€™ , â€˜Mocordâ€™, â€˜Nodectâ€™) change monitor function. The â€˜filterâ€™ execute filter previously saved.
â€¢ â€˜namefilterâ€™ is the name of filter execute in action â€˜filterâ€™. Case sensitive.
â€¢ 'score' is the score given to the alarm, usually to indicate it's importance. For 'on' triggers it should be non-zero, otherwise it should be zero.
â€¢ 'cause' is a 32 char max string indicating the reason for, or source of the alarm e.g. 'Relay 1 open'. This is saved in the â€˜Causeâ€™ field of the event. Ignored for 'off' or 'cancel' messages
â€¢ 'text' is a 256 char max additional info field, which is saved in the â€˜Descriptionâ€™ field of an event. Ignored for 'off' or 'cancel' messages.
â€¢ 'showtext' is up to 32 characters of text that can be displayed in the timestamp that is added to images. The â€˜showâ€™ action is designed to update this text without affecting alarms but the text is updated, if present, for any of the actions. This is designed to allow external input to appear on the images captured, for instance temperature or personnel identity etc.
Users browsing this forum: No registered users and 3 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum