Changes

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, you have to pair the device you want to get data from, first

* 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

After setting up all, you should have something similar to the screen below. Click on save and apply.

After setting up all, you should have something similar to the screen below. Click on save and apply.

[[File:Config421.png|none|thumb|749x749px]]

[[File:Config421.png|none|thumb|749x749px]]

If you've done

To check if your setup is working, you can use any MQTT client, and subscribe to the topic you've created, you should be able to see the data of the source you've selected. In the image below, i've used the AWS IoT mqtt test client to subscribe to the topic that the router was publishing.

= 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.

Depending on your RUT model, you can have the following options of data sources to send over MQTT:

* Bluetooth

* Bluetooth