Anedya Concepts

To take full advantage of the flexibility provided by the Anedya Platform, you need to understand the concepts on which the Anedya platform works. Like all other services, the Anedya platform has its strengths and limitations, knowledge of which enables you to optimize your application to get better performance, reduced cost, and seamless operation of all your IoT devices.

This section will explain the concept of this platform as well as some best practices.

Let's start with how resources are organized in Anedya. Resources are the entities that you create as a part of your application development using any platform. This includes Nodes, Variables, Certificates, API Keys, etc. Please note that creating resources will incur you charge as per resource pricing. You have a free quota for each resource after which you will be charged based on usage.

Projects

In simplest terms, a project is a collection of all resources related to a particular application. For example, you can have one project for one of your products and another project for a different product, if you provide IoT solutions, each project can contain the resources for your different clients.

note

Projects are completely isolated and it is not possible to move resources from one project to another.

Projects also allow you to restrict the access of the application to that specific project only.

Nodes

Nodes are the most important type of resource. It represents a physical device in your IoT application and allows you to perform actions on that device. You can create as many nodes as you require.

Nodes can be created either by web UI or by using APIs. Each node has a unique ID assigned by the Anedya platform. Apart from this unique ID, you can also provide a unique identifier for that node. identifier needs to be unique for all nodes within a project.

To be able to submit data from your physical device, you need to bind a physical device with the node in the platform. You can do this by several methods depending on the complexity of your application and the capabilities of a physical device. To be able to bind a physical device with the platform, The physical device must have a unique ID in the form of a 128-bit UUID which should not change for the entire lifespan of the device and should be discarded when the device is decommissioned.

⚠️Important!

Unique device IDs need to be in the form of 128-bit UUID only.

Variables

Variables as the name suggests are the variables that are submitted by the devices. For example, in a project, you need to submit room temperature and humidity from several devices. To achieve this, you need to create two variables in the Anedya dashboard. You can create multiple types of variables. Currently supported types are:

• Float
• Geo-coordinates

Essentially it is kind of defining a table schema where you can consider each variable to be a column. Please note that variables are global and you don't need to create separate variables for each device you onboard.