Tutorial

End-to-End demo with mioty

How to configure a mioty Base Station with a commercial
Backend serviceand visualize data with Thingsboard

Introduction

Last updated: 03.11.2025

In this tutorial, we will walk through setting up a complete end-to-end mioty® IoT system — from the sensor node to data visualization in the cloud.

The goal is to get a working demo running quickly, using off-the-shelf tools and minimal configuration, so you can focus on understanding how the pieces fit together.

We will start with a mioty® endpoint device and its payload decoder (using the maker example from mioty-pico-endpoint), connect it to a mioty® base station (either purchased or built with the mioty®GO project), and send the data through a LORIOT network server to ThingsBoard Cloud for visualization and management.

By the end of this guide, you will have:

  • mioty® endpoint transmitting data wirelessly to your base station

  • functioning network server forwarding decoded data to the cloud

  • dashboard on ThingsBoard showing your live sensor readings

 

This setup is ideal for prototyping, demos, or learning the mioty® ecosystem before deploying a larger-scale solution. The screenshots are meant to give you an overview to understand how a mioty® solution is set up, even if you don’t have all the necessary hardware available yet.

1. Setting up the Network

The screenshots and instructions show an example with the AVA Evaluation Kit, but the instructions will work in a very similar way with any other commercial base station.

Make sure you are running the Base Station mode, which means that the mioty® Service Center and Application Center are externally hosted on the cloud and not on the base station hardware itself. We will make use of the standardized Base Station to Service Center Interface (BSSCI) specified by the mioty® Alliance.


Next, sign in to the Loriot backend. You can create a free community account if you don’t have one already. These two backend locations are mioty®-ready:

EU3 – Madrid, Spain
US2 – New York, USA

In these Loriot instances, you will be able to switch to mioty®.

Now, create a new network with the Create New Network button or in the Networks menu:

 

You will be adding a new base station to your network. Now it’s time to look up the EUI of your base station. In case of the AVA Evaluation Kit, it can be found in the base station dashboard. Copy it from there to create your Base Station in the network. Also add the address, where it will be placed.

Now, we will need to set up the BSSCI interface between the base station and the service center. On your Loriot Base Station page, go to Certificate and generate a TLS Certificate.

Copy that information over to your Base Station:

And your Service Center Connection should switch to green, you have successfully connected your base station to the Loriot Service Center Backend!

2. Provisioning your End-Point

For this step, you will need a mioty® End-Point including its keys (EpEUI, ShAddr, NwkSnKey).

Create a new application within Loriot to serve as a bucket for this project:

You are now able to enroll End-Points in your application.

Important step: After registering your End-Point on the Service Center, you have to propagate the attachment to the base stations! This seems a bit unlogic at first, but it is the way to register your device on each base station through the BSSCI interface. You may also use the Smart Attachment feature to link your application to a specific network, to have the attachment done automatically after adding a device.

Now you should see that your End-Point sending data, after you have switched it on.

And on the Spectrogram view on the Base Station site, you might see the bursts of the mioty® telegrams, at least if you are using the AVA Evaluation kit software:

3. Routing data to an IoT Platform

Now that you have your network and end-point up and running, you might want to choose an IoT Platform to eventually do something with your data. There are many options available, please check the mioty® Alliance website for available platforms and the developer page.

For this demo, we use ThingsBoard which is an Open Source platform for data collection, processing, and visualization. It supports multiple connectivity options, integrates with a variety of protocols, and provides powerful dashboard tools for real-time monitoring. One of its key advantages for our setup is the ability to add a payload parser, which allows us to decode raw mioty® messages directly in the platform. This is a feature not available in the LORIOT Service Center. While some mioty® Application Centers may offer a blueprint parser for decoding data, this is not a mandatory feature, making ThingsBoard particularly useful for demonstrations and prototyping.

In this guide, we use ThingsBoard Cloud as our demonstrator, as it allows for a quick setup without the need to run your own infrastructure. A free demo of the cloud version is available for 30 days, which is ideal for following along with this tutorial. Since ThingsBoard is open source, you also have the option to host it on your own servers, which removes the ongoing cloud subscription costs.

Let’s get started by creating an account on the Thingsboard Cloud platform.

We will be adding an Integration for Loriot, which allows us to parse the payload directly on the ThingsBoard platform. Click + to add a new integration and select the HTTP Integration Type.

Insert an Uplink data converter (usually provided by the device manufacturer as a .js file)

In the case of the RPi Pico example, we can insert the decoder example from the GitHub page.

There is no downlink capability in this example. Go to connection and copy the HTTP endpoint URL. You may want to add headers for additional security.

Now, go back to your Application in Loriot and check the Output page.

Add a new output and select HTTP Push. Insert the URL that you have copied in your ThingsBoard integration.

Wait for the next uplink transmitted by your end-point. The HTTP integration in thingsboard will automatically create your device, and you should be able to see it in Devices.

4. Building a dashboard

Now that your data gets routed into a Device on ThingsBoard, it should be quite straightforward to create a dashboard and adapt it to your needs.

You can create dashboards for your single test device, or also for a group of devices. Just follow the guides available on the ThingsBoard platform.

On this example, we are looking at the temperature value transmitted by our demo node, as well as the Frame Counter to make sure that all frames have been transmitted, and the RSSI and SNR values to monitor signal quality indication.

5. Conclusion

This guide has shown how to set up a complete end-to-end mioty® system, starting from a sensor endpoint, connecting through a base station, forwarding data via the LORIOT Service Center, and finally visualizing it on a ThingsBoard dashboard. With only a few configuration steps, you can establish a working prototype that demonstrates the reliability and scalability of mioty® as an LPWAN solution. The standardized interfaces, such as the BSSCI, ensure interoperability across hardware and software components, while the integration with an open-source platform like ThingsBoard highlights the flexibility of the ecosystem.

The setup described here is particularly well suited for proofs of concept, demos, and small pilot deployments. It helps developers and companies understand the data flow from the edge to the cloud, experiment with payload parsers, and evaluate how mioty® can be integrated into their own IoT solutions. Since the system is modular, individual components—such as the network server, IoT platform, or visualization tools—can be exchanged or scaled independently, which reduces vendor lock-in and future-proofs the solution.

Looking ahead, this foundation can be extended into production-grade deployments by adding redundancy in the network, enhancing device security, or connecting to enterprise backends through APIs. As the mioty® Alliance continues to expand its ecosystem, more commercial devices, software integrations, and cloud services will become available, making it even easier to bring robust LPWAN applications to market.

Share these news