This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:iot-open:practical:hardware:sut:stm32:iot_3 [2024/04/27 09:33] – [FAQ] ktokarz | en:iot-open:practical:hardware:sut:stm32:iot_3 [2024/04/27 09:42] (current) – ktokarz | ||
---|---|---|---|
Line 85: | Line 85: | ||
In our case, the command can look like this: | In our case, the command can look like this: | ||
< | < | ||
- | AT+MQTTUSERCFG=0, | + | AT+MQTTUSERCFG=0, |
</ | </ | ||
Line 100: | Line 100: | ||
The command can look like this: | The command can look like this: | ||
< | < | ||
- | AT+MQTTCONN=0, | + | AT+MQTTCONN=0, |
</ | </ | ||
Line 116: | Line 116: | ||
=== Step 3 === | === Step 3 === | ||
- | Implement the MQTT configuration and connection to the broker. Use the template for the " | + | Implement the MQTT configuration and connection to the broker. Use the template for the " |
=== Step 4 === | === Step 4 === | ||
Line 128: | Line 128: | ||
===== FAQ ===== | ===== FAQ ===== | ||
- | **Can I publish messages on different topics?**: Certainly you can. You can publish the readings of the temperature sensor with one topic, and readings of the humidity with another. The limit of the number of different topics comes only from the available resources of the MQTT broker. | + | **Can I publish messages on different topics?**: Certainly you can. You can publish the readings of the temperature sensor with one topic, and readings of the humidity with another. The limit of the number of different topics comes only from the available resources of the MQTT broker.\\ |
+ | **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.\\ | ||
+ | **Do I need to authorise to publish and subscribe? | ||
<WRAP noprint> | <WRAP noprint> |