Changes

115 bytes added ,  15:15, 2 August 2023
no edit summary
Line 1: Line 1:  +
[[File:Networking_rutos_configuration_examples_openremote_logo.png|right]]
 
=Introduction=
 
=Introduction=
OpenRemote an intuitive user-friendly 100% open source IoT platform. You can build a complete IoT device management solution including: device management and auto provisioning, customisation of asset types, automation via when-then, flow, javascript and groovy rules, data analytics, connectivity via several protocol agents and manager APIs (e.g. MQTT broker, HTTP/REST, WS), Multi-tenancy (realms), Users and roles management, Edge gateway, Front-end UI web components and consoles, and an Insights dashboard builder.
+
 
 +
OpenRemote an intuitive user-friendly 100% open source IoT platform. You can build a complete IoT device management solution including: device management and auto provisioning, customisation of asset types, automation via when-then, flow, javascript and groovy rules, data analytics, connectivity via several protocol agents and manager APIs (e.g. MQTT broker, HTTP/REST, WS), Multi-tenancy (realms), Users and roles management, Edge gateway, Front-end UI web components and consoles, and an Insights dashboard builder.
    
In this article you will find instructions on how to setup OpenRemote Manager as a MQTT Broker and how to send telemetry data using Teltonika device to the OpenRemote platform.
 
In this article you will find instructions on how to setup OpenRemote Manager as a MQTT Broker and how to send telemetry data using Teltonika device to the OpenRemote platform.
Line 74: Line 76:     
===First example: Publishing RUT MODBUS to OpenRemote manager using MQTT===
 
===First example: Publishing RUT MODBUS to OpenRemote manager using MQTT===
[[File:Networking_rutos_configuration_examples_openremote_020.png|border|center|class=tlt-border]]
+
[[File:Networking_rutos_configuration_examples_openremote_020_v2.png|border|center|class=tlt-border]]
    
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.  You can also send data from another MODBUS Slave devices connected to the router.
 
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.  You can also send data from another MODBUS Slave devices connected to the router.
Line 149: Line 151:     
===Second example: Publishing Bluetooth data (from Eye Sensor) to OpenRemote manager using MQTT===
 
===Second example: Publishing Bluetooth data (from Eye Sensor) to OpenRemote manager using MQTT===
[[File:Networking_rutos_configuration_examples_openremote_019.png|border|center|class=tlt-border]]
+
[[File:Networking_rutos_configuration_examples_openremote_019_v1.png|border|center|class=tlt-border]]
    
In this example the RUT device will collect [[RUTX11 Bluetooth|Bluetooth]] data from [https://teltonika-gps.com/products/accessories/sensors-beacons/eye EYE Sensor]. The received data will be sent over MQTT to OpenRemote manager.
 
In this example the RUT device will collect [[RUTX11 Bluetooth|Bluetooth]] data from [https://teltonika-gps.com/products/accessories/sensors-beacons/eye EYE Sensor]. The received data will be sent over MQTT to OpenRemote manager.
Line 203: Line 205:  
# https://github.com/openremote/openremote/wiki
 
# https://github.com/openremote/openremote/wiki
 
# Forum https://forum.openremote.io/
 
# Forum https://forum.openremote.io/
 +
[[Category:Third party services]]