This document provides a detailed overview of the various fields you will encounter when creating a device instance in the Zoho IOT application.
Field Name | Description |
Model | The specific model on which the device creation is based.
Learn more about device models. |
Product | Represents the device product for the device you are adding.
Learn more about device products. |
Name | A label to identify your device. |
Description | A brief description of the device. |
Device Type | Choose the type of device—gateway, peripheral, or smart sensor.
Learn more about device types. |
Device Connectivity | The protocol used for device communication with the Zoho IOT application. |
Device Application | The system software running on your hardware.
Custom Application: System software developed using any SDK of your choice.
Edge Agent: System software developed and provided by Zoho IOT. Manufacture Defined: System software developed and provided by the device's manufacturer. |
Authentication Type | The method used for device communication authentication.
Learn more about authentication types. |
Data Interval | The frequency at which the device sends data. |
Edge Key | A unique key to identify the instance at the device level in the incoming message/command payloads. |
DevEUI | A 64-bit unique identifier assigned by the manufacturer or owner of the device. |
LoRaWAN Datastream | The connector for the LoRa Network Server (LNS) in which the device is managed. |
Connected Asset | The asset added in the Zoho IOT application to which the sensor/device is attached to. |
Connected Gateway | The device added in the Zoho IOT application, which represents the gateway the peripheral device is connected to in the real world. |
Based on the type of device, the fields for adding a device instance vary. An example for each device type and how the field is configured is given below.
Gateway type
Example: Configuring a Raspberry Pi 4 to serve as a gateway device that communicates with the Zoho IoT application using the MQTT protocol.
Model: "Home Gateway" - the device is based on the model called Home Gateway.
Name: "My RPi" - Name used to identify the device in the application.
Description: "A Raspberry Pi used as a gateway device in a home automation set up" - The description provides added information about the device.
Type: "Gateway" - The raspberry pi device acts as a gateway that gathers information from various sensors and sends it to the Zoho IOT application.
Device Connectivity: "MQTT" - The raspberry pi will communicate with the Zoho IOT application using the MQTT protocol.
Device Application: "Custom Application," the system software that runs on the Raspberry Pi, is a custom application developed by a user.
Authentication Type: "Security Token with TLS" - The authentication type used for device communication.
Data interval: "5", The rasberry pi will send information to the Zoho IOT application every 5 minutes.
Edge Key: "myrpi_livingroom", this edge key allows the device My RPi to use only the data under the payload with the id myrpi_living room.
Here is an example of the payload,
Smart Sensor type
Example: Setting up an AM308 Milesight, a LoRaWAN-based sensor, connected to TheThingsNetwork. Model: "IAQ", the device instance is based on the model called IAQ.
Name: "AM308 R1" - Tag identifying the device in the application.
Description: "A sensor to measure the room climate in the dining room". - Additional information about the device.
Type: "Smart Sensor", -The device collects and directly communicates data to the Zoho IOT application.
Device Connectivity: "LoRaWAN via LoRaWAN Datastream" - Information regarding the LoRa device is communicated to the Zoho IOT application using a datastream.
DevUI: "24Exxxxxxxx06122" - Sixteen digit ID provided with in the device information of the milesight device.
LoRa Datastream: "TTN - Room Monitoring" - Datastream in the Zoho IOT application that connects to TheThingsNetwork LoRa Network Server.
Data interval: "10" - data about the device will be fetched every 10 minutes by the Zoho IOT application.
Peripheral Sensor type
Example: Adding a CONZERV EM6400 energy meter to the Zoho IoT application, which communicates with its gateway device via the Modbus RTU Protocol. Model: "Energy Meter" - the device is based on the model called Energy Meter.
Name: "Energy Meter Living room" - Name used to identify the device.
Description: "Energy Meter that measure the electricity values of the living room" - Information of what the energy meter does.
Type: "Peripheral Sensor" - The energy meter needs to connect to a gateway device to send information to the Zoho IOT application.
Device Connectivity: "Peripheral Communication via Gateway" - The peripheral can only communicate to the Gateway Device.
Peripheral Protocol: "Modubus RTU" - the protocol with which the energy meter communicates with the Raspberry Pi (Gateway device of the energy meter).
Connected Gateway: My RPi, the device representation of the Raspberry Pi gateway device in the Zoho IOT application.
Data Interval: "5", Data about the he peripheral device is sent to the application every 5 minutes.
See Also