This article describes the error codes that IoT Platform may return to devices.

Common error codes

Table 1. General-purpose error codes
Error code Cause Solution
400 An error occurred while processing the request. Submit a ticket.
429 Traffic throttling is triggered due to frequent requests. Submit a ticket.
460 The data reported by the device is empty, the format of the parameter is invalid, or the number of parameters has reached the upper limit. Check the parameters based on the data formats that are described in the Alink protocol article.
500 An unknown error occurred in the system. Submit a ticket.
5005 An error occurred while querying the product information. Check the product information in the console and make sure that the ProductKey is valid.
5244 An error occurred while querying the metadata of the LoRaWAN-based product. Submit a ticket.
6100 An error occurred while querying the information about the specified device. Check the device information on the Devices page of the IoT Platform console.
6203 An error occurred while parsing the topic. Submit a ticket.
6250 An error occurred while querying the product information. Check the product information in the console and make sure that the ProductKey is valid.
6204 The specified device is disabled. You cannot perform operations on this device. Check the device status on the Devices page of the IoT Platform console.
6450 The method parameter is missing after the custom data is parsed to the standard Alink format. On the Device Log page of the console, or in the on-premises log file of the device, check whether the data reported by the device contains the method parameter.
6760 A system error occurred. Submit a ticket.
Table 2. Error codes about parsing scripts
Error code Cause Solution
26001 The system does not find a parsing script. Navigate to the Data Parsing tab in the console and make sure that the script has been submitted.
Note You cannot run scripts that are not submitted.
26002 The script runs properly, but the script content is invalid. For example, the script contains syntax errors. Use the same data to test the script. Check the error message and modify the script. We recommend that you test the script on an on-premises device before you submit the script to IoT Platform.
26006 The script runs properly, but the script content is invalid. The script must contain the protocolToRawData and rawDataToProtocol methods. An error occurs if these methods are missing. Navigate to the Data Parsing tab in the console and check whether the protocolToRawData and rawDataToProtocol methods exist.
26007 The script runs properly, but the format of the response is invalid. The script must contain the protocolToRawData and rawDataToProtocol methods. The protocolToRawData method must return a byte[] array, and the rawDataToProtocol method must return a JSON object. An error occurs if the response is not in the required format. Test the script in the console or on an on-premises device, and check whether the format of the response is valid.
26010 Traffic throttling is triggered due to frequent requests. Submit a ticket.
Table 3. Error codes about Thing Specification Language (TSL) models
Error code Cause Solution
5159 Failed to query the defined properties when the system verifies parameters based on the TSL model. Submit a ticket.
5160 Failed to query the defined events when the system verifies parameters based on the TSL model. Submit a ticket.
5161 Failed to query the defined services when the system verifies parameters based on the TSL model. Submit a ticket.
6207 The Alink data reported by the device or the data returned after the system parses the custom data is not in the JSON format. Follow the data formats described in the Device properties, events, and services article when you report data.
6300 The method parameter that is required by the Alink protocol does not exist in the standard Alink data or the parsed custom data reported by the device. On the Device Log page of the console, or in the on-premises log file of the device, check whether the data reported by the device contains the method parameter.
6301 When the system verifies parameters based on the TSL model, the data type is specified as an array. However, the type of data reported by the device is not an array. Navigate to the Define Feature tab in the console, and check the data type defined in the TSL model. Report data based on the required data type.
6302 The required input parameters of the service are not specified. Log on to the console and check the TSL model. Make sure that the required input parameters are specified.
6306 When the system verifies parameters based on the TSL model, the following errors may be found:
  • The data types of the input parameters are different from those defined in the TSL model.
  • The parameter values are not in the value range defined in the TSL model.
Log on to the console and check the TSL model. Make sure that the data types of the input parameters are the same as those defined in the TSL model, and the parameter values are within the value range defined in the TSL model.
6307 The input parameters do not comply with the 32-bit float data specifications defined in the TSL model. When the system verifies parameters based on the TSL model, the following errors may be found:
  • The data types of the input parameters are different from those defined in the TSL model.
  • The parameter values are not in the value range defined in the TSL model.
6308 The input parameters do not comply with the Boolean data specifications defined in the TSL model. When the system verifies parameters based on the TSL model, the following errors may be found:
  • The data types of the input parameters are different from those defined in the TSL model.
  • The parameter values are not in the value range defined in the TSL model.
6310 The input parameters do not comply with the text data specifications defined in the TSL model. When the system verifies parameters based on the TSL model, the following errors may be found:
  • The data types of the input parameters are different from those defined in the TSL model.
  • The length of the input parameters has reached the upper limit defined in the TSL model.
6322 The input parameters do not comply with the 64-bit float data specifications defined in the TSL model. When the system verifies parameters based on the TSL model, the following errors may be found:
  • The data types of the input parameters are different from those defined in the TSL model.
  • The parameter values are not in the value range defined in the TSL model.
6304 The input parameters cannot be found in the structure defined in the TSL model. Log on to the console and check the TSL model. Make sure that the data types of the input parameters are valid.
6309 The input parameters do not comply with the enumeration data specifications defined in the TSL model.
6311 The input parameters do not comply with the date data specifications defined in the TSL model. When the system verifies parameters based on the TSL model, the following errors may be found:
  • The data types of the input parameters are different from those defined in the TSL model.
  • The input data is not a UTC timestamp.
6312 The input parameters do not comply with the structure data specifications defined in the TSL model. When the system verifies parameters based on the TSL model, the following errors may be found:
  • The data types of the input parameters are different from those defined in the TSL model.
  • The number of the parameters contained in the structure is different from that defined in the TSL model.
6320 The specified property is not found when IoT Platform queries the TSL data of the device. Log on to the console and check whether the specified property exists in the TSL model. If the property does not exist, add the property.
6321 The identifier of the property, event, or service is not specified. Submit a ticket.
6317 The parameters required in the TSL model are not specified, such as the type and specs parameters. Submit a ticket.
6324 The input parameters do not comply with the array data specifications defined in the TSL model. When the system verifies parameters based on the TSL model, the following errors may be found:
  • The elements in the array do not follow the array syntax defined in the TSL model.
  • The number of elements in the array has reached the upper limit defined in the TSL model.
  • Go to the Product Details page of the IoT Platform console. On the Define Feature tab, check the array syntax defined in the TSL model.
  • View the logs reported by the device and check the number of elements in the array.
6325 The data types of the elements in the array are not supported by IoT Platform. Only the following data types of elements are supported: integer, 32-bit float, 64-bit float, double, text, and structure. Check whether the data types of the elements are supported by IoT Platform.
6326 The format of the time field reported by the device is invalid. Follow the data formats described in the Device properties, events, and services article when you report data.
6328 The value of the input parameter is not an array. Log on to the console and check the TSL model. Make sure that the data type of the input parameter is array.
System error codes
6318 An system error occurred while parsing the TSL model. Submit a ticket.
6313
6329
6323
6316
6314
6301

Error codes about device registration

  • Register directly connected devices

    Request topic: /sys/{productKey}/{deviceName}/thing/sub/register

    Error codes: 460, 5005, 5244, 500, 6288, 6100, 6619, 6292, and 6203

    The following table describes the causes and solutions of the errors that may occur when you register a directly connected device. For more information about other error codes, see the Common error codes section in this article.

    Error code Cause Solution
    6288 Dynamic registration is disabled for the device. Log on to the console and enable dynamic registration on the Product Details page.
    6619 The device has been bound to another gateway. Navigate to the Device Details tab in the console and check whether the device has been bound to a gateway.
  • Register directly connected devices based on unique-certificate-per-product authentication

    Error codes: 460, 6250, 6288, 6600, 6289, 500, and 6292

    The following table describes the causes and solutions of the errors that may occur when you dynamically register a directly connected device based on unique-certificate-per-product authentication. For more information about other error codes, see the Common error codes section in this article.

    Error code Cause Solution
    6288 Dynamic registration is disabled for the device. Log on to the console and enable dynamic registration on the Product Details page.
    6292 The algorithm that is used to calculate the signature is not supported by IoT Platform. Use an algorithm that is supported by the signMethod parameter. For more information, see Device registration.
    6600 An error occurred while verifying the signature. Use a supported algorithm to calculate a signature and then verify the signature. For more information, see Device registration.
    6289 The device has been activated. Log on to the console and check the status of the device.

Error codes about topological relationships

  • Add topological relationships

    Request topic: /sys/{productKey}/{deviceName}/thing/topo/add

    Error codes: 460, 429, 6402, 6100, 401, 6204, 6400, and 6203

    The following table describes the causes and solutions of the errors that may occur when you add a topological relationship between a gateway and a sub-device. For more information about other error codes, see the Common error codes section in this article.

    Error code Cause Solution
    401 Failed to verify the signature when you add the topological relationship. Use a supported algorithm to calculate a signature and then verify the signature. For more information, see Manage topological relationships.
    6402 The gateway and sub-device are the same device. When you add a topological relationship, you cannot add the current gateway to itself as a sub-device. View the information about all existing sub-devices, and check whether the gateway shares the same information with a sub-device.
    6400 The number of sub-devices that you add to the gateway has reached the upper limit. Log on to the console and check the number of existing sub-devices of the gateway on the Sub-device Management tab. For more information about the limits, see Limits.
  • Delete topological relationships

    Request topic: /sys/{productKey}/{deviceName}/thing/topo/delete

    Error codes: 460, 429, 6100, 6401, and 6203

    The following table describes the cause and solution of an error that may occur when you delete a topological relationship between a gateway and a sub-device. For more information about other error codes, see the Common error codes section in this article.

    Error code Cause Solution
    6401 The topological relationship does not exist. Log on to the console, click Devices in the left-side navigation pane, and then click the Sub-device Management tab on the Device Details page of the gateway. Then, you can view the information about the sub-device.
  • Obtain topological relationships

    Request topic: /sys/{productKey}/{deviceName}/thing/topo/get

    Error codes: 460, 429, 500, and 6203

    For more information about these error codes, see the Common error codes section in this article.

  • A gateway reports a detected sub-device

    Request topic: /sys/{productKey}/{deviceName}/thing/list/found

    Error codes: 460, 500, 6250, 6280, and 6203

    The following table describes the cause and solution of an error that may occur when a gateway reports a detected sub-device. For more information about other error codes, see the Common error codes section in this article.

    Error code Cause Solution
    6280 The name of the sub-device reported by the gateway is invalid. The name must be 4 to 32 characters in length and can contain letters, digits, and underscores (_). Check whether the name of the sub-device reported by the gateway is valid.

Error codes about sub-device connection and disconnection

  • A sub-device goes online

    Request topic: /ext/session/${productKey}/${deviceName}/combine/login

    Error codes: 460, 429, 6100, 6204, 6287, 6401, and 500

  • A sub-device goes offline

    Topic to which error messages are sent: /ext/session/{productKey}/{deviceName}/combine/logout_reply

    Error codes: 460, 520, and 500

  • A sub-device is forced to go offline

    Topic to which error messages are sent: /ext/error/{productKey}/{deviceName}

    Error codes: 427, 521, 522, and 6401

  • A sub-devices fails to send a message

    Topic to which error messages are sent: /ext/error/{productKey}/{deviceName}

    Error code: 520

The following table describes the causes and solutions of the errors that may occur when a sub-device goes online or offline. For more information about other error codes, see the Common error codes section in this article.

Error code Cause Solution
427 The device is forced to go offline because the device certificate is used by another device.
IoT Platform identifies a device only based on the device certificate (ProductKey, DeviceName, and DeviceSecret).
  • The same device certificate is burned on multiple devices.
  • The network or power supply of the device is unstable. The device is reconnected to IoT Platform immediately after an abrupt network outage or power failure. In this case, IoT Platform identifies the reconnected device as a new device. Even if the error message is returned, the device can work properly.
Navigate to the Device Details page in the console and check the time when the device was last connected to IoT Platform. You can determine whether the same device certificate information is used to connect another device to IoT Platform.
428 The number of sub-devices that you add to the specified gateway has reached the upper limit. You can add a maximum of 1,500 sub-devices to each gateway. Check the number of sub-devices that are added to the gateway.
521 The device has been deleted. Navigate to the Devices page in the console and check whether the device has been deleted.
522 The device has been disabled. Check the device status on the Devices page of the IoT Platform console.
520 An error occurred in the session between the sub-device and IoT Platform.
  • The specified session does not exist because the sub-device is not connected to IoT Platform, or the sub-device is already disconnected from IoT Platform.
  • The session exists, but the session is not established by using the current gateway.
6287 An error occurred while verifying the signature based on the ProductSecret or DeviceSecret. Use a supported algorithm to calculate a signature and then verify the signature. For more information, see Connect or disconnect sub-devices.
1914 The number of sub-devices to be connected to or disconnected from IoT Platform at a time has reached the upper limit. You can connect or disconnect a maximum of five sub-devices at a time. Check whether the number of sub-devices to be connected to or disconnected from IoT Platform at a time has reached the upper limit.
1913 The gateway is disconnected from IoT Platform. Check the reason why the gateway is disconnected from IoT Platform based on logs.

