# Technical Training 1

## Technologies Referenced

This section outlines the major technologies reference in this training. Learning about this technologies is recommended.

### MQTT

MQTT (Message Queuing Telemetry Transport) is a lightweight and efficient publish-subscribe messaging protocol, commonly used in IoT (Internet of Things) applications.

<figure><img src="/files/PXWydpLzjgrJlBYPjpIG" alt=""><figcaption><p>MQTT Diagram</p></figcaption></figure>

MQTT is widely used for data transport throughout the MobiusFlow software.

### JSON

JSON (JavaScript Object Notation) is a lightweight data interchange format that is easy for humans to read and write, and easy for machines to parse and generate.

Learn how JSON works [here](https://jsonpath.com/).

A basic knowledge of JSON is required when using the Flows (logic engine) within MobiusFlow.

### EnOcean

EnOcean is a short distance wireless communication protocol used widely within the IoT space. Each EnOcean device has a unique identifier (UID) which is used to identify the sender of all EnOcean wireless telegrams.

<figure><img src="/files/8IWOLueaTWrGe7qgs7IE" alt="" width="563"><figcaption><p>Diagram of EnOcean devices and a MobiusFlow connector (EnOcean Transceiver / MQTT Converter)</p></figcaption></figure>

During this training, EnOcean will be used as an exemplar IoT technology to demonstrate MobiusFlow from the device level.

## MobiusFlow Overview

### Structure

A MobiusFlow instance runs a central MobiusFlow Hub. Services, each of which have a function within the overall solution, reside on the hub, and use it as a relay to communicate information.

<figure><img src="/files/NsdmzbUkHIsmwlIhjFwy" alt=""><figcaption><p>MobiusFlow Hub / Service / Object hierarchy</p></figcaption></figure>

A MobiusFlow object often represents a virtual equivalent of a real-world device, however can represent non-physical entities such as calculated data.

Some services can have MobiusFlow objects reside on them, often when the service needs to directly interact with those objects in some way. For example, objects representing EnOcean devices will always reside on an EnOcean devices service.

### Points / Resources

A MobiusFlow object contains many resources, each being its own individual data stream representing something about that object.

<figure><img src="/files/oZCb5RI3iIFDFYFJQ7YP" alt=""><figcaption><p>MobiusFlow Object / Resource hierarchy</p></figcaption></figure>

Below shows a screenshot from the MobiusFlow software of the list of resources associated to an EnOcean Temperature / Humidity / C02 sensor.

<figure><img src="/files/vMx1FVK3VR5V8BafHGMV" alt=""><figcaption></figcaption></figure>

**A point is a chargeable resource**. Notice in the above screenshot, the points column is only populated for Temperature, Humidity and CO2.

Also notice how the MobiusFlow software calculates your total point usage and displays this at the bottom right hand corner.

### URIs

All parts of the MobiusFlow hierarchy are assigned a unique URI with the following structure:

<mark style="color:blue;">**HID**</mark>/<mark style="color:green;">**SID**</mark>/<mark style="color:purple;">**PID**</mark>/<mark style="color:yellow;">**INS**</mark>/<mark style="color:red;">**RID**</mark>

<table><thead><tr><th width="82"></th><th width="437">Explanation</th><th>Format</th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>HID</strong></mark></td><td><strong>Hub ID</strong></td><td>6-Digit Hex</td></tr><tr><td><mark style="color:green;"><strong>SID</strong></mark></td><td><strong>Service ID</strong></td><td>3-Digit Hex</td></tr><tr><td><mark style="color:purple;"><strong>PID</strong></mark></td><td><strong>Profile ID</strong> (A MobiusFlow profile can be thought of as an object type)</td><td>4-Digit Hex</td></tr><tr><td><mark style="color:yellow;"><strong>INS</strong></mark></td><td><strong>Instance ID</strong> (The ID of that object instance)</td><td>4-Digit Hex</td></tr><tr><td><mark style="color:green;"><strong>RID</strong></mark></td><td><strong>Resource ID</strong></td><td>2-Digit Hex</td></tr></tbody></table>

#### Example URIs

**Service**

Full example URI of a service:

<mark style="color:blue;">**000001**</mark>/<mark style="color:green;">**020**</mark>

Representing <mark style="color:green;">service</mark> <mark style="color:green;"></mark><mark style="color:green;">**020**</mark> on <mark style="color:blue;">hub</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**000001**</mark>.

**Object**

Full example URI of an object:

<mark style="color:blue;">**000001**</mark>/<mark style="color:green;">**020**</mark>/<mark style="color:purple;">**0028**</mark>/<mark style="color:yellow;">**0001**</mark>

Representing <mark style="color:yellow;">instance</mark> <mark style="color:yellow;">**0001**</mark> of object type (<mark style="color:purple;">profile</mark>) <mark style="color:purple;">**0028**</mark> on <mark style="color:green;">service</mark> <mark style="color:green;"></mark><mark style="color:green;">**020**</mark> on <mark style="color:blue;">hub</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**000001**</mark>.

**Resource**

Full example URI of a resource:

<mark style="color:blue;">**000001**</mark>/<mark style="color:green;">**020**</mark>/<mark style="color:purple;">**0028**</mark>/<mark style="color:yellow;">**0001**</mark>/<mark style="color:red;">**40**</mark>

Representing <mark style="color:red;">resource</mark> <mark style="color:red;"></mark><mark style="color:red;">**40**</mark> on <mark style="color:yellow;">instance</mark> <mark style="color:yellow;">**0001**</mark> of object type (<mark style="color:purple;">profile</mark>) <mark style="color:purple;">**0028**</mark> on <mark style="color:green;">service</mark> <mark style="color:green;"></mark><mark style="color:green;">**020**</mark> on <mark style="color:blue;">hub</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**000001**</mark>.

**Conclusion**

Using the URI system, it is therefore possible to reference any component of a given MobiusFlow configuration.

## Configuration Example

### Example Overview

This aims to show how data taken from EnOcean sensors at a hardware level, is brought into and through the MobiusFlow system, and then presented in the form of a dashboard.

#### Project Schematic

<figure><img src="/files/G6JSn7bgMig96rJnP025" alt=""><figcaption></figcaption></figure>

The following shows a colorless project schematic representing lack of implementation. As the project is implemented, this diagram will be colored in so progress can easily shown.

<figure><img src="/files/xsGPNNwDOXtV1KImzIru" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note that the EnOcean devices have been dropped from the diagram for simplicity
{% endhint %}

#### Explanation of Services

<table><thead><tr><th width="197">Service</th><th>Explanation of requirement</th></tr></thead><tbody><tr><td>MQTT Broker</td><td>To allow MobiusFlow connectors to connect to and send data to</td></tr><tr><td>Connector Service</td><td>To collect incoming messages from MobiusFlow connectors and bring the data into the MobiusFlow Hub</td></tr><tr><td>EnOcean Devices Service</td><td>To decode raw EnOcean messages from the MobiusFlow hub and populate this service's child MobiusFlow objects with human-readable data.</td></tr></tbody></table>

### MobiusFlow Configuration

#### MQTT Broker

Add and start MQTT Broker service:

{% @supademo/embed demoId="xStHe6UWWvbTYrBqlcUdU" url="<https://app.supademo.com/demo/xStHe6UWWvbTYrBqlcUdU>" %}

<figure><img src="/files/U2BbXw3f0OR472puWmG4" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
The MQTT Broker service has been added, configured and started.
{% endhint %}

#### Connector Service

Add connectors service, add a connector to the service, and finally start the service.

Add and start service:

{% @supademo/embed demoId="nP9jONKIhXeY6UU3vpfy-" url="<https://app.supademo.com/demo/nP9jONKIhXeY6UU3vpfy->" %}

Add a MobiusFlow connector object to the connectors service and configure:

{% @supademo/embed demoId="gOuyB74D391kXXWWTMcxc" url="<https://app.supademo.com/demo/gOuyB74D391kXXWWTMcxc>" %}

<figure><img src="/files/vw8OhaAfqT4kB9RQrDiJ" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
The Connector service has been added, configured and started.
{% endhint %}

#### EnOcean Devices Service

Add EnOcean Devices service, add EnOcean device objects to the service, and finally start the service.

{% @supademo/embed demoId="WYcHRyM3hcqiaTqaWdM8b" url="<https://app.supademo.com/demo/WYcHRyM3hcqiaTqaWdM8b>" %}

<figure><img src="/files/efjopph8aGTLlCST0LVk" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
The EnOcean devices service has been added, configured and started.
{% endhint %}

### Connecting Hardware

For full information on how to configure a MobiusFlow connector see [here](/help/user-guides/mobiusflow-connectors/mobiusflow-official-connector/configuring-a-connector.md).

{% @supademo/embed demoId="uE5baHAyFlNXcYRKvq0\_y" url="<https://app.supademo.com/demo/uE5baHAyFlNXcYRKvq0_y>" %}

<figure><img src="/files/NBwPP0GuH1R3UOMYMFE1" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
MobiusFlow connector is connected.
{% endhint %}

### Service Status and Data

The status of all service can viewed. This is a helpful insight into the current state of the solution as well as aiding with diagnostics.

{% @supademo/embed demoId="clrp2xqqx1s3fpef51h0xi1g0" url="<https://app.supademo.com/demo/clrp2xqqx1s3fpef51h0xi1g0>" %}

The data of any live object can viewed by navigating to that object and then clicking on resources.

{% @supademo/embed demoId="-CVQ2GYE8NdFMXO5t9iKl" url="<https://app.supademo.com/demo/-CVQ2GYE8NdFMXO5t9iKl>" %}

### Flows

Connecting the flows to the MobiusFlow engine, as well as the baseline principles of pulling into the flows is covered [here](/help/technical-docs/flows.md).

<figure><img src="/files/QD78T6zrbuJhnn11zAwU" alt=""><figcaption></figcaption></figure>

### Dashboard

In this example, the live state of the buttons on a 4-Rocker EnOcean switch is shown on a basic dashboard.

{% @supademo/embed demoId="CpNsJwVOsJ9VTjfZMQ9hu" url="<https://app.supademo.com/demo/CpNsJwVOsJ9VTjfZMQ9hu>" %}

<figure><img src="/files/ebf0KMGwpqADPidPnRvw" alt=""><figcaption><p>Completed project schematic</p></figcaption></figure>

Using dashboard in the way illustrated can be as simple or as complex as required. Display widgets include graphs, charts and tables, as well input widgets such as switches, buttons, drop-downs and text inputs. Full documentation of the Flows dashboard can be found [here](https://dashboard.flowfuse.com/getting-started.html).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mobiusflow.com/help/user-guides/technical-training-guides/technical-training-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.