...
Every alarm is governed by a single condition. Right now , there is in fact only one type of condition available, though it offers a wide range of possible configurations all on its ownthere are two different types of conditions, one that watches a cameras monitoring event and one that watches a cameras overall condition.
Going forward, further we hope to add more types of conditions will be added, enabling you to evaluate more aspects of a camera.
...
Alarm actions are the actual ringing of the alarm bells. Metaphorically of course, we don’t have any actual bells. In a base configuration, all actions of an alarm are executed for a specific camera as soon as the state of that camera alarm goes into ALARM.
Right now , there is only one there are two generic type of action actions available, which is the email notification action. In the future more types of actions will become available, and an alarm can have multiple actions - notification via email or sms. More specialised alarm types may be available, but I won’t mention them all here. While an alarm can only have one condition, it can have multiple actions, up to one of each type.
One particularly useful aspect of actions is that their configuration can be extended for specific cameras, by users down to poweruser level. That is, lower tier users can add their own configuration to an action to suit their own needs, which will be executed in addition to the default configuration in the alarm. In other words, to take an email notification as an example, they can add their own email addresses to the list, and define their own subject and message text, but they cannot remove any recipients that are configured in the alarm itself, nor change the configuration of the message these recipients receive.
...
In order to keep alarms as effective as possible while annoying you as little as possible, the various parameters in this section allow you some precise control about when and when not to execute an alarms actions, and how often. The exact function of these parameters are described here: Alarm Configuration
...
The last part of an alarm configuration is a pattern of default camera peripherals, that can be used to automate alarm assignment. Creating a new alarm it is not very productive if that alarm then has to be added manually to every camera. Nor is it very productive to activate the desired alarms on any new camera you create.
...
The basics should be fairly clear by now: When you add a specific alarm to a specific camera, a camera alarm is created that is actually evaluated, has an alarm state and can execute actions. There are two ways to add an alarm to a camera: Either through applying an alarms default camera peripherals (see above), or by manually adding the alarm to a camera on the camera configuration page ( *not* the alarm configuration page!).
...
No, what you can do in this case, is extend the action configuration in the Camera Alarm Configuration and add your customers email there, and any emails he of people they might want to receive the notification too. And you can enter a custom message for the emails that list receives, for example in a different language, and configure some other things, and all of this will not touch the base configuration of your alarm, and the configuration will only be used for this specific camera. The email addresses registered in the alarm configuration will all still receive the mail as configured in the alarm config, even for this specific camera.
...