IoT Platform:Error codes for devices

Common error codes

Error codes for device registration

• Register directly connected devices

  • Request topic: /sys/${productKey}/${deviceName}/thing/sub/register
  • Response topic: /sys/${productKey}/${deviceName}/thing/sub/register_reply

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

  The following table describes the causes of and solutions to 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 of this topic.

  Error code	Cause	Troubleshooting
  6288	Dynamic registration is disabled for the device.	Log on to the IoT Platform console and enable dynamic registration on the product details page.
  6619	The device is bound to another gateway.	Go to the Device Details tab in the IoT Platform console and check whether the device is bound to a gateway.

• Dynamically register directly connected devices based on unique-certificate-per-product verification

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

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

  Error code	Cause	Troubleshooting
  6288	Dynamic registration is disabled for the device.	Log on to the IoT Platform 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 Register devices.
  6600	The system failed to verify the signature.	Use a supported algorithm to calculate a signature and then verify the signature. For more information, see Register devices.
  6289	The device is activated.	Log on to the IoT Platform console and check the status of the device.

Error codes for topological relationships

• Add topological relationships

  • Request topic: /sys/${productKey}/${deviceName}/thing/topo/add
  • Response topic: /sys/${productKey}/${deviceName}/thing/topo/add_reply

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

  The following table describes the causes of and solutions to 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 of this topic.

  Error code	Cause	Troubleshooting
  401	The system 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 as its sub-device.	View 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 exceeds the limit.	Log on to the IoT Platform 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
  • Response topic: /sys/${productKey}/${deviceName}/thing/topo/delete_reply.

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

  The following table describes the cause and solution of the 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 of this topic.

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

• Obtain topological relationships

  • Request topic: /sys/${productKey}/${deviceName}/thing/topo/get
  • Response topic: /sys/${productKey}/${deviceName}/thing/topo/get_reply

  Error codes: 460, 429, 500, and 6203

  For more information about the error codes, see the "Common error codes" section of this topic.

• A gateway submits information about a detected sub-device

  • Request topic: /sys/${productKey}/${deviceName}/thing/list/found
  • Response topic: /sys/${productKey}/${deviceName}/thing/list/found_reply

  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 submits information about a detected sub-device. For more information about other error codes, see the "Common error codes" section of this topic.

  Error code	Cause	Troubleshooting
  6280	The sub-device name submitted 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 sub-device name submitted by the gateway is valid.

Error codes for sub-device connections and disconnections

• A sub-device goes online

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

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

• 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-device fails to send a message

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

  Error code: 520

• A gateway fails to submit multiple messages from sub-devices to IoT Platform

  Topic to which error messages are sent: /sys/${productKey}/${deviceName}/proxy/batch_post_reply

  Error code: 9242

The following table describes the causes of and solutions to 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 of this topic.

Error codes for properties, events, and services

• A device submits properties

  • Pass-through data format:

    • Request topic: /sys/{productKey}/{deviceName}/thing/model/up_raw

    • Response topic: /sys/${productKey}/${deviceName}/thing/model/up_raw_reply

  • Alink data format:

    • Request topic: /sys/${productKey}/${deviceName}/thing/event/property/post

    • Response topic: /sys/${productKey}/${deviceName}/thing/event/property/post_reply

  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 the error that may occur when a device submits properties. For more information about other error codes, see the "Common error codes" section of this topic.

  Error code	Cause	Troubleshooting
  6106	The number of properties that are submitted by the device exceeds the limit. A device can submit up to 200 properties at the same time.	Log on to the IoT Platform console, choose Maintenance > Device Log, and then check the number of properties that are submitted by the device. You can also check the information in the on-premises log file of the device.

• A device submits events

  • Pass-through data format:

    • Request topic: /sys/{productKey}/{deviceName}/thing/model/up_raw

    • Response topic: /sys/${productKey}/${deviceName}/thing/model/up_raw_reply

  • Alink data format:

    • Default module

      • Request topic: /sys/${productKey}/${deviceName}/thing/event/${tsl.event.identifier}/post

      • Response topic: /sys/${productKey}/${deviceName}/thing/event/${tsl.event.identifier}/post_reply

    • Custom module

      • Request topic: /sys/${productKey}/${deviceName}/thing/event/${tsl.functionBlockId}:${tsl.event.identifier}/post

      • Response topic: /sys/${productKey}/${deviceName}/thing/event/${tsl.functionBlockId}:${tsl.event.identifier}/post_reply

  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 the error codes, see the "Common error codes" section of this topic.

• A gateway submits the data of multiple sub-devices at the same time

  • Pass-through data format:

    • Request topic: /sys/{productKey}/{deviceName}/thing/model/up_raw

    • Response topic: /sys/${productKey}/${deviceName}/thing/model/up_raw_reply

  • Alink data format:

    • Request topic: /sys/${productKey}/${deviceName}/thing/event/property/pack/post

    • Response topic: /sys/${productKey}/${deviceName}/thing/event/property/pack/post_reply

  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 of and solutions to the errors that may occur when the gateway submits the data of multiple sub-devices at the same time. For more information about other error codes, see the "Common error codes" section of this topic.

  Error code	Cause	Troubleshooting
  6401	The topological relationship does not exist.	Go to the Sub-device Management tab in the IoT Platform console and check the information about the sub-device.
  6106	The number of properties that are submitted by the device exceeds the limit. A device can submit up to 200 properties at the same time.	Log on to the IoT Platform console, choose Maintenance > Device Log, and then check the number of properties submitted by the device. You can also check the information in the on-premises log file of the device.
  6357	The amount of data submitted by the gateway exceeds the limit. A gateway can submit the data of up to 20 sub-devices at the same time.	Check the data records in the on-premises log file of the device.
  6356	The number of events submitted by the gateway exceeds the limit. A gateway can submit up to 200 events at the same time.	Check the data records in the on-premises log file of the device.

Error codes that may appear when devices specify desired device property values

• A device obtains desired property values

  • Request topic: /sys/${productKey}/${deviceName}/thing/property/desired/get
  • Response topic: /sys/${productKey}/${deviceName}/thing/property/desired/get_reply

  Error codes: 460, 6104, 6661, and 500

  The following table describes the causes of and solutions to 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 of this topic.

  Error code	Cause	Troubleshooting
  6104	The number of properties contained in the request exceeds the limit. A request can contain up to 200 properties.	Log on to the IoT Platform console, choose Maintenance > Device Log, and then check the number of properties in the submitted data. You can also check the information in the on-premises log file of the device.
  6661	The system failed to query the desired property values. A system exception occurred.	Submit a ticket.

• A device clears desired property values

  • Request topic: /sys/${productKey}/${deviceName}/thing/property/desired/delete
  • Response topic: /sys/${productKey}/${deviceName}/thing/property/desired/delete_reply

  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 for device tags

• A device submits tag information

  • Request topic: /sys/${productKey}/${deviceName}/thing/deviceinfo/update
  • Response topic: /sys/${productKey}/${deviceName}/thing/deviceinfo/update_reply

  Error codes: 460 and 6100

• A device deletes tag information

  • Request topic: /sys/${productKey}/${deviceName}/thing/deviceinfo/delete
  • Response topic: /sys/${productKey}/${deviceName}/thing/deviceinfo/delete_reply

  Error codes: 460 and 500

Error codes that may appear when devices obtain TSL models

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

• Response topic: /sys/${productKey}/${deviceName}/thing/dsltemplate/get_reply

Error codes: 460, 5159, 5160, and 5161

Error codes that may appear when devices request update package information

• Request topic: /sys/${productKey}/${deviceName}/thing/ota/firmware/get

• Response topic: /sys/${productKey}/${deviceName}/thing/ota/firmware/get_reply

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 of this topic.

Error codes that may appear when devices request configuration data

• Request topic: /sys/${productKey}/${deviceName}/thing/config/get
• Response topic: /sys/${productKey}/${deviceName}/thing/config/get_reply

Error codes: 460, 500, 6713, and 6710

The following table describes the causes of and solutions to the errors that may appear when a device requests the configuration data. For more information about other error codes, see the "Common error codes" section of this topic.