Devices

By using the JSON script, you can add template without following the all UI steps. Below are the sample JSON for quickly adding the template. Read more.

{
  "code": "CODE",
  "name": "NAME",
  "tag": "TAG(to enable GatewaySupport) | NULL",
  "attributes": [
    {
      "name": "attr",
      "type": "number | string",
      "tag": "TAG(if GatewaySupport enabled) | NULL"
    },
    {
      "name": "parent",
      "type": "object",
      "tag": "TAG(if GatewaySupport enabled) | NULL",
      "childs": [
        {
          "name": "childattr",
          "type": "number | string"
        }
      ]
    }
  ]
}

Yes, IoTConnect provides the twin property on template edit details where you can pass your default settings or constant value to device firmware while device connect with IotConnect for the first time. Read more.

By default, the system will be retained 90 days data for your history, but you can contact us if you want it more.

There many reasons behind not receiving telemetry data. The below are a few points that need to check to find out the problem.

Wrong MQTT configuration or wrong connection string
Port is not enabled on network settings
Wrong configuration on Azure IoT Hub
Wrong Topic
Timezone on server and your profile is different
Wrong JSON format

IoTConnect provides for end customers to create Custom Fields based on requirement in User/Device/Entity level. To add Custom Fields, visit knowledge base.

For example, if you want to add Title Field which consist of Mr., Mrs. or Miss value, you can create Custom Field with “Select” option and add all possible value on it.

IoTConnect has a feature to add large numbers of devices by using the batch import module, read more.

There are a huge numbers of different hardware types, firmware versions, revisions and other variations of devices that are available in the IoT market. It is very much difficult to ensure plug and play compatibility with each and every device available in the market but we ensure you to help in making the most of the devices compatible with your system. please check out article to get more details.

SDK integration consists of 3 parts.

1. Initialize / Create IoTConnectSDK Object
2. Send Data
3. Receive Data / Callback function

All cloud communication happens through this. Go to our Client Libraries and SDK page for more information.

It simulates any devices for the defined interval and duration of the time. You can simulate hundreds of virtual connected devices, without having to configure and manage physical devices. To learn more, please click here.

No, you can as many attributes as you want on your devices.

Before creating a device, you should have at least one entity and device template. You can refer to our how-to guide on devices for more details.