104
edits
Changes
no edit summary
=== '''Creating a thing''' ===
=== '''Creating a thing''' ===
First off, open the [https://aws.amazon.com/pt/console/ AWS Management Console] and login with your credentials. After that, you will see a screen similar to this:
First off, open the [https://aws.amazon.com/pt/console/ AWS Management Console] and login with your credentials. After that, you will see a screen similar to this:
[[File:Image987.png|none|thumb|862x862px]]
[[File:Image987.png|border|class=tlt-borde|none|thumb|862x862px]]
On the search bar on the top, search for "IoT Core", and click on the first search result. You will see a screen like the one below, open the "Manage" section and click on "Things".
On the search bar on the top, search for "IoT Core", and click on the first search result. You will see a screen like the one below, open the "Manage" section and click on "Things".
[[File:Image986.png|thumb|865x865px|alt=|none]]
[[File:Image986.png|thumb|865x865px|alt=|none]]
Then, do the following procedure to create a Thing: click on the "Create Things" button -> "Create single thing" -> Give it any name -> "No shadow" -> "Auto-generate a new certificate (recommended)" -> "Create thing".
Then, do the following procedure to create a Thing: click on the "Create Things" button -> "Create single thing" -> Give it any name -> "No shadow" -> "Auto-generate a new certificate (recommended)" -> "Create thing".
=== Certificate Handling ===
===Certificate Handling===
Certificates are used by Publishers and Subscribers to connect to your AWS MQTT Broker.
Certificates are used by Publishers and Subscribers to connect to your AWS MQTT Broker.
[[File:Image874.png|none|thumb|406x406px]]
[[File:Image874.png|none|thumb|406x406px]]
=== Setting up policies ===
===Setting up policies===
The policies are needed for allowing incoming data into AWS.
The policies are needed for allowing incoming data into AWS.
[[File:Image471.png|none|thumb|479x479px]]
[[File:Image471.png|none|thumb|479x479px]]
=== Getting your endpoint ===
===Getting your endpoint===
The endpoint is the host address of your MQTT Broker, where Publishers and Subscribers will connect to.
The endpoint is the host address of your MQTT Broker, where Publishers and Subscribers will connect to.
=RUT as MQTT Publisher=
=RUT as MQTT Publisher=
=== What data do you want to publish? ===
===What data do you want to publish?===
Depending on your RUT model, you can have the following options of data sources to send over MQTT:
Depending on your RUT model, you can have the following options of data sources to send over MQTT:
* Bluetooth
*Bluetooth
* Wifi scanner
* Wifi scanner
* MODBUS
*MODBUS
* Router monitoring
* Router monitoring
=== Publishing Bluetooth/Wifi scanner/Modbus data ===
===Publishing Bluetooth/Wifi scanner/Modbus data===
Before sending data from those sources to the MQTT Broker, the router needs to know what data from each source to send:
Before sending data from those sources to the MQTT Broker, the router needs to know what data from each source to send:
* For Bluetooth, first you have to pair the device you want to get data from
*For Bluetooth, first you have to pair the device you want to get data from
* For Wifi scanner data, you have to enable the wifi scanner functionality first
* For Wifi scanner data, you have to enable the wifi scanner functionality first
* For MODBUS data, you need to set what data from what MODBUS slave the router has to get
*For MODBUS data, you need to set what data from what MODBUS slave the router has to get
If you need any help on setting up each functionality, the Teltonika Wiki has topics for each one of them
If you need any help on setting up each functionality, the Teltonika Wiki has topics for each one of them
[[File:Image4752.png|none|thumb|961x961px]]
[[File:Image4752.png|none|thumb|961x961px]]
= Example: Publishing RUT MODBUS data over MQTT =
=Example: Publishing RUT MODBUS data over MQTT=
In this example the RUT device will act as MODBUS TCP Master and MODBUS TCP Slave, so the device will make requests (Master) and answer to himself (Slave). The received reply, will be sent over MQTT.
In this example the RUT device will act as MODBUS TCP Master and MODBUS TCP Slave, so the device will make requests (Master) and answer to himself (Slave). The received reply, will be sent over MQTT.
* Bluetooth
*Bluetooth
