[ENG] 15. [DKSF 70/71.6 IU] Support of Customizable Notifications by a Device

In a web interface of a device, there is a possibility to create SMS notifications with a random text, which work in parallel with the standard SMS notifications with a standard text.

In a web interface of a device, there is a possibility to create notifications, sent by the request HTTP GET. WEBHOOK or HTTP API, which is a mechanism of a realization of notifications about certain events, sent to third-party services or applications in a real-time mode. HTTP API is a much more effective solution for receiving data in a real timе mode. A device has this feature with the aim to be simply integrated with modern third-party services and applications, which support this technology. For example, the integration with the automation service Zapier.com allows executing many actions when receiving corresponding notifications. More detailed information about the possibilities provided by Zapier.com can be learned via the link: https://zapier.com/zapbook/webhook/.

To create a configured notification, there is a need to go to the page «NOTIFICATION» of a device web interface and click the line «click here to add new record» (a maximum of 16 customizable notifications):

A window for configuring a notification with the next parameters will appear (on the screenshot below an already configured notification from the temperature sensor on the channel 5 is represented):

Sensor – is a drop-down menu with the choice of a necessary sensor and its sequence number for sending a notification from it. Possible values are: «Thermo», «Humidity (relative humidity)», «Humidity (temperature)», «Smoke (analog current loop)», «Smoke (1W)», «IO line», «Relay».

Event – is an event that initiates sending a notification from a chosen sensor. If no event is specified in the settings, then such notification is considered inactive.

Notification Method – is a method of sending a notification. Possible values are «SMS», «HTTP GET».

SMS Text – is a random text for an SMS notification. At the beginning of the text of a configured SMS notification, it is possible to set up to four destinations, having indicated their phone numbers in square brackets divided by a comma. Numbers are specified in the format «Country_codeOpertor's_codePhone_number». Space must be included between a closing square bracket and a text of a notification. If destinations are not indicated, i.e. there are no square brackets at the beginning of the text, then SMS will be sent to the numbers specified in the settings on the page «SMS» of a device web interface.

URL of a request – is a called URL of a third-party service or a cloud application. To send these notifications the next pattern is used: NetPing--SNMP TRAP --> webhook.netping.ru–HTTP(URL) --> destination server. Therefore, a destination server must be addressed using a white address and it must be accessible from the outside.

It is possible to include the information from the MIB branch that is related to the sensor, IO line or a relay that caused the event into the text of an SMS or in the URL. The format is {N}, where N is a component of the SNMP OID that is placed before the sensor index.

For example, a text of an SMS notification «{6} - {3} ({4}°C - {5}°C), {2}°C» for a temperature sensor includes the next information from the branch and the MIB tree: