[ENG] 13. [DKSF 48.5 IU] Device Support for Custom Notifications

In the device’s web-interface, it is possible to create custom notifications (SMS EMail) with an arbitrary text, which can include additional information about the event that caused the notification. The customizable notifications work in parallel with standard SMS and email notifications with the fixed text. Except the sending SMS and email, configured notifications allow you to generate an HTTP GET request designed to integrate NetPing with cloud services. For example, with the automation service Zapier.com or ifttt.com, which allows you to perform a lot of actions receiving relevant notifications. You can learn more about the possibilities provided by Zapier.com at https://zapier.com/zapbook/webhook/, and iftt.com at https://ifttt.com/discover.

NetPing does not have a client`s HTTP/HTTPS, and to complete the request, it accesses the proprietary cloud service webhook.netping.ru. It is transparent, does not remember and does not accumulate information passed through it. Available for any NetPing device and does not require any prior authorization and configuration.

Remember that requests to the called service come from the Internet, so you need to specify the external address of the service, and not the address of the local network.

To create a custom notification, go to the “NOTIFICATIONS” page of the device’s web interface and click on the line “click here to add new record” (maximum 16 custom notifications):

A notification settings window will appear with the following parameters (the screenshot below shows an already customized notification from the temperature sensor on channel 5).

SMS-notification:

HTTP GET-notification:

Еmail-notification:

The description of sensors and events:

When you use the channel number “any channel”, it is recommended to use the substitution with the channel number so that the notification contains information about the sensor which caused this notification.
The SensorThe EventThe Description
 Termo 1..8/any channelfailed sensorSensor failed of not connected
below safe rangeTemperature has dropped below safe range
in safe rangeTemperature has returned to the safe range
above safe rangeTemperature has risen above safe range
Humidity (rel. humid) 1..4 any channelfailed sensorSensor failed of not connected
below safe rangeRelative humidity has dropped below safe range
in safe rangeRelative humidity has returned to the safe range
above safe rangeRelative humidity has risen above safe range
Humidity (temperature) 1..4 / any channelfailed sensorSensor failed of not connected
below safe rangeTemperature of a humidity sensor has dropped below safe range
in safe rangeTemperature of a humidity sensor has returned to safe range
above safe rangeTemperature of a humidity sensor has risen above safe range
Smoke (1W) 1..4 / any channelNormalReadings are normal
Alarm!

The sensor detected the smoke

offThe sensor (current in the loop) is switched off
failedThe sensor failure
 IO line 1..4 / any channelLog.0Logic line level switched to 0
Log.1Logical line level switched to 1
Relay 1...8 / any channeloffThe relay is off
onThe relay is on
Watchdog 1...8 / any channelreset The "Watchdog" module carried out the reset of the relay
suspenseThe operation of the module is suspensed
restoreThe operaion of the module is restored
Signal 1..4 / any channelactivation

The signal has been activated by logic. So, the rule of logic worked, the output of it is the “Signal 1..4”. More details about the rules of logic and, in particular, the signal can be found in the section [ENG] 10.2. [DKSF 48.5 IU] How Can I Use the "LOGIC" Module?

Monitoring 220V

GSMSMS not a command Incoming SMS is not a command
SMS from unknown numbersAn incoming SMS from an unknown number (subject to the setting of white lists of numbers). Read more about setting up white lists in the section: [ENG] 12.2. [DKSF 48.5 IU] I Need to Configure the Number to Send SMS Notifications. How Can I Do This?

The Description of notification methods:

The method of notificationThe description
SMS

Arbitrary SMS notifications. At the beginning of the text of a custom SMS notification, you can specify up to four recipients by specifying their phone numbers in square brackets, separated by commas. Numbers are indicated in the format "Countrycode OperatorcodeCustomernumber". There must be a space between the closing square bracket and the message text. For example, "[+79130000001, +79130000002, +79130000003, +79130000004] Houston, we have a problem!"

If you do not specify the recipients, i.e. there are no square brackets at the beginning of the text,  the SMS will be sent to the numbers specified in the settings on the “SMS” page of the device’s web interface and marked with a “On” checkmark.

HTTP GET

The called URL of a third-party service or cloud application. In order to send these notifications, the following scheme is used:NetPing--SNMP TRAP --> webhook.netping.ru–HTTP(URL) --> destination server. Therefore, the destination server must be accessed via a white address and access to it must be from the outside.

email

The sending of the email notification is carried out to the addresses specified on the "EMAIL" page. In a custom notification it is possible to set the subject of the message in the "Subj" entry field (substitutions are possible) and the text of the email message itself. The recipient cannot be set, messages are sent to the recipients specified on the "EMAIL" page.

You can put the information from the NetPing MIB branch related to the sensor, IO line, or the relay that caused the event in the custom notification text. Format: {N}, where N is the SNMP OID component located in front of the sensor index.

 For example, the text of the SMS notification “{6} - {3} ({4}°C - {5}°C), {2}°C" for the temperature sensor includes the following information from the NetPing MIB branch of the tree:

The SubstitutionThe Complete OID of variable value from NetPing MIBThe name of the variable value from NetPing MIBThe Description
{6}.1.3.6.1.4.1.25728.8800.1.1.6.nnpThermoMemoThe memo of the Temperature Sensor, where n  a number of sensor 1..8.
{3}.1.3.6.1.4.1.25728.8800.1.1.3.nnpThermoStatusThe Status of the Sensor, where n  a number of sensor.
{4}.1.3.6.1.4.1.25728.8800.1.1.4.n

npThermoLow

The lower border of the range of normal temperature values, where n is the number of sensor.
{5}.1.3.6.1.4.1.25728.8800.1.1.5.nnpThermoHighThe upper border of the range of normal temperature values, where n is the number of sensor.
{2}.1.3.6.1.4.1.25728.8800.1.1.2.n

npThermoValue

Current temperature at the temperature sensor, where n is the number of sensor.

Additionally.

In the SMS text in the custom event notifications from GSM (SMS is not a command and SMS from an unknown number), the following substitution can be used:

  • {11} - sender's mobile number;
  • {12} - SMS text encoded 1251;
  • {13} - SMS text encoded UTF8.