Differences

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

Link to this comparison view

--- en:iot-open:practical:hardware:sut:esp32:iot_3 [2024/04/21 18:29] – [Steps] pczekalski
+++ en:iot-open:practical:hardware:sut:esp32:iot_3 [2024/04/28 16:45] (current) – [Suggested Readings and Knowledge Resources] pczekalski
@@ Line 1: / Line 1: @@
-<todo @pczekalski>Dokończyć</todo>
 ====== IOT3: Connecting to the MQTT and publishing data ======
 In the following scenario, you will learn how to connect to the MQTT broker and publish a message.
@@ Line 21: / Line 20: @@
   * [[en:iot-open:hardware2:esp32|]],
   * [[en:iot-open:practical:hardware:sut:esp32|]],
-  * [[en:iot-open:iotprogramming2:espressif_networking|]].
+  * [[en:iot-open:iotprogramming2:espressif_networking|]]
+  * [[en:iot-open:networking2:applicationnetworkprotocols|]].
 ===== Hands-on Lab Scenario =====
+Note - this scenario can be used in pair with [[[en:iot-open:practical:hardware:sut:esp32:iot_4|]] to build a publish-subscribe solution using two devices (sender and receiver). You need to book two devices then and develop them in parallel.
 ==== Task to be implemented ====
@@ Line 115: / Line 116: @@
 ===== FAQ =====
 **My MQTT client disconnects randomly**: The most common reason is you're using a non-unique MQTT client name. Please change it to some other (even random generated) and give it another try.\\
-**How do I observe messages that I send?**: Use a software client, such as [[http://mqtt-explorer.com/| MQTT Explorer]], if you're able to access the "internal IoT" network (you're in the range of the network). If you're remote, the only way is to book another device and implement a client subscribing to your message, as presented in the scenario [[[en:iot-open:practical:hardware:sut:esp32:iot_3|]]. Our MQTT broker is also visible in the campus network on the wired interfaces so that you can access it, e.g. via EduVPN or from the laboratory computers. Refer to the supervisor for IP and credentials.\\
+**How do I observe messages that I send?**: Use a software client, such as [[http://mqtt-explorer.com/| MQTT Explorer]], if you're able to access the "internal IoT" network (you're in the range of the network). If you're remote, the only way is to book another device and implement a client subscribing to your message, as presented in the scenario [[[en:iot-open:practical:hardware:sut:esp32:iot_4|]]. Our MQTT broker is also visible in the campus network on the wired interfaces so that you can access it, e.g. via EduVPN or from the laboratory computers. Refer to the supervisor for IP and credentials.\\
 **Do I need to authorise to publish and subscribe?**: Yes, you do. The supervisor provides the user and password on demand, also presented in the Node's technical documentation.

en/iot-open/practical/hardware/sut/esp32/iot_3.1713724179.txt.gz · Last modified: 2024/04/21 18:29 by pczekalski