Device Connection

Connectivity

  • Besides Java, supports MQTT-based connection SDK in C, Python, and Node JS. Users can select the suitable SDKs for device-side development. For more information, see EnOS™ IoT Device SDK

  • Added support for devices connecting to EnOS through HTTP or HTTPS. Devices are authenticated to HTTP broker with the product key, device key, and device secret. Connecting through the HTTP protocol is suitable for the following types of devices:

    • Devices unable to sustain connection for long due to the network or restricted bandwidth.
    • Devices that supports only the HTTP protocol.
    • Devices that needs to constantly upload file-type measurement points, such as a camera that sends video files.

    EnOS provides EnOS SDK for HTTP (java) and also supports customized protocol based on the EnOS-defined HTTP protocol.

    For more information, see HTTP-based Connection.

Model

  • Supports industry-standard model function libraries in defining a model. This ensures the standardization of model functions and consistency in data structure across models. Standardized model function libraries also facilitate uniformed data handling and application. Users can extend these libraries in their private cloud environments. For more information, see Thing Model.
  • In addition to importing and exporting model information in a JSON file, added support of editing model information by importing and exporting an Excel file to improve model management efficiency and ease of use. To use this feature, open the Model Details page for the model you want to edit, click Feature Definition, and click Export Model and Import Model. For more information, see Managing Models.

Device Management

  • Added support for updating device instance information using Excel documents, including device name, time zone, and attributes. Internationalization settings are supported for the device name.
  • Added support for adding or removing sub-devices of a gateway device in batch.
  • Added support for forwarding device data to multiple device instances. You can forward the data collected from one physical device to multiple device instances of the same model on EnOS Cloud. This can be used in scenarios where one physical device must be bound to several nodes on the same asset tree. For more information, see Forwarding Data From a Physical Device to Multiple Device Instances
  • Added support of logical asset management. You can manage your non-device assets created in Asset Tree in Asset Management > Logic Asset . Editing and deleting logical assets are supported for now. For more information, see Managing Asset Tree.
  • Supports searching for device asset by tag. A tag consists of a key and value in the form of Key : Value :
    • Supports searching with multiple tags. The relation between tags is OR. For example, if you search with two tags, Key1 : Value1 , Key2 : Value2, you are searching for devices with either Key1 : Value1 or Key2 : Value2 or both.
    • If you search with a tag whose value is left blank, all tags of the tag key you entered will be displayed as results. For example, if you search with Key3:(Value left blank), you are searching all tags with the key being Key3.

Alert

  • Added support for importing and exporting capabilities for alert severities, alert types, alert content, and alert rules to improve the efficiency for configuring alert services. For more information, see Managing Alerts in Batch.
  • Added support for the asset tree-based alert masking feature. By configuring this feature, you can receive only the alerts from the parent nodes and mask the alerts from all the child nodes so as to reduce the invalid alerts received by the application. For more information, see Masking Alert.
  • In alert rule, we added support of setting the attribute of a device as alert threshold. Devices of the same model may need alerts of different thresholds for the same measurement point in various scenarios. You can set the threshold as the attribute of a device when creating this device. Then, during creating an alert rule, select the attribute instead of a fixed value as the threshold to trigger the alert. For more information, see Tutorial: Setting Different Alert Thresholds for Devices of the Same Model.
  • Added support for setting an alert to be triggered when measurement points satisfying the alert rule is continuously reported for some time. In some scenarios, alerts need to be delayed until it persists for a specified time instead of being immediately triggered when there is an anomaly. You can set a triggering delay timer for these alert in alert rule. The timer starts when a measurement point satisfying the rule is reported. If subsequent measurement points continue to satisfy the rule, timer goes on. If any subsequent measurement point reported does not satisfy alert rule, the timer is reset. When the timer times out after the specified triggering delay, the alert is triggered. For more information, see Tutorial: Setting Alert Triggering Delay Timer.
  • Alerts based on device state are supported in alert rules. This type of alert is triggered once a device goes into a specific state. State-based alerts also support alert triggering delay and alert masking. Currently, only Offline can be configured for a state-based alert. For more information, see Tutorial: Setting State-based Alerts.