0
edits
Changes
no edit summary
Router monitoring via MQTT Linux guide applies to TRB145 gateway and RUT9xx, RUTx routers.
Router monitoring via MQTT Linux guide applies to TRB145 gateway and to RUT9xx, RUTx routers.
==Introduction==
==Introduction==
'''MQTT (MQ Telemetry Transport or Message Queue Telemetry Transport)''' is an ISO standard (ISO/IEC PRF 20922) publish-subscribe-based messaging protocol. It works on top of the TCP/IP protocol. It is designed for connections with remote locations where a "small code footprint" is required or the network bandwidth is limited. The publish-subscribe messaging pattern requires a message broker.
'''MQTT (MQ Telemetry Transport or Message Queue Telemetry Transport)''' is an ISO standard (ISO/IEC PRF 20922) publish-subscribe-based messaging protocol. It works on top of the TCP/IP protocol. It is designed for connections with remote locations where a "small code footprint" is required or the network bandwidth is limited. The publish-subscribe messaging pattern requires a message broker.
This article provides a guide on how to configure and use a basic MQTT setup on TRB145 gateway and RUT9xx, RUTx routers.
This article provides a guide on how to configure and use a basic MQTT setup on TRB145 gateway and on RUT9xx, RUTx routers.
==How MQTT works==
==How MQTT works==
In general an MQTT connection takes place between two Clients and a Broker. A RUT router and TRB14x gateways can be Broker, Client or both. The MQTT Publisher(Client) present in TRB14x and RUT routers subscribes to two topics by default: '''<TYPE>/get''' and '''get/<SERIAL>/command'''. Where '''<TYPE>''' is device type, for RUT routers type is '''router''' and for TRB14x type is '''device''' and '''<SERIAL>''' is the router's serial number.
First lets look over how MQTT works on TRB145 gateway and on RUT9xx, RUTx routers. An MQTT connection takes place between two Clients and a Broker. A RUT router and TRB145 gateway can be Broker, a Client or both. The MQTT Publisher (Client) present in RUT routers subscribes to two topics by default: '''router/get''' and '''get/<SERIAL>/command''', where '''<SERIAL>''' is the router's serial number. When a third party client connects to the Broker, it sends the message '''id''' to the the topic '''router/get'''. The publisher then sends a response containing its serial number to the topic '''router/id'''. Now that the Client knows the router's serial number it can ask for values of various parameters by sending requests to the topic '''router/<SERIAL>/parameter_name'''. The MQTT Publisher can send responses containing values of these system parameters:
First lets look over how MQTT works on TRB145 gateway and on RUT9xx, RUTx routers. An MQTT connection takes place between two Clients and a Broker. A RUT router and TRB145 gateway can be Broker, a Client or both. The MQTT Publisher (Client) present in RUT routers subscribes to two topics by default: '''router/get''' and '''get/<SERIAL>/command''', where '''<SERIAL>''' is the router's serial number. When a third party client connects to the Broker, it sends the message '''id''' to the the topic '''router/get'''. The publisher then sends a response containing its serial number to the topic '''router/id'''. Now that the Client knows the router's serial number it can ask for values of various parameters by sending requests to the topic '''router/<SERIAL>/parameter_name'''. The MQTT Publisher can send responses containing values of these system parameters:
