| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:iot-open:practical:hardware:sut:esp32:iot_3 [2024/04/21 18:55] – [Hands-on Lab Scenario] pczekalski | en:iot-open:practical:hardware:sut:esp32:iot_3 [2024/04/28 16:45] (current) – [Suggested Readings and Knowledge Resources] pczekalski |
|---|
| * [[en:iot-open:hardware2:esp32|]], | * [[en:iot-open:hardware2:esp32|]], |
| * [[en:iot-open:practical:hardware:sut: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 ===== | ===== Hands-on Lab Scenario ===== |
| ===== FAQ ===== | ===== 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.\\ | **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. | **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. |
| |
