Essentials

Notifications for a group of devices can be configured to provide real-time monitoring of the data received from the devices or inform you on the status of the connectors.
Within 5 seconds after the configured trigger occurs, the recipients of the notifications will receive a message with content customized by the user.
This key feature provides critical information for you to monitor and respond to the status of devices and connectors. For example, a notification can be set up to alert the failure to push data from UnaConnect to the end user platform, which could be caused by unreachable end user infrastructure or when a user modifies or deletes a connector.

To view the list of notifications for the devices in a group:
  1. Click on the Current Group dropdown menu on the left navigation bar to see a list of all device groups that can be accessed, then select from the list to switch to the Group Dashboard page of the device group.
  2. On the left navigation bar, click on the Notifications tab, and the Notifications page is displayed.
  3. On this page, the notification name, device type, device ID and title of the notification are displayed for each of the configured notification. It also displays the Subscribed Toggle to enable/disable the notification.

Flexible notification content settings allow you to configure highly flexible contents such as customized subject header and message body to provide you and others with relevant information to help you quickly respond to the situation. You may configure the notification contents with:

A customized text in the desired language that is fixed for all notification messages. For example: This is an alert for temperature out of threshold..

To receive the current temperature from a device sensor, you can also input variables in the content. For example: Current temperature is {temperature}.
Note: For all device types, the list of its variables available is:
  • deviceId
  • deviceName
  • groupId
  • deviceType
For a specific device type, please refer to the device data JSON file that you can find in the device data page.

For example: a button device that could have a short or long click can be configured to send the notifications as Order a {short_click=1:Pizza}{long_click=1:Coke}. In this example, you will Order a Pizza with a short click on the button, and Order a Coke with a long click on the button.
Note: In this method, the available operations are: =, >, <, >=, <=, !=

Here are some examples of the notification body if we wish to receive a { "temperature":10 } notification from a device ABC
It will trigger for the following contents:
  • Hi Valentin, the room is {temperature>=24:hot}{temperature<18:cold} ({temperature} °C). : "Hi Valentin, the room is cold (10°C)"
  • The temperature recorded by {deviceId} is {temperature} : "The temperature recorded by ABC is 10°C"
  • The temperature at home is {temperature>=32:really hot} {temperature<=10:really cold} : "The temperature at home is really cold"
  • 天氣很{temperature<15:冷} : "天氣很冷"
It will NOT be triggered for the following contents:
  • Hi Valentin, the temperature detected is {temperature>=24:hot} : It will not trigger because the temperature is lower than 10.
  • 天氣很{temperature>=24:熱} : It will not trigger because the temperature is lower than 10.
  • The button has been pressed {shortCount} times : It will not trigger because the data does not have the field shortCount
  • The button has been pressed {longCount>0:pressed} times: It will not trigger because the data does not have the field longCount
  • The temperature at home is {temperature>=32:really hot} {temperature<8:really cold}: It will not trigger because the temperature is not in the defined range.