ABC 2026
<aside> 🚨 DISCLAIMER: This material has been produced using various openly available online resources to enhance its quality and comprehensiveness. In creating this document, we have attempted to acknowledge the original authors and primary contributors of the sourced materials. However, due to the extensive range of resources consulted, there may be instances where some contributors should be explicitly mentioned. Should there be any concerns or complaints regarding the attribution or content of this material, please do not hesitate to contact [email protected] for resolution and clarification.
</aside>
This document provides a demo of the Cloud IoT platform, Ubidots (https://ubidots.com/). An overview of the platform will be presented, followed by experiments demonstrating how MQTT can be utilized to send data to a cloud-based platform. This process enables data storage in a cloud repository and facilitates data analysis using the platform's software tools.
Ubidots provides 3 tiers to power your IoT Development cycle:
Every time an Ubidots Device receives a sensor value in a variable, a data-point or "dot" is created. Ubidots stores dots that come from your devices inside variables, and these stored dots have corresponding timestamps:
An Ubidots Device is a virtual entity. This means you could map multiple physical devices to a single Ubidots Device, or map many variables from a single physical device to several Ubidots Devices. It is your decision how you want to organize your data in your Ubidots account. The recommendation is of course to map 1 Physical Device to 1 Ubidots Device.
The Dot
Each dot contains these items:
Values
A numerical value. Ubidots accepts up to 16 floating-point length numbers.
{"value" : 34.87654974}
Timestamps