Device Message 2.1
Overview
IoTConnect platform provides various flavors of SDKs, however, it may be a case where these SDKs are not fit for your device due to memory or hardware limitations.
IoTConnect provides you to build your own SDKs using the protocol which IoTConnect SDKs are using. You can find detailed documentation on workflow and all the minor things that you need to take care of while building your own SDKs.
Below is the Developer Document to build SDK of any language that supports your device.
Discovery API
To start the process you need to call the discovery API by passing a few parameters to fetch Identity Endpoint. For this, You need CPID or SID, IOTConnect-supported language, version, and environment.
Identity API
On the success of the Discovery Call, you will get the URL of the Identity API. This API will provide additional values required to establish the device connection, send telemetry data, etc.
Device Identity Messages
To retrieve more information on attributes, settings/shadow, rules, etc device must send JSON with a specific message type.
IoTConnect SDK
- Get Device Hello Message
- Get Device Template Attributes
- Get Device Template Setting/Shadow
- Get Edge Rule
- Get Child Devices
- Get Pending OTA(s)
- Get Pending Command(s)
- Get Pending OTA(s) & Command(s)
- Create Child Device
- Delete Child Device
Device to Cloud (D2C) messages
This article merely provides the message data structures for the D2C communication with IoTConnect Device SDK or Bring your own Custom SDK.
IoTConnect SDK
Cloud to Device (C2D) messages
This article merely provides the message data structures for the C2D communication with IoTConnect Device SDK or Bring your own Custom SDK.
IoTConnect SDK
Reference Table
This article merely provides troubleshooting & response codes.