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
en:iot-open:practical:hardware:sut:stm32:iot_3 [2024/04/27 08:09] – [Steps] ktokarzen: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:
 <code> <code>
-AT+MQTTUSERCFG=0,1,\"STM32#0001\",\"vrel\",\"vrel2018\",0,0,\"\"+AT+MQTTUSERCFG=0,1,\"STM32#0001\",\"username\",\"password\",0,0,\"\"
 </code> </code>
  
Line 100: Line 100:
 The command can look like this: The command can look like this:
 <code> <code>
-AT+MQTTCONN=0,\"192.168.1.90\",1883,1+AT+MQTTCONN=0,\"192.168.1.100\",1883,1
 </code> </code>
  
Line 116: Line 116:
  
 === Step 3 === === Step 3 ===
-Implement the MQTT configuration and connection to the broker. Use the template for the "AT" command from first step. Ensure that your node is successfully connected.+Implement the MQTT configuration and connection to the broker. Use the template for the "AT" command from the first step. Ensure that your node is successfully connected.
  
 === Step 4 === === Step 4 ===
Line 122: Line 122:
  
 ==== Result validation ==== ==== Result validation ====
-You should be able to connect to the WiFi and MQTT broker (verified by the status present on the selected display) and then publish a message (once or periodically). Depending on whether you're fully remote or able to access our networks with an additional device, you need to implement a subscriber (as present in the scenario [[[en:iot-open:practical:hardware:sut:esp32:iot_4|]]) or use MQTT Explorer (or any other application capable of connecting to our MQTT Broker) to observe messages that you publish.+You should be able to connect to the WiFi and MQTT broker (verified by the status present on the selected display) and then publish a message (once or periodically). Depending on whether you're fully remote or able to access our networks with an additional device, you need to implement a subscriber (as present in the scenario [[[en:iot-open:practical:hardware:sut:stm32:iot_4|]]) or use MQTT Explorer (or any other application capable of connecting to our MQTT Broker) to observe messages that you publish. 
 +<note info> 
 +Because LCD can't properly display some non-visible characters the presented code sometimes shows additional, non-letter characters. It is out of the scope of this scenario to filter these characters out. We leave the task of making visual improvements to your invention. 
 +</note>
  
 ===== FAQ ===== ===== FAQ =====
-**Can I change the IP address?**: Normally IP addresses are assigned by the server known as DHCP. In some situations, you can use static IP assigned manually in the stationIt is not advised, however, because you may accidentally generate an overlapping address that will collide with another device in the same network.+**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 anotherThe 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?**: Yes, you do. The supervisor provides the user and password on demand, also presented in the Node's technical documentation.
  
 <WRAP noprint> <WRAP noprint>
en/iot-open/practical/hardware/sut/stm32/iot_3.1714205372.txt.gz · Last modified: 2024/04/27 08:09 by ktokarz
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0