351
edits
MQTT Broker: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
Normally messages aren't stored anywhere. They just get sent out and received by whoever happens to be listening to the same topic. However, we automatically log messages to the <code>sensors/</code> topics using [https://github.com/influxdata/telegraf/tree/master/plugins/inputs/mqtt_consumer Telegraf] + [https://github.com/influxdata/influxdb#influxdb- InfluxDB]. | Normally messages aren't stored anywhere. They just get sent out and received by whoever happens to be listening to the same topic. However, we automatically log messages to the <code>sensors/</code> topics using [https://github.com/influxdata/telegraf/tree/master/plugins/inputs/mqtt_consumer Telegraf] + [https://github.com/influxdata/influxdb#influxdb- InfluxDB]. | ||
==== Topics ==== | |||
MQTT topics consist of categories separated by slashes. Here are some topics currently in use: | |||
* sensors/air/0/temp | |||
* sensors/air/0/pm25 | |||
* sensors/air/1/temp | |||
* sensors/air/1/pm25 | |||
You can use <code>+</code> as a wildcard to match a single hierarchy when subscribing. For example, <code>sensors/air/+/temp</code> will subscribe to all air temperature sensors. | |||
You can use <code>#</code> as a wildcard to match all '''remaining''' hierarchies. It must be the last character. For example, <code>sensors/#</code> will subscribe to all sensors. | |||
===Access=== | ===Access=== | ||