You are here: start » tools » mqtt_as

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tools:mqtt_as [2020/08/18 08:28] – [config.py] darrontools:mqtt_as [2020/08/18 23:41] (current) – external edit 127.0.0.1
Line 7: Line 7:
 ==ESP32== ==ESP32==
  
-boot.py is the MicroPython startup. The others, the MQTT demo.+boot.py is the MicroPython startup. The others are the MQTT demo.
  
 <code> <code>
Line 18: Line 18:
 ==Shell== ==Shell==
  
-Scripts to interact with mosquitto.+These scripts to interact with the mosquitto MQTT broker.
  
 <code> <code>
Line 27: Line 27:
 ===boot.py=== ===boot.py===
  
-The ESP32 startup file.+The ESP32 startup file which run our test after a short boot delay.
  
 <code> <code>
Line 42: Line 42:
 ===test.py=== ===test.py===
  
-Main executable called from startup.+Main executable called from startup. This demo is pulled from the README documentation with local changes.
  
 Configure SERVER here. Configure SERVER here.
Line 84: Line 84:
 ===config.py=== ===config.py===
  
-mqtt_as configuration as found in distribution directory with mosquitto server and wifi+mqtt_as configuration as found in distribution directory with mosquitto MQTT broker and wifi
 changes. changes.
  
-Configure MQTT server, ssid and password.+Configure MQTT broker, ssid and password.
  
 <code> <code>
Line 129: Line 129:
 ===mqtt_as.py=== ===mqtt_as.py===
  
-mqtt_as excecutable.+mqtt_as excecutable. This is the main logic which maintains a Wifi connection and publishes and subscribes to topics.
  
 <code> <code>
Line 214: Line 214:
  
 ==script== ==script==
 +
 +Subscribe to the topic named 'result' published by the ESP32 module and display it.
  
 <code> <code>
 #! /bin/bash #! /bin/bash
-while : +mosquitto_sub -h 192.168.0.13 -t result
-do +
-    mosquitto_sub -h 192.168.0.13 -t result +
-    sleep 5 +
-done+
 </code> </code>
  
 ==Shell output== ==Shell output==
 +
 +Running status for the result topic.
  
 <code> <code>
Line 234: Line 234:
  
 ==script== ==script==
 +
 +Publish two messages to the topic named 'foo_topic' which the ESP32 device is subscribed to,
  
 <code> <code>
Line 248: Line 250:
  
 ==ESP32 output== ==ESP32 output==
 +
 +Show running status on the ESP32 and incoming subscription topics.
  
 <code> <code>