Connecting a Teltonika Networks device
Last edited: July 18th 2026
Prerequisites
The device model used in this guide is the RUT241. There may be variations using other models or firmware version.
- An RUT241 Teltonika device running RUT2M_R_00.07.17.1.
- Access to the RUT241 Teltonika device through the Web UI.
- Successfully downloaded the OPC-UA package on the RUT241 device.
- Successfully downloaded the MQTT package on the RUT241 device.
- You have an account on the Inuatek Data Collection Cloud (DCC).
- Successfully added a Generic MQTT device in the IoT Tree. See Adding an MQTT device in IoT Administration.
Preparing the RUT241
This guide focuses on sending data from an OPC-UA server to the DCC via MQTT.
It begins by describing how data is collected from an OPC-UA server and then outlines the process of transmitting the collected data to the DCC via MQTT.
If you have a RUT241 with an OPC UA Server and configured nodes, please proceed to the Setting up OPC UA Value Groups.
Setting up OPC-UA
In this guide, we will gather data from an OPC UA server hosted on a PLC that is accessible by the RUT241. The collected data is from a temperature sensor and a photoelectric distance sensor.
Start off by open the OPC UA service:
Unfold the Add new Instance below the OPC UA server and give the server a proper name, then click the ADD button in order to add a new OPC UA server!
Once added a new modal opens:
Fill out required infomation in order to connect to the OPC UA server and enable the server by switching the radio button to on.
Once filled, we can start to add the actual data points by adding a new instance, which opens another modal for creating a server node and fill out the required addressing for the data point:
Add required number of datapoints:
NOTE Click Test in order to test if the addressing to the specific datapoint is correct. The test DO NOT fetch the data point.
Now that the required datapoints have been added, the RUT241 OPC UA Groups can be setup.
Setting up OPC UA Value Groups
Value Groups are used to define the data that will be included in the MQTT Data Format and transmitted to the DCC via MQTT.
Start by expanding OPC UA Value Groups and create a new instance by assigning it a unique ID. This ID will later be used as the data point name when the data is transmitted to the DCC over MQTT. In this example, the name of the server nodes is used. Once the Add button is clicked a new modal will open:
Once the has opened, enable the created group, and fill out the fields:
- Name: Name of the datapoint
- Period: custom (time between data retrieval in seconds)
- Failure mode: none
In this example we are collecting data from the OPC UA Server every 60s. The remaining fields shall remain empty.
Add a datapoint to the group by adding a new Instance. Enter a Value name and click ADD, this will open a new modal:
Fill out the fields and Enable the Value:
- Name: The name of the Value have no functional purpose. For simplicity you may use the node name as the Value name.
- Server: Select the server that has access to the OPC UA Server.
- Server Node: Select the correct Server Node.
NOTE: Only one datapoint can be associated with a group in order to function with the DCC. This is to insure each datapoint has a unique ID. Hence, it is necessary to create an equivalent number of groups as there are datapoints. In this guide, we have two data points, and thus two groups are configured as "Temperature" and "Distance sensor" respectively:
To test whether the group can collect data from the OPC UA Server click the Test button of the Group, this will fetch the data from the UPC UA server and you can verify that the collected data is correct.
Add the reminder of the Groups:
We are now finished setting up the OPC UA data points and are now ready for setting up the MQTT conenction towards the DCC.
Setting up MQTT
This section will cover setting up MQTT using TLS certificates on the RUT241.
Navigate to the "Data to Server" tab. Then, click ADD to create a new data sender:
This will open a new modal:
In the setup the following fields must be provided:
- Name: name of the Data. Shall later be user when creating the Collection in next step.
- Type: OPC UA
- Data filtering: All
- Segment count: 1
- Format type: Custom
- Format format:
{"id":"%name%", "v":"%data%", "t":%timestamp%000} - Empty value: N/A
- Delimiter: , (comma)
Click Next: Collection edit
In the setup the following fields must be provided:
- Enable: on
- Timer: In this example Period is chosen
- Period (in seconds): In this example 60 is chosen
- Retry: on
- Retry count: Retry to send the same data N times
- Timeout: Timeout in seconds between retry attempts.
- Format type: Custom
- Format format:
{ "data": [<Data>] }Defined in earlier step, you can see the available variables by clicking Show string list - Empty value: N/A
- Delimiter: , (comma)
Click Next: Server edit
In the setup the following fields must be provided:
- Type: MQTT
- Server address: Broker address (mqttbroker.inuatek.com)
- Port: 8883
- Keepalive: 60 (default)
- Topic: Topic defined when created the device on the DCC
- QoS: 0 (default)
- Enable secure connection: on
- TLS type: Certificate based (default)
- Allow insecure connection: off (default)
- Certificate files from device: off (default)
- Certificate authority file: Upload CA which were provided by the DCC upon device creation:
ca.crt - Client certificate: Upload client cert which were provided by the DCC upon device creation:
client.crt - Private key: Upload key which were provided by the DCC upon device creation:
client.key - Use credentials: off (default)
Note: The specific Server address for your device can be found in the README.md file included with your downloaded certificate package.
Click Save & Apply
Creating an IoT Configuration for a RUT241 device
If you have successfully configured the Data Sender and uploaded your certificates, the device should be able to connect to the MQTT Broker. New Sample Points should automatically be present on the DCC, when new data is received. For more information see Working with the IoT Configuration.