FAQ about TSL models

Issue

Verification errors occur when you import a TSL model file, as shown in the following figure.

Solution

To fix the verification errors, use the following solutions:

• Solution 1: Check the format of the TSL model file and make sure that the file is in the JSON format.

• Solution 2: Click Download and View to obtain an errors.txt file. Troubleshoot and resolve the issues based on the errors.txt file.

  For more information about the errors.txt file, see the following sample file.

  Sample TSL model file:

  {
      "schema":"https://iotx-tsl.oss-ap-southeast-1.aliyuncs.com/schema.json",
      "profile":{
          "productKey":"a1Jk***"
      },
      "services":[],
      "properties": 1,
      "events": [],
      "functionBlockId": "**mtest",
      "functionBlockName": "Custom module 1"
  }

  Sample errors.txt file:

  [
    {
      "path": [
        "properties"
      ],
      "property": "instance.properties",
      "message": "is not of a type(s) array",
      "schema": {
        "type": "array",
        "items": {
          "$ref": "#/definitions/propertyDefinition"
        }
      },
      "instance": 1,
      "name": "type",
      "argument": [
        "array"
      ],
      "stack": "instance.properties is not of a type(s) array"
    },
    {
      "path": [
        "functionBlockId"
      ],
      "property": "instance.functionBlockId",
      "message": "does not match pattern \"^[_a-zA-Z0-9]{1,30}$\"",
      "schema": {
        "type": "string",
        "pattern": "^[_a-zA-Z0-9]{1,30}$"
      },
      "instance": "**mtest",
      "name": "pattern",
      "argument": "^[_a-zA-Z0-9]{1,30}$",
      "stack": "instance.functionBlockId does not match pattern \"^[_a-zA-Z0-9]{1,30}$\""
    }
  ]

  Parameter	Description

  Parameter	Description
  path	The path of the error. In this example, the following errors are detected: // The value of the properties parameter is not an array. "path": [ "properties" ] // The value of the functionBlockId parameter contains invalid characters. "path": [ "functionBlockId" ]
  property	The invalid property in "path". For example, in "path": ["functionBlockId" ], the value of the instance.functionBlockId property is invalid.
  message	The error message. For example, in "path": ["functionBlockId" ], the error message does not match pattern \"^[_a-zA-Z0-9]{1,30}$\" is returned for the instance.functionBlockId property.
  schema	The rule that is used to verify the TSL model file. For example, in "path": ["functionBlockId" ], the type and pattern rules are used. For more information about the rules, see schema.
  instance	The object that is verified. For example, in "path": ["functionBlockId" ], the setting of "functionBlockId": "**mtest" is verified.
  name	The name of the rule that is not matched in the verification. For example, in "path": ["functionBlockId" ], the value of **mtest does not match the pattern rule.
  argument	The content of the rule that is not matched in the verification. For example, in "path": ["functionBlockId" ], the content of the pattern rule is ^[_a-zA-Z0-9]{1,30}$.
  stack	The concatenated values of the property and message parameters.

For more information, see jsonschema.

The following table describes the differences.

After devices submit property data, historical data, or multiple values of properties, IoT Platform generates data records based on the timestamps.

Differences between communication topics and data formats

Topics and data formats vary based on the type of data that is submitted to IoT Platform. For more information, see Devices submit property data to IoT Platform, Devices submit historical TSL data to IoT Platform, and Devices submit multiple properties and events to IoT Platform at a time.

Examples

In this example, the data of the temperature property is submitted by a device to IoT Platform.

• The device submits snapshot values of the temperature property.

  1. The device submits the following values of the temperature property with timestamps from left to right in sequence.

     13:00	14:00	15:00	15:10

     13:00	14:00	15:00	15:10
     60	70	80	90

  2. The device submits the snapshot value 100 of the temperature property. The following data is displayed based on the method that the device uses to submit data.

     • If no timestamps exist, IoT Platform generates a timestamp based on the time when the data is submitted. In this example, 15:30:00 is used. In this case, 100 is displayed in the IoT Platform console as the value of the temperature property. The value 100 is also the most recent value of the temperature property in the data records.

     • If a timestamp (for example, 15:00:00) is specified, 100 replaces 80 as the value of the temperature property at 15:00:00. In this case,100 is displayed in the IoT Platform console as the value of the temperature property. The most recent value of the temperature property in the data records is 90 at 15:10:00.

• The device submits historical values of the temperature property.

  1. The device submits the following historical values of the temperature property at the same time.

     13:00	14:00	15:00	15:10

     13:00	14:00	15:00	15:10
     60	70	80	90

  2. The device submits the following historical values of the temperature property at the same time.

     13:10	14:10

     13:10	14:10
     100	200

     The most recent temperature value that is written to the database is displayed in the IoT Platform console as the value of the temperature property. In this example, 100 at 13:10:00 is displayed or 200 at 14:10:00 is displayed. The most recent value of the temperature property in the data records is 90 at 15:10:00.