Changes for page MQTT Forward Instruction
Last modified by Kilight Cao on 2024/08/31 16:26
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,19 +1,16 @@ 1 - **~Contents:**1 + 2 2 3 -{{toc/}} 4 4 5 - 6 6 = 1. Introduction = 7 7 8 8 Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse. 9 9 10 - 11 11 == 1.1 Support Devices == 12 12 13 13 This MQTT forward instruction is for below devices: 14 14 15 15 * Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] 16 -* LG01N, OLG01N ( (% style="color:red" %)**Warning**(%%): LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>url:https://wiki.dragino.com/index.php/Through_MQTT_to_upload_data]])13 +* LG01N, OLG01N (Warning: LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>url:https://wiki.dragino.com/index.php/Through_MQTT_to_upload_data]]) 17 17 * LG02, OLG02 18 18 * LG308, DLOS8 19 19 * LPS8 ... ... @@ -23,9 +23,7 @@ 23 23 24 24 = 2. Firmware Change Log for MQTT feature = 25 25 26 -((( 27 27 This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware. 28 -))) 29 29 30 30 * LG02_LG08-5.3.1580178039 31 31 ** Initiate version ... ... @@ -40,47 +40,33 @@ 40 40 * For Uplink: The sensor sends data to LoRa Gateway via LoRa wireless, The gateway will process these data and forward to remote MQTT Broker via Internet. 41 41 * For Downlink: The gateway subscribe a topic in the MQTT broker, when there is update on the topic, the gateway will know and broadcast the data to Local LoRa network, 42 42 43 -[[image:image -20220527133547-1.png]]38 +[[~[~[image:https://wiki.dragino.com/images/thumb/4/45/MQTT_Forward_1.png/600px-MQTT_Forward_1.png~|~|height="348" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_1.png]] 44 44 45 45 General MQTT structure 46 46 47 - 48 48 == 3.2 How sensor data is forwarded == 49 49 50 50 In this MQTT forward feature, the key point is how the gateway process the sensor data. 51 51 52 - 53 53 === 3.2.1 Upstream === 54 54 55 55 Assume there are two sensor nodes, their ID are Node1 ID: 6734 , Node2 ID: 7456. In the remote MQTT broker there are two topics: Topic1: /channel/765800, Topic2: /channel/367860. We can set up in the gateway to map Node1 to Topic1 and Node2 to Topic2. So when there is a sensor data from Node1, the gateway will forward the data to Topic1, when there is sensor data from Node2, the gateway will forward to Topic2. 56 56 57 -((( 58 58 The data flow works as below diagram. 59 -))) 60 60 61 61 [[~[~[image:https://wiki.dragino.com/images/thumb/2/2a/MQTT_Forward_2.png/600px-MQTT_Forward_2.png~|~|height="355" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_2.png]] 62 62 63 -((( 64 64 Upstream path 65 -))) 66 66 67 -((( 68 68 Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span> 69 -))) 70 70 71 -((( 72 - 73 -))) 74 - 75 75 === 3.2.2 Downstream === 76 76 77 77 The gateway subscribes to a topic of the remote MQTT broker topic. When there is some one publish a value on this topic. The gateway will get it and broadcast to local LoRa Network. 78 78 79 -((( 80 80 Below are the data flow for downstream. 81 -))) 82 82 83 -[[image:https://wiki.dragino.com/images/thumb/3/3a/MQTT_Forward_3.png/600px-MQTT_Forward_3.png||height="368" width="600"]] 64 +[[~[~[image:https://wiki.dragino.com/images/thumb/3/3a/MQTT_Forward_3.png/600px-MQTT_Forward_3.png~|~|height="368" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_3.png]] 84 84 85 85 Downstream path 86 86 ... ... @@ -89,9 +89,7 @@ 89 89 90 90 The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish. 91 91 92 -((( 93 -Currently the (% class="mark" %)**-t (topic)**(%%) and (% class="mark" %)**-m (message)**(%%) support Macros. 94 -))) 73 +Currently the -t (topic) and -m (message) support Macros. 95 95 96 96 === 3.3.1 -t topic macro === 97 97 ... ... @@ -111,7 +111,7 @@ 111 111 112 112 === 3.3.3 Example for Macro === 113 113 114 -[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]] 93 +[[~[~[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png~|~|height="385" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_9.png]] 115 115 116 116 MQTT Publish configure 117 117 ... ... @@ -122,13 +122,11 @@ 122 122 123 123 When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below: 124 124 125 -[[image:https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png||height="325" width="600"]] 104 +[[~[~[image:https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png~|~|height="325" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_20.png]] 126 126 127 127 Sensor Data 128 128 129 -((( 130 -According to above macro. Gateway will publish (% class="mark" %)**field1=22.0&field2=49.0**(%%) to topic: (% class="mark" %)**dragino-1b7060/78901/data**(%%), where 78901 is the remote channel for this node ID. 131 -))) 108 +According to above macro. Gateway will publish field1=22.0&field2=49.0 to topic: dragino-1b7060/78901/data, where 78901 is the remote channel for this node ID. 132 132 133 133 134 134 == 3.4 Modify the MQTT to support more options == ... ... @@ -135,126 +135,128 @@ 135 135 136 136 The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands. User can check the valid options by command mosquitto_pub ~-~-help. as below: 137 137 138 -(% class="box" %) 139 -((( 140 -root@dragino-1ec39c:~~# mosquitto_pub ~-~-help 115 +{{{root@dragino-1ec39c:~# mosquitto_pub --help 141 141 mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit. 142 142 mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4. 143 -\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL} 118 + 119 +Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL} 144 144 {-f file | -l | -n | -m message} 145 - [-c] [-k keepalive] [-q qos] [-r] [ ~-~-repeat N] [~-~-repeat-delay time]121 + [-c] [-k keepalive] [-q qos] [-r] [--repeat N] [--repeat-delay time] 146 146 [-A bind_address] 147 147 [-i id] [-I id_prefix] 148 - [-d] [ ~-~-quiet]124 + [-d] [--quiet] 149 149 [-M max_inflight] 150 150 [-u username [-P password]] 151 - [ ~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]]152 - [{ ~-~-cafile file |~-~-capath dir} [~-~-cert file] [~-~-key file]153 - [ ~-~-ciphers ciphers] [~-~-insecure]154 - [ ~-~-tls-alpn protocol]155 - [ ~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]156 - [ ~-~-psk hex-key~-~-psk-identity identity [~-~-ciphers ciphers]]157 - [ ~-~-proxy socks-url]158 - [ ~-~-property command identifier value]127 + [--will-topic [--will-payload payload] [--will-qos qos] [--will-retain]] 128 + [{--cafile file | --capath dir} [--cert file] [--key file] 129 + [--ciphers ciphers] [--insecure] 130 + [--tls-alpn protocol] 131 + [--tls-engine engine] [--keyform keyform] [--tls-engine-kpass-sha1]] 132 + [--psk hex-key --psk-identity identity [--ciphers ciphers]] 133 + [--proxy socks-url] 134 + [--property command identifier value] 159 159 [-D command identifier value] 160 - mosquitto_pub ~-~-help 161 -\\-A : bind the outgoing socket to this host/ip address. Use to control which interface 136 + mosquitto_pub --help 137 + 138 + -A : bind the outgoing socket to this host/ip address. Use to control which interface 162 162 the client communicates over. 163 --d : enable debug messages. 164 --D : Define MQTT v5 properties. See the documentation for more details. 165 --f : send the contents of a file as the message. 166 --h : mqtt host to connect to. Defaults to localhost. 167 --i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id. 168 --I : define the client id as id_prefix appended with the process id. Useful for when the 140 + -d : enable debug messages. 141 + -D : Define MQTT v5 properties. See the documentation for more details. 142 + -f : send the contents of a file as the message. 143 + -h : mqtt host to connect to. Defaults to localhost. 144 + -i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id. 145 + -I : define the client id as id_prefix appended with the process id. Useful for when the 169 169 broker is using the clientid_prefixes option. 170 --k : keep alive in seconds for this client. Defaults to 60. 171 --L : specify user, password, hostname, port and topic as a URL in the form: 172 - mqtt(s): ~/~/[username[:password]@]host[:port]/topic173 --l : read messages from stdin, sending a separate message for each line. 174 --m : message payload to send. 175 --M : the maximum inflight messages for QoS 1/2.. 176 --n : send a null (zero length) message. 177 --p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS. 178 --P : provide a password 179 --q : quality of service level to use for all messages. Defaults to 0. 180 --r : message should be retained. 181 --s : read message from stdin, sending the entire input as a message. 182 --t : mqtt topic to publish to. 183 --u : provide a username 184 --V : specify the version of the MQTT protocol to use when connecting. 147 + -k : keep alive in seconds for this client. Defaults to 60. 148 + -L : specify user, password, hostname, port and topic as a URL in the form: 149 + mqtt(s)://[username[:password]@]host[:port]/topic 150 + -l : read messages from stdin, sending a separate message for each line. 151 + -m : message payload to send. 152 + -M : the maximum inflight messages for QoS 1/2.. 153 + -n : send a null (zero length) message. 154 + -p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS. 155 + -P : provide a password 156 + -q : quality of service level to use for all messages. Defaults to 0. 157 + -r : message should be retained. 158 + -s : read message from stdin, sending the entire input as a message. 159 + -t : mqtt topic to publish to. 160 + -u : provide a username 161 + -V : specify the version of the MQTT protocol to use when connecting. 185 185 Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311. 186 - ~-~-help : display this message.187 - ~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.188 - ~-~-repeat-delay : if using~-~-repeat, wait time seconds between publishes. Defaults to 0.189 - ~-~-quiet :(% class="mark" %)don't print error messages.190 - ~-~-will-payload : payload for the client Will, which is sent by the broker in case of163 + --help : display this message. 164 + --repeat : if publish mode is -f, -m, or -s, then repeat the publish N times. 165 + --repeat-delay : if using --repeat, wait time seconds between publishes. Defaults to 0. 166 + --quiet : don't print error messages. 167 + --will-payload : payload for the client Will, which is sent by the broker in case of 191 191 unexpected disconnection. If not given and will-topic is set, a zero 192 192 length message will be sent. 193 - ~-~-will-qos : QoS level for the client Will.194 - ~-~-will-retain : if given, make the client Will retained.195 - ~-~-will-topic : the topic on which to publish the client Will.196 - ~-~-cafile : path to a file containing trusted CA certificates to enable encrypted170 + --will-qos : QoS level for the client Will. 171 + --will-retain : if given, make the client Will retained. 172 + --will-topic : the topic on which to publish the client Will. 173 + --cafile : path to a file containing trusted CA certificates to enable encrypted 197 197 communication. 198 - ~-~-capath : path to a directory containing trusted CA certificates to enable encrypted175 + --capath : path to a directory containing trusted CA certificates to enable encrypted 199 199 communication. 200 - ~-~-cert : client certificate for authentication, if required by server.201 - ~-~-key : client private key for authentication, if required by server.202 - ~-~-keyform : keyfile type, can be either "pem" or "engine".203 - ~-~-ciphers : openssl compatible list of TLS ciphers to support.204 - ~-~-tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1.177 + --cert : client certificate for authentication, if required by server. 178 + --key : client private key for authentication, if required by server. 179 + --keyform : keyfile type, can be either "pem" or "engine". 180 + --ciphers : openssl compatible list of TLS ciphers to support. 181 + --tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1. 205 205 Defaults to tlsv1.2 if available. 206 - ~-~-insecure : do not check that the server certificate hostname matches the remote183 + --insecure : do not check that the server certificate hostname matches the remote 207 207 hostname. Using this option means that you cannot be sure that the 208 208 remote host is the server you wish to connect to and so is insecure. 209 209 Do not use this option in a production environment. 210 - ~-~-tls-engine : If set, enables the use of a TLS engine device.211 - ~-~-tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine.212 - ~-~-psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode.213 - ~-~-psk-identity : client identity string for TLS-PSK mode.214 - ~-~-proxy : SOCKS5 proxy URL of the form:215 - socks5h: ~/~/[username[:password]@]hostname[:port]187 + --tls-engine : If set, enables the use of a TLS engine device. 188 + --tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine. 189 + --psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode. 190 + --psk-identity : client identity string for TLS-PSK mode. 191 + --proxy : SOCKS5 proxy URL of the form: 192 + socks5h://[username[:password]@]hostname[:port] 216 216 Only "none" and "username" authentication is supported. 217 - \\See https:~/~/mosquitto.org/ for more information.218 - )))194 + 195 +See https://mosquitto.org/ for more information.}}} 219 219 220 220 221 -((( 222 222 and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines: 223 -))) 224 224 225 -(% class="box" %) 226 -((( 227 -# Call MQTT Publish command 228 -\\# 1. Case with User, Password and Client ID present (e.g. Azure) 200 +{{{# Call MQTT Publish command 201 + 202 +# 1. Case with User, Password and Client ID present (e.g. Azure) 229 229 if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 230 -case="1" 231 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user -P "$pass" $C $cafile $PUB_FLAG "$mqtt_data" 232 -\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS) 204 + case="1" 205 + mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user -P "$pass" $C $cafile $PUB_FLAG "$mqtt_data" 206 + 207 +# 2. Case with Certificate, Key and ClientID present (e.g. AWS) 233 233 elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then 234 -case="2" 235 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic ~-~-cert $cert ~-~-key $key $C $cafile $PUB_FLAG "$mqtt_data" 236 -\\# 3. Case with no User, Certificate or ClientID present 209 + case="2" 210 + mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic --cert $cert --key $key $C $cafile $PUB_FLAG "$mqtt_data" 211 + 212 +# 3. Case with no User, Certificate or ClientID present 237 237 elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then 238 -case="3" 239 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data" 240 -\\# 4. Case with no User, Certificate, but with ClientID present 214 + case="3" 215 + mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data" 216 + 217 +# 4. Case with no User, Certificate, but with ClientID present 241 241 elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then 242 -case="4" 243 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data" 244 -\\# 5. Case with User and ClientID present, but no Password and no Certificate present 219 + case="4" 220 + mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data" 221 + 222 +# 5. Case with User and ClientID present, but no Password and no Certificate present 245 245 elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 246 -case="5" 247 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data" 248 -\\# 6. Case with User and Password present, but no ClientID and no Certificate present 224 + case="5" 225 + mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data" 226 + 227 +# 6. Case with User and Password present, but no ClientID and no Certificate present 249 249 elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then 250 -case="6" 251 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data" 252 -\\# 0. Else - invalid parameters, just log 229 + case="6" 230 + mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data" 231 + 232 +# 0. Else - invalid parameters, just log 253 253 else 254 -case="Invalid parameters" 255 -logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called." 256 -fi 257 -))) 234 + case="Invalid parameters" 235 + logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called." 236 +fi}}} 258 258 259 259 260 260 = 4. Example to communicate to a simple MQTT server = ... ... @@ -267,23 +267,21 @@ 267 267 268 268 The [[MQTT.fx>>url:http://mqttfx.jensd.de/index.php/download]] is a MQTT client tool. We can use this to simulate a MQTT connection to our MQTT broker first to make sure the MQTT broker works. This will also help us understand how it works. 269 269 270 -((( 271 271 In this test, the MQTT broker and MQTT.fx are installed in the same PC, so the MQTT server address in MQTT.fx should be localhost. Below shows how to connect to the server. 272 -))) 273 273 274 -[[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]] 251 +[[~[~[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png~|~|height="201" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_4.png]] 275 275 276 276 Connect to MQTT Broker 277 277 278 278 After connected, use publish to public some thing to MQTT server. This to simulate upsteam 279 279 280 -[[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png||height="149" width="600"]] 257 +[[~[~[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png~|~|height="149" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_5.png]] 281 281 282 282 Upstream: Publish message to MQTT Broker 283 283 284 284 To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below: 285 285 286 -[[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png||height="279" width="600"]] 263 +[[~[~[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png~|~|height="279" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_6.png]] 287 287 288 288 Downstream: Subscribe a topic to get downstream 289 289 ... ... @@ -295,7 +295,7 @@ 295 295 In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection. 296 296 297 297 298 - (% class="mark" %)**For Upstream**275 +For Upstream 299 299 300 300 command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]] 301 301 ... ... @@ -303,82 +303,65 @@ 303 303 304 304 Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network. 305 305 306 -[[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png||height="188" width="600"]] 283 +[[~[~[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png~|~|height="188" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_6.png]] 307 307 308 308 mosquitto_pub 309 309 310 310 311 - (% class="mark" %)**For Downstream**288 +For Downstream 312 312 313 313 Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic. 314 314 315 -[[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png||height="267" width="600"]] 292 +[[~[~[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png~|~|height="267" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_7.png]] 316 316 317 317 mosquitto_sub 318 318 319 - 320 320 == 4.4 Configure Dragino UI for MQTT connection == 321 321 322 322 This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection. 323 323 324 -((( 325 -Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client** 326 -))) 300 +Go to Dragino Menu ~-~-> MQTT Client 327 327 328 -[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]] 302 +[[~[~[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png~|~|height="249" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_8.png]] 329 329 330 330 go to mqtt configure menu 331 331 332 -((( 333 -Select **Forward to MQTT server**. (% class="mark" %)**Notice**(%%): This option is removed from the latest firmware, in the latest firmware, if user submit "SAVE & APPLY" in MQTT page, the gateway will use MQTT service. 334 -))) 306 +Select Forward to MQTT server. Notice: This option is removed from the latest firmware, in the latest firmware, if user submit "SAVE & APPLY" in MQTT page, the gateway will use MQTT service. 335 335 336 -[[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]] 308 +[[~[~[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png~|~|height="240" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Commands_8.png]] 337 337 338 338 forward to MQTT 339 339 340 - 341 341 === 4.4.1 Configure the MQTT Client for Upstream === 342 342 343 343 Below screenshot is same as the publish command: 344 344 345 -(% class="box" %) 346 -((( 347 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 348 -~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for 349 -~/~/CLIENTID: dragino-1b7060 350 -~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 351 -~/~/DATA: The data stores in /var/iot/channels/ 352 -))) 316 +{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 317 +//where the CLIENTID, CHANNEL & DATA are macro. represent for 318 +//CLIENTID: dragino-1b7060 319 +//CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 320 +//DATA: The data stores in /var/iot/channels/ 321 +}}} 353 353 354 -[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]] 323 +[[~[~[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png~|~|height="385" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_9.png]] 355 355 356 356 MQTT Publish configure 357 357 327 +[[~[~[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png~|~|height="544" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_10.png]] 358 358 359 -[[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]] 360 - 361 361 MQTT Channel settings 362 362 363 -((( 364 364 For example, if we put a data(temp=46) on the file /var/iot/channels/4567, because 4567 match the remote channel 78901. the gateway will run this command: 365 -))) 366 366 367 -(% class="box" %) 368 -((( 369 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46 370 -))) 333 +{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46 334 +}}} 371 371 372 -((( 373 373 to MQTT broker. 374 -))) 375 375 376 376 377 -((( 378 378 Below is a simulation to put this data to active the MQTT publish. 379 -))) 380 380 381 -[[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]] 341 +[[~[~[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png~|~|height="308" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_11.png]] 382 382 383 383 MQTT Publish 384 384 ... ... @@ -387,21 +387,17 @@ 387 387 388 388 Below screen shot equal to this subscribe command: 389 389 390 -(% class="box" %) 391 -((( 392 -mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 393 -))) 350 +{{{ mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 351 +}}} 394 394 395 -[[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]] 353 +[[~[~[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png~|~|height="173" width="579"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_12.png]] 396 396 397 397 MQTT Subscribe 398 398 399 399 400 -((( 401 401 When MQTT broker receive a update on this topic, the gateway will get the update and use LoRa radio to broadcast this message. The LoRa parameters used for update is: 402 -))) 403 403 404 -[[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]] 360 +[[~[~[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png~|~|height="300" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_13.png]] 405 405 406 406 LoRa Broadcast parameters. 407 407 ... ... @@ -408,11 +408,13 @@ 408 408 409 409 And below is the subscribe simulation: 410 410 411 -[[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png||height="255" width="600"]] 367 +[[~[~[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png~|~|height="255" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_14.png]] 412 412 413 413 downstream simulation 414 414 415 415 372 +\\ 373 + 416 416 == 4.5 Add LoRa support to communicate with remote sensor == 417 417 418 418 In above section, we have configured the UI to support MQTT upstream and downstream. We can simulate via Linux command. In this section, we will guide how to communicate with remote LoRa End Node for upstream and downstream. ... ... @@ -419,27 +419,19 @@ 419 419 420 420 === 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 === 421 421 422 -((( 423 423 We can use [[LoRa Shield>>url:http://www.dragino.com/products/lora/item/102-lora-shield.html]] to send LoRa Raw data to Gateway and receive data from gateway. 424 -))) 425 425 426 -((( 427 427 The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]] 428 -))) 429 429 430 -((( 431 431 And this link is the required library: [[arduino-LoRa-master>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]. Unzip this library and put in Arduino library location. 432 -))) 433 433 434 -((( 435 435 What does the Arduino Sketch do? The Arduino Sketch will: 436 -))) 437 437 438 438 * Upstream: Keep sending a LoRa Message every minutes with this payload : <4567>tem=xx&hum=yy (Where xx and yy are temperature and humidity value generated randomly). 439 439 * Downstream: Listening broadcast message from gateway, and print it in console. 440 440 * The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below: 441 441 442 -[[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png||height="197" width="600"]] 392 +[[~[~[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png~|~|height="197" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_17.png]] 443 443 444 444 LoRa Parameter should match 445 445 ... ... @@ -446,11 +446,11 @@ 446 446 447 447 Below is the test result after the Arduino Sketch is running. 448 448 449 -[[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png||height="319" width="600"]] 399 +[[~[~[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png~|~|height="319" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_18.png]] 450 450 451 451 Upstream Data Flow 452 452 453 -[[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png||height="309" width="600"]] 403 +[[~[~[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png~|~|height="309" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_19.png]] 454 454 455 455 Downstream Data Flow 456 456 ... ... @@ -457,107 +457,96 @@ 457 457 458 458 === 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 === 459 459 460 -((( 461 -Since firmware (% class="mark" %)**LG02_LG08~-~-build-v5.3.1585192026-20200326-1109,**(%%) Dragino LoRaWAN gateways support the communication to LoRaWAN (% class="mark" %)**ABP end node**(%%) locally without the need of LoRaWAN server. This feature allow us to integrate MQTT in the gateway to support LoRaWAN to MQTT forwarding or visa verse. 462 -))) 410 +Since firmware LG02_LG08~-~-build-v5.3.1585192026-20200326-1109, Dragino LoRaWAN gateways support the communication to LoRaWAN ABP end node locally without the need of LoRaWAN server. This feature allow us to integrate MQTT in the gateway to support LoRaWAN to MQTT forwarding or visa verse. 463 463 464 -((( 465 -When use test this feature, please use the version higher then : (% class="mark" %)**LG02_LG08~-~-build-v5.4.1593400722-20200629-1120**(%%), in this version, the upload format is changed and readable, which is easier for integration. 466 -(% class="mark" %)**Video Instruction**(%%):[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 467 -))) 412 +When use test this feature, please use the version higher then : LG02_LG08~-~-build-v5.4.1593400722-20200629-1120, in this version, the upload format is changed and readable, which is easier for integration. 468 468 469 -((( 470 -**Step 1**: Refer [[Communicate with ABP End Node>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node]] to know how to set up LG308 to work with LoRaWAN End node. 471 -))) 472 472 473 -((( 474 -**Step 2**: Make sure your Radio settings match the End Node settings. 475 -))) 415 +\\Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 416 + 476 476 477 -[[ image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png||height="387"width="600"]]418 +Step 1: Refer [[Communicate with ABP End Node>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node]] to know how to set up LG308 to work with LoRaWAN End node. 478 478 420 +Step 2: Make sure your Radio settings match the End Node settings. 421 + 422 +[[~[~[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png~|~|height="387" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_5.png]] 423 + 479 479 Use Same Frequency Band as End Node 480 480 481 481 482 -((( 483 -((( 484 -**Step 3**: Set up publish format and MQTT channel. The LG308 will store the Data from End node in HEX format in the file. And we need to config the format to META 485 -))) 486 -))) 427 +Step 3: Set up publish format and MQTT channel. The LG308 will store the Data from End node in HEX format in the file. And we need to config the format to META 487 487 488 -[[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png||height="385" width="600"]] 429 +[[~[~[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png~|~|height="385" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_3.png]] 489 489 490 490 Publish mush use META as data format for LG308 491 491 492 492 493 - **Step 4**: Map the Device Address to Remote ID in MQTT server.434 +Step 4: Map the Device Address to Remote ID in MQTT server. 494 494 495 -[[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]] 436 +[[~[~[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png~|~|height="335" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_4.png]] 496 496 497 497 Map Dev Addr to remote ID 498 498 499 499 500 - **Step 5: Upstream**: Save the change, we can see the log info via "sytem log", End Node and MQTT Server441 +Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server 501 501 502 -[[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]] 443 +[[~[~[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png~|~|height="279" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_6.png]] 503 503 504 504 Upstream Process 505 505 506 -[[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png||height="246" width="600"]] 447 +[[~[~[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png~|~|height="246" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_6_1.png]] 507 507 508 508 Choose ASCII Format 509 509 510 -[[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png||height="248" width="600"]] 451 +[[~[~[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png~|~|height="248" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_6_2.png]] 511 511 512 512 LHT65 Decoder 513 513 455 +Step 6: Set up subscribe: Subscribe a topci for downstream. 514 514 515 - **Step 6:Setupubscribe:** Subscribeatopcifordownstream.457 +[[~[~[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png~|~|height="176" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_7.png]] 516 516 517 -[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]] 518 - 519 519 Subscribe to a topic 520 520 521 521 522 - **Step 7**: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.462 +Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 523 523 524 -[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]] 464 +[[~[~[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png~|~|height="298" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_8.png]] 525 525 526 526 Downstream Flow 527 527 528 - (% class="mark" %)**Notice: The text use for Downstream must meet the requirement from [[LG308 Downstream Payload>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node#Downstream]]**468 +Notice: The text use for Downstream must meet the requirement from [[LG308 Downstream Payload>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node#Downstream]] 529 529 530 530 531 531 = 5. Example For Different MQTT Servers = 532 532 533 -(% style="width:731.222px" %) 534 -|=(% style="width: 270px;" %)((( 535 -[[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png||alt="ThingSpeak1.png" height="114" width="233"]] 473 +|=((( 474 +[[~[~[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png~|~|alt="ThingSpeak1.png" height="98" width="200"~]~]>>url:https://wiki.dragino.com/index.php/File:ThingSpeak1.png]] 536 536 537 -== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] == 476 +=== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] === 538 538 539 539 540 540 [[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]] 541 -)))|=( % style="width: 242px;" %)(((542 -[[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height=" 65" width="223"]]480 +)))|=((( 481 +[[~[~[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png~|~|alt="Lewei50.png" height="58" width="200"~]~]>>url:https://wiki.dragino.com/index.php/File:Lewei50.png]] 543 543 483 +=== [[乐联网平台>>url:https://www.lewei50.com/]] === 544 544 545 -== [[乐联网平台>>url:https://www.lewei50.com/]] == 546 546 486 +[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]] 487 +)))|=((( 488 +[[~[~[image:https://wiki.dragino.com/images/thumb/a/aa/AWS-IOT.png/200px-AWS-IOT.png~|~|alt="AWS-IOT.png" height="122" width="200"~]~]>>url:https://wiki.dragino.com/index.php/File:AWS-IOT.png]] 547 547 548 -[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]] 549 -)))|=(% style="width: 214px;" %)((( 550 -[[image:https://wiki.dragino.com/images/thumb/a/aa/AWS-IOT.png/200px-AWS-IOT.png||alt="AWS-IOT.png" height="112" width="183"]] 490 +=== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] === 551 551 552 -== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] == 553 553 554 - 555 555 [[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]] 556 556 ))) 557 557 496 + 558 558 = 6. How to Debug = 559 559 560 -User can login the gateway's console and run (% class="mark" %)**logread -f**(%%). It will shows the output when there is packet arrive.User can see if it is correct.499 +User can login the gateway's console and run **logread -f**. It will shows the output when there is packet arrive.User can see if it is correct. 561 561 562 562 = 7. How to ask for Support = 563 563
- image-20220527133547-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -199.3 KB - Content
- image-20220527134000-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -115.8 KB - Content
- image-20220527134038-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -94.2 KB - Content