Name | A unique identifier to identify your device. For this illustration, the name MyTRB Gateway01 is provided. |
Description | Additional Information about your device. |
Type | The function of your device, if its a gateway or smart sensor or a peripheral. Since the TRB245 is a gateway device, Gateway option will only be available. |
Device Application | The application running on your physical device. For this illustration we will select Manufacturer defined. |
Authentication Type | The security level of the MQTT connection between the physical device and the Zoho IoT application. Root CA and Client Certificate for a connection will become available only if the appropriate option is selected. It is recommended you use TLS for actual implementation and Non-TLS for testing. For this illustration, the TLS is option is selected. |
Data Interval | The frequency of time in minutes the application should wait for the device to send information to the application before the connection is timed out and disconnected. For this illustration, a Keep Alive Interval of 15 mins is assigned. |
Edge Key | A key to identify the particular device in the payload consisting of information about multiple devices. Since we are adding a device instance for a gateway device, the field is left blank for this illustration. |
Name | A name for your device product. |
Description | Additional information about your device product can be provided here. |
Manufacturer Name | The manufacturer of your physical Device. Unlike other field, The Manufacturer field takes a Manufacturer Module Instance as the input, For that you have separately create manufacturer first as show here. For now, it is advisable you simply leave this field empty. |
Device Type | The function of your device must be selected here. Gateway: If your physical device is a gateway device that collects data from various sensors and peripherals and send it to the application. Smart Sensor: The device collects data and is capable of directly sending it to the application. Peripheral: The physical device can only collect data and send it to a gateway device and not directly to the application. Since we are adding a Gateway Device, Select the Gateway Option. |
Compatible Device Application | This indicates the type of application running on your physical device. Manufacturer defined: The application is provided by the device manufacturer themselves. Custom Application: You have built your own application using various SDKs to run on the device. For this illustration, we will select custom application and manufacturer defined as both is possible for a gateway device. But only one option will be selected while adding the device instance. |
Device Connectivity | Select the protocol with which your gateway device will communicate with the Zoho IoT application. Here, if your device can support both MQTT and HTTPS, you can select both. Selecting both will give you the option to select which device protocol your device instance will use. Only one can be selected while adding the device instance. For this example we will select only MQTT as the device considered for this illustration can only connect using MQTT. |
Name | A unique identifier to identify your device. For this illustration, the name MyGateway01 is provided. |
Description | Additional Information about your device. |
Type | The function of your device, if it's a gateway or smart sensor or a peripheral. Since we defined the Device product as a gateway, only the Gateway option will be available and selected by default. |
Device Application | The application running on your physical device. For this illustration, we will select Custom Application, assuming that you have built your own device application. If your device runs a Manufacturer defined application, then select Manufacturer Defined. |
Authentication Type | The security level of the MQTT connection between the physical device and the Zoho IoT application. Root CA and Client Certificate for a connection will become available only if the appropriate option is selected. It is recommended you use TLS for actual implementation and Non-TLS for testing. For this illustration, the TLS is option is selected. |
Data Interval | The frequency of time in minutes the application should wait for the device to send information to the application before the connection is timed out and disconnected. For this illustration, a Keep Alive Interval of 15 mins is assigned. |
Edge Key | A key to identify the particular device in the payload consisting of information about multiple devices. Since it's a gateway device, the field is left blank. |
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.