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)
Details
- Page properties
-
- Content
-
... ... @@ -1,8 +1,6 @@ 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. ... ... @@ -12,7 +12,7 @@ 12 12 This MQTT forward instruction is for below devices: 13 13 14 14 * Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] 15 -* LG01N, OLG01N ( (% class="mark" %)**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]]) 16 16 * LG02, OLG02 17 17 * LG308, DLOS8 18 18 * LPS8 ... ... @@ -22,9 +22,7 @@ 22 22 23 23 = 2. Firmware Change Log for MQTT feature = 24 24 25 -((( 26 26 This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware. 27 -))) 28 28 29 29 * LG02_LG08-5.3.1580178039 30 30 ** Initiate version ... ... @@ -39,47 +39,33 @@ 39 39 * 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. 40 40 * 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, 41 41 42 -[[image:https://wiki.dragino.com/images/thumb/4/45/MQTT_Forward_1.png/600px-MQTT_Forward_1.png||height="348" width="600"]] 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]] 43 43 44 44 General MQTT structure 45 45 46 - 47 47 == 3.2 How sensor data is forwarded == 48 48 49 49 In this MQTT forward feature, the key point is how the gateway process the sensor data. 50 50 51 - 52 52 === 3.2.1 Upstream === 53 53 54 54 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. 55 55 56 -((( 57 57 The data flow works as below diagram. 58 -))) 59 59 60 60 [[~[~[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]] 61 61 62 -((( 63 63 Upstream path 64 -))) 65 65 66 -((( 67 67 Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span> 68 -))) 69 69 70 -((( 71 - 72 -))) 73 - 74 74 === 3.2.2 Downstream === 75 75 76 76 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. 77 77 78 -((( 79 79 Below are the data flow for downstream. 80 -))) 81 81 82 -[[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]] 83 83 84 84 Downstream path 85 85 ... ... @@ -88,9 +88,7 @@ 88 88 89 89 The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish. 90 90 91 -((( 92 -Currently the (% class="mark" %)**-t (topic)**(%%) and (% class="mark" %)**-m (message)**(%%) support Macros. 93 -))) 73 +Currently the -t (topic) and -m (message) support Macros. 94 94 95 95 === 3.3.1 -t topic macro === 96 96 ... ... @@ -110,7 +110,7 @@ 110 110 111 111 === 3.3.3 Example for Macro === 112 112 113 -[[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]] 114 114 115 115 MQTT Publish configure 116 116 ... ... @@ -121,13 +121,11 @@ 121 121 122 122 When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below: 123 123 124 -[[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]] 125 125 126 126 Sensor Data 127 127 128 -((( 129 -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. 130 -))) 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. 131 131 132 132 133 133 == 3.4 Modify the MQTT to support more options == ... ... @@ -134,136 +134,128 @@ 134 134 135 135 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: 136 136 137 -(% class="box" %) 138 -((( 139 -root@dragino-1ec39c:~~# mosquitto_pub ~-~-help 115 +{{{root@dragino-1ec39c:~# mosquitto_pub --help 140 140 mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit. 141 141 mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4. 142 - 118 + 143 143 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 ~-~-help161 - 162 --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 163 163 the client communicates over. 164 --d : enable debug messages. 165 --D : Define MQTT v5 properties. See the documentation for more details. 166 --f : send the contents of a file as the message. 167 --h : mqtt host to connect to. Defaults to localhost. 168 --i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id. 169 --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 170 170 broker is using the clientid_prefixes option. 171 --k : keep alive in seconds for this client. Defaults to 60. 172 --L : specify user, password, hostname, port and topic as a URL in the form: 173 - mqtt(s): ~/~/[username[:password]@]host[:port]/topic174 --l : read messages from stdin, sending a separate message for each line. 175 --m : message payload to send. 176 --M : the maximum inflight messages for QoS 1/2.. 177 --n : send a null (zero length) message. 178 --p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS. 179 --P : provide a password 180 --q : quality of service level to use for all messages. Defaults to 0. 181 --r : message should be retained. 182 --s : read message from stdin, sending the entire input as a message. 183 --t : mqtt topic to publish to. 184 --u : provide a username 185 --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. 186 186 Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311. 187 - ~-~-help : display this message.188 - ~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.189 - ~-~-repeat-delay : if using~-~-repeat, wait time seconds between publishes. Defaults to 0.190 - ~-~-quiet :(% class="mark" %)don't print error messages.191 - ~-~-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 192 192 unexpected disconnection. If not given and will-topic is set, a zero 193 193 length message will be sent. 194 - ~-~-will-qos : QoS level for the client Will.195 - ~-~-will-retain : if given, make the client Will retained.196 - ~-~-will-topic : the topic on which to publish the client Will.197 - ~-~-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 198 198 communication. 199 - ~-~-capath : path to a directory containing trusted CA certificates to enable encrypted175 + --capath : path to a directory containing trusted CA certificates to enable encrypted 200 200 communication. 201 - ~-~-cert : client certificate for authentication, if required by server.202 - ~-~-key : client private key for authentication, if required by server.203 - ~-~-keyform : keyfile type, can be either "pem" or "engine".204 - ~-~-ciphers : openssl compatible list of TLS ciphers to support.205 - ~-~-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. 206 206 Defaults to tlsv1.2 if available. 207 - ~-~-insecure : do not check that the server certificate hostname matches the remote183 + --insecure : do not check that the server certificate hostname matches the remote 208 208 hostname. Using this option means that you cannot be sure that the 209 209 remote host is the server you wish to connect to and so is insecure. 210 210 Do not use this option in a production environment. 211 - ~-~-tls-engine : If set, enables the use of a TLS engine device.212 - ~-~-tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine.213 - ~-~-psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode.214 - ~-~-psk-identity : client identity string for TLS-PSK mode.215 - ~-~-proxy : SOCKS5 proxy URL of the form:216 - 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] 217 217 Only "none" and "username" authentication is supported. 218 - 219 -See https:~/~/mosquitto.org/ for more information. 220 -))) 194 + 195 +See https://mosquitto.org/ for more information.}}} 221 221 222 222 223 -((( 224 224 and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines: 225 -))) 226 226 227 -(% class="box" %) 228 -((( 229 -# Call MQTT Publish command 230 - 231 -# 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) 232 232 if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 233 -case="1" 234 -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" 235 - 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 + 236 236 # 2. Case with Certificate, Key and ClientID present (e.g. AWS) 237 237 elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then 238 -case="2" 239 -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"240 - 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 + 241 241 # 3. Case with no User, Certificate or ClientID present 242 242 elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then 243 -case="3" 244 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data" 245 - 214 + case="3" 215 + mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data" 216 + 246 246 # 4. Case with no User, Certificate, but with ClientID present 247 247 elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then 248 -case="4" 249 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data" 250 - 219 + case="4" 220 + mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data" 221 + 251 251 # 5. Case with User and ClientID present, but no Password and no Certificate present 252 252 elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 253 -case="5" 254 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data" 255 - 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 + 256 256 # 6. Case with User and Password present, but no ClientID and no Certificate present 257 257 elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then 258 -case="6" 259 -mosquitto_pub $D -h $server -p $port -q $pub_qos 260 - 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 + 261 261 # 0. Else - invalid parameters, just log 262 262 else 263 -case="Invalid parameters" 264 -logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called." 265 -fi 266 -))) 234 + case="Invalid parameters" 235 + logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called." 236 +fi}}} 267 267 268 268 269 269 = 4. Example to communicate to a simple MQTT server = ... ... @@ -276,23 +276,21 @@ 276 276 277 277 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. 278 278 279 -((( 280 280 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. 281 -))) 282 282 283 -[[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]] 284 284 285 285 Connect to MQTT Broker 286 286 287 287 After connected, use publish to public some thing to MQTT server. This to simulate upsteam 288 288 289 -[[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]] 290 290 291 291 Upstream: Publish message to MQTT Broker 292 292 293 293 To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below: 294 294 295 -[[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]] 296 296 297 297 Downstream: Subscribe a topic to get downstream 298 298 ... ... @@ -304,7 +304,7 @@ 304 304 In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection. 305 305 306 306 307 - (% class="mark" %)**For Upstream**275 +For Upstream 308 308 309 309 command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]] 310 310 ... ... @@ -312,59 +312,51 @@ 312 312 313 313 Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network. 314 314 315 -[[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]] 316 316 317 317 mosquitto_pub 318 318 319 319 320 - (% class="mark" %)**For Downstream**288 +For Downstream 321 321 322 322 Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic. 323 323 324 -[[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]] 325 325 326 326 mosquitto_sub 327 327 328 - 329 329 == 4.4 Configure Dragino UI for MQTT connection == 330 330 331 331 This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection. 332 332 333 -((( 334 -Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client** 335 -))) 300 +Go to Dragino Menu ~-~-> MQTT Client 336 336 337 -[[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]] 338 338 339 339 go to mqtt configure menu 340 340 341 -((( 342 -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. 343 -))) 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. 344 344 345 -[[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]] 346 346 347 347 forward to MQTT 348 348 349 - 350 350 === 4.4.1 Configure the MQTT Client for Upstream === 351 351 352 352 Below screenshot is same as the publish command: 353 353 354 -(% class="box" %) 355 -((( 356 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 357 -~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for 358 -~/~/CLIENTID: dragino-1b7060 359 -~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 360 -~/~/DATA: The data stores in /var/iot/channels/ 361 -))) 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 +}}} 362 362 363 -[[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]] 364 364 365 365 MQTT Publish configure 366 366 367 -[[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]] 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]] 368 368 369 369 MQTT Channel settings 370 370 ... ... @@ -378,7 +378,7 @@ 378 378 379 379 Below is a simulation to put this data to active the MQTT publish. 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 ... ... @@ -390,7 +390,7 @@ 390 390 {{{ mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 391 391 }}} 392 392 393 -[[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]] 394 394 395 395 MQTT Subscribe 396 396 ... ... @@ -397,7 +397,7 @@ 397 397 398 398 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: 399 399 400 -[[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]] 401 401 402 402 LoRa Broadcast parameters. 403 403 ... ... @@ -404,11 +404,13 @@ 404 404 405 405 And below is the subscribe simulation: 406 406 407 -[[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]] 408 408 409 409 downstream simulation 410 410 411 411 372 +\\ 373 + 412 412 == 4.5 Add LoRa support to communicate with remote sensor == 413 413 414 414 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. ... ... @@ -427,7 +427,7 @@ 427 427 * Downstream: Listening broadcast message from gateway, and print it in console. 428 428 * The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below: 429 429 430 -[[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]] 431 431 432 432 LoRa Parameter should match 433 433 ... ... @@ -434,11 +434,11 @@ 434 434 435 435 Below is the test result after the Arduino Sketch is running. 436 436 437 -[[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]] 438 438 439 439 Upstream Data Flow 440 440 441 -[[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]] 442 442 443 443 Downstream Data Flow 444 444 ... ... @@ -450,8 +450,7 @@ 450 450 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. 451 451 452 452 453 - 454 -Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 415 +\\Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 455 455 456 456 457 457 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. ... ... @@ -458,7 +458,7 @@ 458 458 459 459 Step 2: Make sure your Radio settings match the End Node settings. 460 460 461 -[[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png||height="387" width="600"]] 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]] 462 462 463 463 Use Same Frequency Band as End Node 464 464 ... ... @@ -465,7 +465,7 @@ 465 465 466 466 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 467 467 468 -[[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]] 469 469 470 470 Publish mush use META as data format for LG308 471 471 ... ... @@ -472,7 +472,7 @@ 472 472 473 473 Step 4: Map the Device Address to Remote ID in MQTT server. 474 474 475 -[[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]] 476 476 477 477 Map Dev Addr to remote ID 478 478 ... ... @@ -479,21 +479,21 @@ 479 479 480 480 Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server 481 481 482 -[[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]] 483 483 484 484 Upstream Process 485 485 486 -[[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]] 487 487 488 488 Choose ASCII Format 489 489 490 -[[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]] 491 491 492 492 LHT65 Decoder 493 493 494 494 Step 6: Set up subscribe: Subscribe a topci for downstream. 495 495 496 -[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]] 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]] 497 497 498 498 Subscribe to a topic 499 499 ... ... @@ -500,7 +500,7 @@ 500 500 501 501 Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 502 502 503 -[[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]] 504 504 505 505 Downstream Flow 506 506 ... ... @@ -509,36 +509,33 @@ 509 509 510 510 = 5. Example For Different MQTT Servers = 511 511 512 -(% style="width:731.222px" %) 513 -|=(% style="width: 270px;" %)((( 514 -[[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]] 515 515 516 -== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] == 476 +=== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] === 517 517 518 518 519 519 [[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]] 520 -)))|=( % style="width: 242px;" %)(((521 -[[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]] 522 522 523 -(% class="wikigeneratedid" %) 524 -== == 483 +=== [[乐联网平台>>url:https://www.lewei50.com/]] === 525 525 526 -== [[乐联网平台>>url:https://www.lewei50.com/]] == 527 527 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]] 528 528 529 -[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]] 530 -)))|=(% style="width: 214px;" %)((( 531 -[[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/]] === 532 532 533 -== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] == 534 534 535 - 536 536 [[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]] 537 537 ))) 538 538 496 + 539 539 = 6. How to Debug = 540 540 541 -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. 542 542 543 543 = 7. How to ask for Support = 544 544