Notification types
| Child pages (Children Display) |
|---|
General
Notifications are intended to inform the user about events occurring in the monitoring Notifications are intended to inform the user about events occurring in the monitoring system.
| Note |
|---|
Attention! Sending a notification is carried out only in groups of elements, or using logic schemes |
...
To create a notification, push the button " 
" inside the "System tree" menu. Then choose an element to add. A modal window will appear.
It is possible to add the following notifications:
| Child pages (Children Display) |
|---|
Macros in the notification text
The text of the message can include macrosesmultiple macros. Macroses have Macross has the following form:
%{number of macromacros}
When notification is When notification is created the system replaces the macros variables with actual the macros variables with actual values.
The following macros are available:
Macros | Description |
|---|---|
%1 | description of the logic scheme that has triggered Displayed example: If 'Onboard temperature' (id=201001) is state 'alarm' then 'Device5' (id=601001) changes state 'on' immidiatly, ev |
%2 | Description of all sensors in the logic scheme and their sensor state when the logic was triggered. Displayed example: 'Onboard Temperature' (id=201001) in state 'normal' 'Temperature2' (id=201002) in state 'normal' |
%3 | logic scheme response time Displayed example: 08:16:46 2018/09/05 |
%4 | name of the logic scheme Displayed example: 'Logic scheme 3' |
%5 | name of the sensor which triggered the logic scheme |
%6 | state of the sensor in the logic scheme that has triggered the logic at the moment when this logic was triggered |
%7 | the value measured by the sensor or logic level that has triggered the logic scheme at the moment when it was triggered |
%8 | sensor ID that triggered the operation of the logic circuit |
Example
Example. If the text has the following form:
| Code Block |
|---|
%4 -- %1 -- %2 -- %3 |
When logic is triggered and the notification is triggered and the notification is sent, the recipient will see a message in the following form:
| Code Block |
|---|
Logic scheme name -- if 'S/N iButton'(id=13) in state 'alarm', then 'Email'(id=302) changes to state 'on' immediately 'Relay-0'(id=31) changes to state 'pulse' immediately -- 'S/N iButton'(id=13) in state 'alarm' -- 12:40:36 2012/01/18 |
Further description
| Info | |
|---|---|
We recommend to recommend to use a more informative form of message more informative form of message by additional text as an explanation. For example, | |
| title |
Full macros example
| Code Block |
|---|
Logic name:\n %4\n --\n Logic triggered at:\n %3\n --\n Logic triggered by:\n %5, %8\n State: %6\n Value: %7\n --\n Logic scheme description:\n %1\n --\n All sensor states on the moment when logic was triggered:\n %2\n --\n |
| Code Block |
Default macros
| Code Block |
|---|
Logic %4: -- Defintion: %1 Current sensor state: %2 -- System time: %3 |
Macroses %5, %6, %7 can parameterize by element identifier {id}, i.e. for these macros may set the element for which will be evaluated macros.
Macroses Macross evaluated example:
| Code Block |
|---|
%5{201002} — print the name of element with id=201002 - 'sc470-0192-internal T°C';
%6{201002} — print the state of element with id=201002 - 'normal';
%7{201002} — print the value of element with id=201002 - '27.4'. |
If an element with the specified identifier is not found in the text of the message is inserted - 'id = xxxx not found'.
If the parameter {id} is not specified, in the text of the message is inserted the calculated value for the element that is triggered by logical
...
scheme.
Since version 2.4.4, the macro %8 is available. The macro% 8 is used to determine the identifier of the sensor when the logic scheme is triggered. In the body of the message, the identifier is displayed in single quotes (example: '302014').
The macro %8 can be used to determine the identifier of the sensor when the logic scheme is triggered by a change in the state of the group, module, or system.
Suppose there is a logical scheme linking the group state change with the sending of the notification. At the initial time, all elements in the group are in a normal state. The group is also in a normal state. The logic is inactive.
Next, one of the sensors in the group is triggered. Accordingly, the group also goes into an alarm state. The logic circuit is activated according to the state of operation of the group. Under the template, the text is formed and the notification is sent.
In this case, when creating the notification text macros %5, %6 will be replaced with the name and status of the group. The macro %8 will be replaced by the value of the identifier of the triggered sensor within the triggered group.
This means that if the element changed state, then the group, module, or system into which this element is included also changes state when the state of the element changes and the group's state change results in the triggering of the logic, macro %8 in the message template will be replaced with the identifier of that element.
| Note |
|---|
Attention! The value of macro %8 is calculated at the time the logic circuit is triggered. The activation of other elements with the activated logic scheme does not change the value of the identifier in the macro %8 |
Example:
| Code Block |
|---|
1. Logic1 is triggered by a Group1 in state Warning.
2. Groups is in the state Alarm and consists of Sensor1 in state Alarm
3. Sensor2 is in state Warning.
4. Sensor3 is in state Warning
5. Sensor1 goes to state Normal
6. Group1 goes to state Warning and logic is triggered
7. Macros %8 will give identifier of Sensor1 |
Macros %8 can be used as a parameter of
...
macros %5, %6, and %7.
Example:
| Code Block |
|---|
%6{%8} - gives current state of the sensor |
...