Monitoring via MQTT: Difference between revisions
Appearance
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
==How MQTT works== | ==How MQTT works== | ||
First lets look over how MQTT works on RUT9xx | 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: | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 18: | Line 18: | ||
! style="text-align: left; vertical-align: top;" | temperature | ! style="text-align: left; vertical-align: top;" | temperature | ||
| style="text-align: left; vertical-align: top;" | Temperature of the module in 0.1 degrees Celsius | | style="text-align: left; vertical-align: top;" | Temperature of the module in 0.1 degrees Celsius | ||
| style="text-align: left; vertical-align: top;" | RUT9xx and | | style="text-align: left; vertical-align: top;" | RUT9xx and RUTx11 | ||
|- | |- | ||
! style="text-align: left; vertical-align: top;" | operator | ! style="text-align: left; vertical-align: top;" | operator | ||
| style="text-align: left; vertical-align: top;" | Current operator’s name | | style="text-align: left; vertical-align: top;" | Current operator’s name | ||
| style="text-align: left; vertical-align: top;" | RUT9xx, | | style="text-align: left; vertical-align: top;" | RUT9xx, RUTx11 and TRB145 | ||
|- | |- | ||
! style="text-align: left; vertical-align: top;" | signal | ! style="text-align: left; vertical-align: top;" | signal | ||
| style="text-align: left; vertical-align: top;" | Signal strength in dBm | | style="text-align: left; vertical-align: top;" | Signal strength in dBm | ||
| style="text-align: left; vertical-align: top;" | RUT9xx, | | style="text-align: left; vertical-align: top;" | RUT9xx, RUTx11 and TRB145 | ||
|- | |- | ||
! style="text-align: left; vertical-align: top;" | network | ! style="text-align: left; vertical-align: top;" | network | ||
| style="text-align: left; vertical-align: top;" | Network state | | style="text-align: left; vertical-align: top;" | Network state | ||
| style="text-align: left; vertical-align: top;" | RUT9xx, | | style="text-align: left; vertical-align: top;" | RUT9xx, RUTx11 and TRB145 | ||
|- | |- | ||
! style="text-align: left; vertical-align: top;" | connection | ! style="text-align: left; vertical-align: top;" | connection | ||
| style="text-align: left; vertical-align: top;" | Current connection type (2G, 3G, 4G) | | style="text-align: left; vertical-align: top;" | Current connection type (2G, 3G, 4G) | ||
| style="text-align: left; vertical-align: top;" | RUT9xx, | | style="text-align: left; vertical-align: top;" | RUT9xx, RUTx11 and TRB145 | ||
|- | |- | ||
! style="text-align: left; vertical-align: top;" | wan | ! style="text-align: left; vertical-align: top;" | wan | ||
| style="text-align: left; vertical-align: top;" | WAN IP address | | style="text-align: left; vertical-align: top;" | WAN IP address | ||
| style="text-align: left; vertical-align: top;" | RUT9xx, | | style="text-align: left; vertical-align: top;" | RUT9xx, RUTx11 and TRB145 | ||
|- | |- | ||
! style="text-align: left; vertical-align: top;" | uptime | ! style="text-align: left; vertical-align: top;" | uptime | ||