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