Configuring fields: Device products
This document provides a detailed overview of the various fields you will encounter when creating a custom device product in the Zoho IOT application.
The field values specified during the configuration of a device product are not permanent characteristics of the device itself; instead, they appear as selectable options when adding the device. When multiple options are available for a device product, only one option from those selected can be used to create a device instance.
For example, when selecting the device connectivity option during the creation of a custom device product, you might choose both MQTT and HTTPS, indicating that the device product supports both communication protocols. However, when creating a device based on this product, you must choose either MQTT or HTTPS as the connectivity protocol of that device.
For example, when selecting the device connectivity option during the creation of a custom device product, you might choose both MQTT and HTTPS, indicating that the device product supports both communication protocols. However, when creating a device based on this product, you must choose either MQTT or HTTPS as the connectivity protocol of that device.
Field Name | Description |
Name | A label to identify your device. |
Description | A brief description of the device. |
Device Type | |
Compatible Device Connectivity | The protocol used for device communication with the Zoho IOT application. |
Compatible Device Application | The system software running on your hardware. Custom Application: System software developed using various SDKs. Edge Agent: System software developed and provided by Zoho IOT. Manufacture Defined: System software developed and provided by the device's manufacturer. |
Peripheral Protocol | The protocol used by the peripheral sensor to communicate with the gateway. |
Based on the device type of the custom device product, the fields will vary. An example for each device type and how the field is configured is given below.
Gateway
Example: Configuring a Arduino PLC as a custom device product to serve as a gateway device that supports both MQTT and HTTPS connectivity protocols.
- Name: "Arduino PLC" - Name to identify the device product in the Zoho IOT Application.
- Description: "A custom-made gateway device based on Arduino" - A brief description or added details about the device product.
- Manufacturer Name: "None" - The manufacturer of the product must be provided. The Manufacturer field is a Lookup field, and can be used to filter products and instances based on a manufacturer.
Note: Adding a manufacturer instance in the application is optional, especially if registering a product for the first time. Learn more about the manufacturer module.
- Device Type: "Gateway " - The Arduino PLC is capable of connecting with multiple sensors and transmitting details to the cloud over a network, and is categorised as a gateway device.
- Compatible Device Application: "Custom Application, Manufacturer Defined" - The system software for this is provided by the manufacturer, and it is also possible to create custom system software for specific needs and connect with the Zoho IOT application, so both options are selected.
- Compatible Device Connectivity: "MQTT, HTTPS" - Support for both MQTT and HTTPS communication protocols is possible for the device product.
Peripheral Sensor
Example: Configuring Selec Digital Electric meter as a custom device product of the peripheral sensor type.
- Name: "EM4M" - Name to identify the device product in the Zoho IOT Application.
- Description: "A digital energy meter capable of monitoring Current, Voltage, and Power." - A brief description or added details about the custom device product.
- Manufacturer Name: "None" - The manufacturer of the product must be provided. The Manufacturer field is a Lookup field, and can be used to filter products and instances based on a manufacturer.
- Device Type: "Peripheral Sensor" - The Selec digital meter is capable of monitoring various electric parameters but cannot send them to the cloud application, hence it is categorised under the Peripheral Sensor type
- Peripheral Protocol: "Modbus RTU, Modbus TCP" - The energy meter can communicate measured data to the gateway device using only the Modbus RTU protocol and RS485.
Smart Sensor
Example: Configuring an Enless Temperature and Humidity Sensor, a LoRaWAN-based sensor, connected to TheThingsNetwork.
- Name: "T&H AMB" - Name to identify the device product in the Zoho IOT Application.
- Description: "A smart sensor capable of monitoring indoor temperature and humidity." - A brief description or added details about the custom device product.
- Manufacturer Name: "None" - The manufacturer of the product must be provided. The Manufacturer field is a Lookup field, and can be used to filter products and instances based on a manufacturer.
- Device Type: "Smart Sensor" - The Enless T&H AMB is capable of measuring temperature and humidity data and communicate it directly to the cloud. Hence, it is categorised under the Smart Sensor type
- Compatible Device Connectivity: "LoRaWAN via LoRaWAN Datastream" - the product uses LoRa technology to connect to the LoRa Network Server and a datastream is used to connect the server with the Zoho IOT application.
- Message Formatter: A custom function to convert the data generated by the lora device to a readable format in the Zoho IOT application. This is not mandatory while creating a custom device product and can be configured at a later stage.
See Also