Lesson 1 Standard Workflow
This is a step-by-step guide covering the most common activities when setting up your IoT solution on the platform. It is intended for users with full access rights to all features in the platform. The steps are presented in a natural, logical order-each with a short introduction, followed by more detailed information in the training material, user guide, and developer documentation.
Lesson 1.1 Adding LoRaWAN devices
Adding IoT nodes to Yggio is the foundation.
Lesson 1.2 Device Views
Views are found in the Device menu and are used to visualize sensor data using customizable columns and settings. They are highly flexible and can include graphical elements, color coding, and filters - for example, to help identify anomalies. Once created views can be shared within an organisation or exported as a text string.
Lesson 1.3 Alarm translators
Alarm Translators are primarily used for threshold-based supervision but can also use algorithms and mathematical logic for more advanced monitoring.
Lesson 1.4 Exporting and Importing Data with CSV
One of the easiest way to export data out of Yggio is to export it as CSV. This can be done both for view and time series. This can be also be used for editing names quickly of several devices and even changing data (not recomended). You can use this for batch managment.
Lesson 1.5 Map and Map Views
On the Map page you can view the location of your devices on a map.
Lesson 1.6 Dashboards
Dashboards are the first thing you see when you log in to the platform under the navigation bar menu "Dashboards". They are highly customizable, easy to edit, and update in real time. Dashboards help you quickly summarize the information you’re interested in-presented clearly and visually engaging.
Lesson 1.7 Access Rights and Data Sharing
The system separates between resources sharing and functionality access. Resources being access to different type of the resources in the platform meanwhile funationality access is determined by the role of a user
Lesson 2 The Extended Work Flow
If you've completed all the steps in Lesson 1, you're ready to move on to the next stage. Lesson 2 takes you beyond the basics and into the core of the platform’s advanced functionality.
Lesson 2.1 Rule Engine
The rule engine triggers actions, which can be sending an email or SMS, making an HTTP request, or publishing a message to an MQTT topic. Triggers, conditions and actions are nodes that you drag onto a canvas and connect, which makes it useful for building and visualizing threshold and alarm rules.
Lesson 2.1 The Rule Engine (Legacy)
Rules trigger actions-such as sending an email-when specified conditions are met. Because both conditions and actions can be customized, the Rule Engine is ideal for monitoring thresholds and alarms.
Lesson 2.2 Calculations
Calculations refer to different calculations to apply between devices. A calculation creates a virtual node that holds the result of the calculation. The data used by the device does not go back in time; instead, it uses data from after the calculation was created. In the device details of the calculated device, you can see which devices are included, what value was used, and the type of calculation. It is one of the most powerful features of the platform and can be used to realize a wide variety of use cases.
Lesson 2.3 IoT Nodes and Network Protocols - From NB-IoT to BLE
LoRaWAN is the most common device type used in modern long-range IoT networks. We covered how to add and manage them in Lesson 1.1: Adding LoRaWAN Devices.
Lesson 2.4 CSV reports
These reports are easily created in the rule engine as an action and linked to a condition so they are created with the current data of the device. When a report is created it can be sent directly to your mail. They can't be edited after they are created but that is where excel reports come in. Rule engines report are easy to set up.
Lesson 2.5 Excel Reports
Excel Reports are generated using the platform’s built-in report engine and exported as .xlsx files. These reports can visualize a wide range of data-such as metering, office utilization, alarms, and more.
Lesson 2.6 Organizations
The platform's organization Manager allows you to create and manage an organizational structure, facilitating the management of different user accounts assigned to handle various types or parts of resources.
Lesson 2.7 Roles
This lesson will teach users how to navigate and manage Roles. Roles directly give or remove access to specific API endpoints and also hide UI elements the user has no access to. Users will learn to assign roles to different users and see the effect on those users' accounts. To complete this lesson, you will need the Organization Admin role and a few colleagues who can check how different roles affect their accounts.
Lesson 2.8 Exploring Connectors
Overview
Lesson 2.9 External Data Sharing
In this lesson, we will explore how to share data outside the platform. There are three main methods:
Lesson 2.10 - Standard Flows: Timers and Geofences
General timers are used to delay alarms. Like, if a door or window opens and isn’t closed again within a certain time, the alarm goes off. Same thing if the temperature passes a limit and doesn’t drop back down soon enough.
Lesson 3.0 Advanced usage
This module goes beyond the day-to-day platform features covered in Lessons 1
Lesson 3.1 Grafana
Grafana is a popular open-source tool for dashboards,
Lesson 3.2 Power BI
The IoT platform's Power BI Custom Connector brings your device data straight into
Lesson 3.3 Node-RED
Node-RED is a low-code, flow-based tool for wiring
Lesson 3.4 MQTT Explorer
MQTT Explorer is a free desktop tool for
Lesson 3.5 Postman
Postman is a graphical HTTP client for
Lesson 3.6 Curl
curl makes the same IoT platform REST API calls as Postman,
Lesson 3.7 Translator development
A translator decodes a device's raw payload into the IoT platform's flat, canonical