Datapoint import conflicts
While associating a device product to a device model, you may encounter issues and warnings due to conflicts in datapoints. Associating multiple device products to the same model comes with limitations based on the datapoints involved. Below are some key limitations:
- Common Datapoint Requirement: Associating more than one device product to a model requires at least one common datapoint between the device products.
- Datapoint Group Consistency: If two device products share a datapoint name, they must also be from the same datapoint group. Associating products from different groups with the same datapoint name is not permitted.
- Gateway Device Type Exception: Device products classified under the Gateway device type can be associated with any model regardless of common datapoints, with the only restriction being a conflict in the datapoint name from different groups.
Understanding these limitations will help prevent errors while creating devices in the application.
A tabulation of association possibilities to a device model.
To be Associated Device Type | Already Associated Device type | Requirement |
Smart sensor/ Peripheral | Smart sensor/ Peripheral | At least one common Datapoint from the same group. |
Smart sensor/ Peripheral | Gateway | No common datapoint Required. If a common datapoint exists, the datapoints must be from the same group. |
Gateway | Smart sensor/ Peripheral | No common datapoint Required. If a common datapoint exists, the datapoints must be from the same group. |
Gateway | Gateway | No common datapoint Required. If a common datapoint exists, the datapoints must be from the same group. |
Here is an explanation of these limitations with examples.
Common Datapoint Requirement
Consider the scenario with a device model named Building Devices, which already has a device product called Shelly H&T associated with it. It has pre-configured datapoints for Temperature and Humidity. Now, suppose you wish to add another device product, the CONZER EM6400NG, an energy meter of the peripheral device type. This device includes datapoints such as Active Power, Line to Line Voltage, L3 to L1 Voltage, L2 to L1 Voltage, L1 to L2 Voltage, and Frequency.
Upon attempting to associate the CONZER EM6400NG with the Building Devices model, you'll encounter an issue because there are no common datapoints between Shelly H&T and CONZER EM6400NG. This discrepancy prevents their association under the same model. Consequently, you will be prompted to select a different model for the CONZER EM6400NG.
To resolve this, you must create a new device model specifically for energy meters. For instance, a model called "Building Energy Meters" could be created to group all energy meter products together, ensuring compatibility among associated device products based on their similar datapoint types.
Datapoint Group Consistency
Consider a device model named Building Devices, to which a device product named Shelly H&T is already associated. This device product features datapoints for Temperature and Humidity, from the datapoint group Environmental Monitoring. Now, you wish to associate another device product that you created called "My Smart Home Device." This device is configured with datapoints for Temperature and Current, which are imported from a custom datapoint group you've named My Datapoints.
Despite both device products having a Temperature datapoint, you'll encounter an issue when trying to associate My Smart Home Device with the Building Devices model. The problem arises because the Temperature datapoint in Shelly H&T and My Smart Home Device come from different groups—Environmental Monitoring and My Datapoints, respectively. Since datapoints from different groups cannot be mixed in the same model, this will prevent the association.
To resolve this issue, you have a couple of options:
- Import the Temperature datapoint for My Smart Home Device from the Environmental Monitoring group to ensure consistency across devices.
- Rename the Temperature datapoint in "My Smart Home Device" to something distinctive like "Temperature - C" to avoid conflicts during the association process.
Gateway Device Type Exception
Consider the scenario within a device model named Building Devices, where a device product named Shelly H&T is already associated. This product includes datapoints for Temperature and Humidity. If you wish to add a new device product of the Gateway device type to this model, you will receive a warning but will still be able to proceed with the association. This flexibility exists despite the datapoints since Gateway type devices are typically allowed to associate with any model.
However, it's important to note that while you can generally associate Gateway devices irrespective of their datapoints, there is a critical exception: if a datapoint in the Gateway device shares a name with a datapoint in other associated devices but originates from a different datapoint group, the association will be blocked. This prevents conflicting data management issues within the model.
For optimal organization and to avoid such conflicts, it is recommended to maintain separate device models specifically for Gateway type devices. This practice ensures clearer segmentation and management of device types within your systems.
Access your files securely from anywhere
Zoho CRM Training Programs
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
Zoho DataPrep Personalized Demo
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.
- Zoho Workerly Home
- Forums
- Connect With Us:
- Zoho Recruit Home
- Forums
- Connect With Us:
New to Zoho Writer?
Create. Review. Publish.
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
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.
New to Zoho Survey?
Zoho Sheet Resources
Zoho Forms Resources
New to Zoho Sign?
Zoho Sign Resources
Sign, Paperless!
New to Zoho TeamInbox?
Zoho TeamInbox Resources
New to Zoho ZeptoMail?
Design. Discuss. Deliver.
New to Zoho Workerly?
New to Zoho Recruit?
New to Zoho CRM?
New to Zoho Projects?
New to Zoho Sprints?
New to Zoho Assist?
New to Bigin?
Related Articles
Deleting a datapoint template
Datapoint templates can be deleted only from the developer application. All Datapoint operations require necessary permissions. Refer User Profiles document for more details. Datapoint Template Dependency: If a datapoint template is utilized in ...Understanding Datapoint Groups
In Zoho IoT applications, Datapoint Group is a collection of various datapoint templates tailored for specific use cases. These templates serve as a predefined set of metrics or measurements that are relevant to the particular application or ...Editing a datapoint template
A datapoint template can be edited only in the developer application and modifications are limited to the parsing key and datapoint status. All Datapoint operations require necessary permissions. Refer User Profiles document for more details. To edit ...Adding an instance specific datapoint
An instance specific datapoint is created and available exclusively to a particular device, asset or location. All Datapoint operations require necessary permissions. Refer User Profiles document for more details. Note: Model based widgets/reports ...Importing datapoint templates in a model
Datapoint templates for a Device model, Asset model, or Location model can be imported directly from predefined datapoint groups. Note: Only Realtime Datapoints without any computation are available in datapoint groups and can be imported. If you ...
New to Zoho LandingPage?
Zoho LandingPage Resources