this feature is not released yet!
This page explains the portal interface for alarm configuration on partner level. If you are not a superuser or above, with general camera permission for your partner account, you are on the wrong page and should instead go here. If you aren’t familiar with the core concepts of how alarms in the yellow portal work, I’d recommend reading up on that first
...
On the overview page, you will see a list with all alarms that sexist exist for your partner. You can right click on any existing alarm to edit it or delete it, or you can create a new one by clicking “create” in the top-right corner. When editing or creating, you will be brought to the alarm configuration page.
...
The alarm configuration page is split into four major sections: The general configuration, the default peripherals, the condition and the actionactions. To learn more about the concepts behind these terms, please refer to this page: core concepts
...
Action Delay: When an alarm changes to ALARM state from another state, it will wait for at least this many seconds until it executes the alarms action for that camera for the first time. If the state changes back to OK before the delay expires, no actions will be executed. Use this if some of your alarms are producing noise because they are oscillatingto reduce noise from oscilations or irregular hickups.
Action Interval: When an alarm for a camera is in ALARM state, and actions have been executed at least once already, at least this many seconds will pass until actions are executed the next time. Use this to avoid spamming actions like notifications when an alarm state lasts for more than a minute longer time (which will be most of the time, unless you’re really fast at fixing things).
Action Execution Window: A time window specifying when during the day or week the alarm may execute actions. If an alarm for a camera is in ALARM state, but is outside the specified time window, no actions will be executed for the camera alarm until it enters the time window again. Trigger delay will start counting as soon as the state changes to ALARM. If it expires before outside the time execution window is entered, actions will be executed immediately when entering it, provided the state is still ALARM. If it didn’t expire yet when entering the window, actions will defer execution until it expires. If the state changes to ALARM outside the time window, and changes back to OK before the time window is entered, no actions will be executed. Use this if you want to suppress for example notifications during the night when noone will read them (or wants to get woken up by them), or at weekends when you don’t want to be bothered by them. Right now, the time of day is always interpreted in CEST.
...
To the left, you have to configure one condition for your alarm, that determines when a camera using this alarm will have its alarm state change. Conditions are always evaluated for a specific camera. You can choose a type of condition, then configure it further to fit your specific needs (note: At this early stage there is only the Camera Event Condition, but more are to follow).
The widget to the right allows you to define several actions to your alarm, one for each type (Note: Right now, there’s only the Email Notification action available, but more are planned in the future). Actions will be executed for a specific camera when the state of a camera alarm changes to ALARM and all other requirements are fulfilled (see general parameters).