Error codes about properties, events, and services

  • A device reports properties
    • Request topic for pass-through data: /sys/{productKey}/{deviceName}/thing/model/up_raw
    • Request topic for Alink data: /sys/{productKey}/{deviceName}/thing/event/property/post

    Error codes: 460, 500, 6250, 6203, 6207, 6313, 6300, 6320, 6321, 6326, 6301, 6302, 6317, 6323, 6316, 6306, 6307, 6322, 6308, 6309, 6310, 6311, 6312, 6324, 6328, 6325, 6200, 6201, 26001, 26002, 26006, and 26007

    The following table describes the cause and solution of an error that may occur when a device reports properties. For more information about other error codes, see the Common error codes section in this article.

    Error code Cause Solution
    6106 The number of properties reported by the device has reached the upper limit. A device can report a maximum of 200 properties at a time. Log on to the console, choose Maintenance > Device Log, and then check the number of properties reported by the device. You can also check the information in the on-premises log file of the device.
  • A device reports events
    • Request topic for pass-through data: /sys/{productKey}/{deviceName}/thing/model/up_raw
    • Request topic for Alink data: /sys/{productKey}/{deviceName}/thing/event/{tsl.identifier}/post

    Error codes: 460, 500, 6250, 6203, 6207, 6313, 6300, 6320, 6321, 6326, 6301, 6302, 6317, 6323, 6316, 6306, 6307, 6322, 6308, 6309, 6310, 6311, 6312, 6324, 6328, 6325, 6200, 6201, 26001, 26002, 26006, and 26007

    For more information about these error codes, see the Common error codes section in this article.

  • A gateway reports data of multiple sub-devices at a time
    • Request topic for pass-through data: /sys/{productKey}/{deviceName}/thing/model/up_raw
    • Request topic for Alink data: /sys/{productKey}/{deviceName}/thing/event/property/pack/post

    Error codes: 460, 6401, 6106, 6357, 6356, 6100, 6207, 6313, 6300, 6320, 6321, 6326, 6301, 6302, 6317, 6323, 6316, 6306, 6307, 6322, 6308, 6309, 6310, 6311, 6312, 6324, 6328, 6325, 6200, 6201, 26001, 26002, 26006, and 26007

    The following table describes the causes and solutions of the errors that may occur when the gateway reports data of multiple sub-devices at a time. For more information about other error codes, see the Common error codes section in this article.

    Error code Cause Solution
    6401 The topological relationship does not exist. Navigate to the Sub-device Management tab in the console and check the information about the sub-device.
    6106 The number of properties reported by the device has reached the upper limit. A device can report a maximum of 200 properties at a time. Log on to the console, choose Maintenance > Device Log, and then check the number of properties reported by the device. You can also check the information in the on-premises log file of the device.
    6357 The amount of data reported by the gateway has reached the upper limit. A gateway can report data of up to 20 sub-devices at a time. Check the data records in the on-premises log file of the device.
    6356 The number of events reported by the gateway has reached the upper limit. A gateway can report a maximum of 200 events at a time. Check the data records in the on-premises log file of the device.

Error codes about desired device property values

  • A device obtains desired property values

    Request topic: /sys/{productKey}/{deviceName}/thing/property/desired/get

    Error codes: 460, 6104, 6661, and 500

    The following table describes the causes and solutions of the errors that may occur when you manage desired device property values. For more information about other error codes, see the Common error codes section in this article.

    Error code Cause Solution
    6104 The number of properties contained in the request has reached the upper limit. A request can contain a maximum of 200 properties. Log on to the console, choose Maintenance > Device Log, and then check the number of properties in the reported data. You can also check the information in the on-premises log file of the device.
    6661 An error occurred while querying the desired property values. A system error occurred. Submit a ticket.
  • A device clears desired property values

    Request topic: /sys/{productKey}/{deviceName}/thing/property/desired/delete

    Error codes: 460, 6104, 6661, 500, 6207, 6313, 6300, 6320, 6321, 6326, 6301, 6302, 6317, 6323, 6316, 6306, 6307, 6322, 6308, 6309, 6310, 6311, 6312, 6324, 6328, and 6325

Error codes about device tags

  • A device reports tag information

    Request topic: /sys/{productKey}/{deviceName}/thing/deviceinfo/update

    Error codes: 460 and 6100

  • A device deletes tag information

    Request topic: /sys/{productKey}/{deviceName}/thing/deviceinfo/delete

    Error codes: 460 and 500

Error codes about obtaining TSL models

Request topic: /sys/{productKey}/{deviceName}/thing/dsltemplate/get

Error codes: 460, 5159, 5160, and 5161

Error codes about requesting update package information

Request topic: /ota/device/request/${YourProductKey}/${YourDeviceName}

Note The topic used to obtain update package information is the same as that used to return responses.

Error codes: 429, 9112, and 500

The following table describes the cause and solution of an error that may occur when a device requests the update package information. For more information about other error codes, see the Common error codes section in this article.

Error code Cause Solution
9112 Failed to query information about the specified device. On the Devices page of the IoT Platform console, check whether the device information is valid.

Error codes about requesting configuration information

Request topic: /sys/{productKey}/{deviceName}/thing/config/get

Error codes: 460, 500, 6713, and 6710

The following table describes the causes and solutions of the errors that may occur when a device requests the configuration information. For more information about other error codes, see the Common error codes section in this article.

Error code Cause Solution
6713 Remote configuration services are unavailable. The remote configuration feature of the specified product is disabled. Log on to the console, choose Maintenance > Remote Config, and then enable the remote configuration feature for the specified product.
6710 Failed to query the remote configuration information. Log on to the console, choose Maintenance > Remote Config, and then check whether you have edited the configuration file for the specified product.