Changes for page General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Last modified by Mengting Qiu on 2025/07/17 10:51

From 53.3 to 53.2 From 83.2 to 83.1

From version 83.1

edited by Edwin Chen
on 2023/08/08 20:51

Change comment: There is no comment for this version

To version 53.3

edited by Xiaoling
on 2023/08/02 11:42

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 15 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Edwin
++XWiki.Xiaoling

Content

@@ -1,8 +1,10 @@
--== **Table of Contents:** ==
++(% class="wikigeneratedid" %)
++**Table of Contents:**
  {{toc/}}
++
  = 1. The use of this guideline =
@@ -9,30 +9,21 @@
  This configure instruction is for Dragino NB-IoT models with -NB or -NS suffix, for example DDS75-NB. These models use the same NB-IoT Module **[[BC660K-GL>>https://www.quectel.com/product/lpwa-bc660k-gl-nb2]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.
--= 2. Attach Network =
++= 2. Network Connection =
--To attache NB-IoT sensors to NB-IoT Network, You need to:
++The -NB and -NS models support (% style="color:blue" %)**LTE Cat NB2**(%%), with below frequency band: multiple frequency bands of (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85**(%%) . Make sure you use a the NB-IoT SIM card.
--1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
--1. Insert the SIM card to Sensor
--1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (% class="mark" %)(补充 APN 指令(%%))
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|(% style="background-color:#4f81bd; color:white" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white" %)**APN**|(% style="background-color:#4f81bd; color:white" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white" %)**Comments**
++|1NCE| | |
++|China Mobile| | |
--[[image:image-20230808205045-1.png||height="293" width="438"]]
--After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
--The -NB and -NS models support (% style="color:blue" %)**LTE Cat NB2**(%%), with below frequency band: multiple frequency bands of (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85**(%%) . Make sure you use a the NB-IoT SIM card.
++== 2.1 1NCE SIM Card. ==
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
--|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**APN**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
--|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
--**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
--Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
--)))|(% style="width:135px" %)
--|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
--|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
  = 3. Configure to connect to different servers =
@@ -55,14 +55,12 @@
  ==== 3.1.2.1 AT Commands ====
--(% style="color:blue" %)**AT Commands:**
++**AT Commands:**
--* (% style="color:#037691" %)**AT+PRO=2,0**  (%%)       ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
++* AT+PRO=2,0         ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
++* AT+SERVADDR=120.24.4.116,5601      ~/~/  Set UDP server address and port
++* AT+CFM=1          ~/~/  If the server does not respond, this command is unnecessary
--* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%)    ~/~/  Set UDP server address and port
--
--* (% style="color:#037691" %)**AT+CFM=1**    (%%)      ~/~/  If the server does not respond, this command is unnecessary
--
  [[image:image-20230802112413-2.png]]
@@ -72,40 +72,33 @@
  [[image:image-20230802112413-3.png]]
--== 3.2 General MQTT Connection ==
++= 2. General MQTT Connection =
--
  The NB-IoT Sensor can send packet to server use MQTT protocol.
--Below are the commands.
++Below are the commands
--(% style="color:blue" %)**AT Commands:**
++AT Commands:
--* (% style="color:#037691" %)**AT+PRO=3,0**   (%%)   ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
++* AT+PRO=3,0  ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
++* AT+SERVADDR=120.24.4.116,1883        ~/~/  Set MQTT server address and port
++* AT+CLIENT=CLIENT                         ~/~/  Set up the CLIENT of MQTT
++* AT+UNAME=UNAME                      ~/~/  Set the username of MQTT
++* AT+PWD=PWD                          ~/~/  Set the password of MQTT
++* AT+PUBTOPIC=NSE01_PUB               ~/~/  Set the sending topic of MQTT
++* AT+SUBTOPIC=NSE01_SUB                  ~/~/  Set the subscription topic of MQTT
--* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%)      ~/~/  Set MQTT server address and port
--
--* (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%)                            ~/~/  Set up the CLIENT of MQTT
--
--* (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%)                      ~/~/  Set the username of MQTT
--
--* (% style="color:#037691" %)**AT+PWD=PWD**             (%%)                           ~/~/  Set the password of MQTT
--
--* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%)                  ~/~/  Set the sending topic of MQTT
--
--* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%)                  ~/~/  Set the subscription topic of MQTT
--
  [[image:image-20230802112413-4.png]]
  [[image:image-20230802112413-5.png]]
--(% style="color:red" %)**Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink  period to a suitable interval.**
++Notice: MQTT  protocol has a much higher power consumption compare with UDP / CoAP  protocol. Please check the power analyze document and adjust the uplink  period to a suitable interval.
--== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
--=== 3.3.1 Get MQTT Credentials ===
++= 3. [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) =
++== 1.1 Get MQTT Credentials ==
  [[ThingSpeak>>url:https://thingspeak.com/]] connection uses MQTT Connection. So we need to get MQTT Credentials first. You need to point MQTT Devices to ThingSpeak Channel as well.
@@ -114,69 +114,55 @@
  [[image:image-20230802112413-7.png]]
--=== 3.3.2 Simulate with MQTT.fx ===
++== 1.2. Simulate with MQTT.fx ==
--==== 3.3.2.1 Establish MQTT Connection ====
++=== 1.2.1 Establish MQTT Connection ===
--
  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
  [[image:image-20230802112413-8.png]]
--* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
++* Broker Address: mqtt3.thingspeak.com
++* Broker Port: 1883
++* Client ID: <Your ThingSpeak MQTT ClientID>
++* User Name: <Your ThingSpeak MQTT User Name>
++* Password: <Your ThingSpeak MQTT Password>
--* (% style="color:#037691" %)**Broker Port:**(%%) 1883
++=== 1.2.2 Publish Data to ThingSpeak Channel ===
--* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
--
--* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
--
--* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
--
--==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
--
--
  [[image:image-20230802112413-9.png]]
  [[image:image-20230802112413-10.png]]
++In MQTT.fx, we can publish below info:
--(% style="color:blue" %)**In MQTT.fx, we can publish below info:**
++* Topic: channels/YOUR_CHANNEL_ID/publish
++* Payload: field1=63&field2=67&status=MQTTPUBLISH
--* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
--
--* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
--
  Where 63 and 67 are the value to be published to field1 & field2.
--(% style="color:blue" %)**Result: **
++Result:
  [[image:image-20230802112413-11.png]]
--=== 3.3.3 Configure NB-IoT Sensor for connection ===
++== 1.3 Configure NB-IoT Sensor for connection ==
--==== 3.3.3.1 AT Commands: ====
++=== 1.3.1 AT Commands: ===
--
  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
--* (% style="color:blue" %)**AT+PRO=3,1** (%%)    ~/~/ Set to use ThingSpeak Server and Related Payload
++* AT+PRO=3,1   ~/~/Set to use ThingSpeak Server and Related Payload
++* AT+CLIENT=<Your ThingSpeak MQTT ClientID>
++* AT+UNAME=<Your ThingSpeak MQTT User Name>
++* AT+PWD=<Your ThingSpeak MQTT Password>
++* AT+PUBTOPIC=<YOUR_CHANNEL_ID>
++* AT+SUBTOPIC=<YOUR_CHANNEL_ID>
--* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
--* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
++=== 1.3.2 Uplink Examples ===
--* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
--
--* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
--
--* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
--
--==== 3.3.3.2 Uplink Examples ====
--
--
  For S31-NB
  For SE01-NB
@@ -202,9 +202,8 @@
  For SN50V3-NB
--==== 3.3.3.3 Map fields to sensor value ====
++=== 1.3.2 Map fields to sensor value ===
--
  When NB-IoT sensor upload to ThingSpeak. The payload already specify which fileds related to which sensor value. Use need to create fileds in Channels Settings. with name so to see the value correctly.
@@ -215,267 +215,388 @@
  Below is the NB-IoT Product Table show the mapping.
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1386px" %)
--|(% style="background-color:#4f81bd; width:124px" %) |(% style="background-color:#4f81bd; color:white; width:91px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:159px" %)Field3|(% style="background-color:#4f81bd; color:white; width:153px" %)Field4|(% style="background-color:#4f81bd; color:white; width:152px" %)Field5|(% style="background-color:#4f81bd; color:white; width:148px" %)Field6|(% style="background-color:#4f81bd; color:white; width:164px" %)Field7|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|(% style="background-color:#4f81bd; color:white; width:66px" %)Field9|(% style="background-color:#4f81bd; color:white; width:66px" %)Field10
--|(% style="background-color:#4f81bd; color:white; width:124px" %)S31x-NB|(% style="width:91px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
--|(% style="background-color:#4f81bd; color:white; width:124px" %)SE01-NB|(% style="width:91px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:159px" %)conduct|(% style="width:153px" %)dielectric_constant|(% style="width:152px" %)Battery|(% style="width:148px" %)RSSI|(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
--|(% style="background-color:#4f81bd; color:white; width:124px" %)DDS20-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
--|(% style="background-color:#4f81bd; color:white; width:124px" %)DDS45-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
--|(% style="background-color:#4f81bd; color:white; width:124px" %)DDS75-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
--|(% style="background-color:#4f81bd; color:white; width:124px" %)NMDS120-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
--|(% rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SPH01-NB|(% style="width:91px" %)ph|(% style="width:102px" %)Temperature|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %)
--|(% style="background-color:#4f81bd; color:white; width:124px" %)NLM01-NB|(% style="width:91px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
--|(% style="background-color:#4f81bd; color:white; width:124px" %)NMDS200-NB|(% style="width:91px" %)distance1|(% style="width:102px" %)distance2|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
--|(% style="background-color:#4f81bd; color:white; width:124px" %)CPN01-NB|(% style="width:91px" %)alarm|(% style="width:102px" %)count|(% style="width:159px" %)door open duration|(% style="width:153px" %)calc flag|(% style="width:152px" %)Battery|(% style="width:148px" %)RSSI|(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
--|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:91px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:159px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:153px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:152px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:148px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:164px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:66px" %)Battery|(% colspan="1" rowspan="1" style="width:66px" %)RSSI
--|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:91px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:159px" %)RSSI|(% colspan="1" rowspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:148px" %)adc0|(% colspan="1" rowspan="1" style="width:164px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %)
--|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod2|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc0|(% colspan="1" style="width:164px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
--|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod3|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc1|(% colspan="1" style="width:164px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:66px" %)adc4|(% colspan="1" style="width:66px" %)
--|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod4|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)adc0|(% colspan="1" style="width:148px" %)exit_state/input PA4|(% colspan="1" style="width:164px" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
--|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod5|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)adc0|(% colspan="1" style="width:148px" %)exit_state/input PA4|(% colspan="1" style="width:164px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
--|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod6|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)count|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:148px" %) |(% colspan="1" style="width:164px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
++|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)Field1|(% colspan="1" rowspan="1" %)Field2|(% colspan="1" rowspan="1" %)Field3|(% colspan="1" rowspan="1" %)Field4|(% colspan="1" rowspan="1" %)Field5|(% colspan="1" rowspan="1" %)Field6|(% colspan="1" rowspan="1" %)Field7|(% colspan="1" rowspan="1" %)Field8|(% colspan="1" rowspan="1" %)(((
++Field9
--== 3.4 Datacake ==
++
++)))|(% colspan="1" rowspan="1" %)(((
++Field10
--=== 3.4.1 Create device ===
++
++)))
++|(% colspan="1" rowspan="1" %)S31x-NB|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)SE01-NB|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)conduct|(% colspan="1" rowspan="1" %)dielectric_constant|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)DDS20-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
++Battery
--[[image:image-20230808162301-1.png]]
++
++)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)DDS45-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
++Battery
++
++)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)DDS75-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
++Battery
--[[image:image-20230808162342-2.png]]
++
++)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)NMDS120-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
++Battery
++
++)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)SPH01-NB|(% colspan="1" rowspan="1" %)ph|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)NLM01-NB|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)NMDS200-NB|(% colspan="1" rowspan="1" %)distance1|(% colspan="1" rowspan="1" %)distance2|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)CPN01-NB|(% colspan="1" rowspan="1" %)alarm|(% colspan="1" rowspan="1" %)count|(% colspan="1" rowspan="1" %)door open duration|(% colspan="1" rowspan="1" %)calc flag|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)DS03A-NB|(% colspan="1" rowspan="1" %)level|(% colspan="1" rowspan="1" %)alarm|(% colspan="1" rowspan="1" %)pb14door open num|(% colspan="1" rowspan="1" %)pb14 last open time|(% colspan="1" rowspan="1" %)pb15 level status|(% colspan="1" rowspan="1" %)pb15 alarm status|(% colspan="1" rowspan="1" %)pb15 door open num|(% colspan="1" rowspan="1" %)pb15 last open time|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI
++|(% colspan="1" rowspan="1" %)SN50V3-NB|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)mod1|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)DS18B20 Temp|(% colspan="1" rowspan="1" %)exit_state/input PA4|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)mod2|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
++DS18B20 Temp
--[[image:image-20230808162421-3.png]]
++
++)))|(% colspan="1" rowspan="1" %)(((
++exit_state/input PA4
--The device ID needs to be filled in with IMEI, and a prefix of 'f' needs to be added.
++
++)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)mod3|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
++Battery
--[[image:image-20230808163612-7.png]]
++
++)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
++exit_state/input PA4
--[[image:image-20230808163035-5.png]]
++
++)))|(% colspan="1" rowspan="1" %)adc1|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)adc4|(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)mod4|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
++Battery
--[[image:image-20230808163049-6.png]]
++
++)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
++DS18B20 Temp
--=== 3.4.2 Scan QR code to obtain data ===
++
++)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
++exit_state/input PA4
--Users can use their phones or computers to scan QR codes to obtain device data information.
++
++)))|(% colspan="1" rowspan="1" %)(((
++DS18B20 Temp2
--[[image:image-20230808170051-8.png]]
++
++)))|(% colspan="1" rowspan="1" %)(((
++DS18B20 Temp3
--[[image:image-20230808170548-9.png]]
++
++)))|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)mod5|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
++Battery
--=== 3.4.2 AT command for connecting to DataCake ===
++
++)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
++DS18B20 Temp
--**AT+PRO=2,0**
++
++)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
++exit_state/input PA4
--**AT+SERVADDR=67.207.76.90,4445**
++
++)))|(% colspan="1" rowspan="1" %)Weight|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
++|(% colspan="1" rowspan="1" %)mod6|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
++Battery
++
++)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)count|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
--== 3.5 Node-Red (via MQTT) ==
++= 4. Datacake =
--=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
++== 1.1 Define Product ==
++Firstly, we need to set the MQTT mode to datacake, and we need to run AT+PRO=3,2. This command is set to datacake. After running the command, the device automatically sets the server address, port.
--[[image:image-20230802112413-29.png]]
++By chosing to add the device under a "New Product" you are required to give a name for this product. You can name it something like "My First MQTT Product".
--[[image:image-20230802112413-30.png]]
++[[image:image-20230802112413-14.png]]
++== 1.2 Create Device ==
--=== 3.5.2 Simulate Connection ===
++In the second step you have to define the device which should be added to the product.
++[[image:image-20230802112413-15.png]]
--[[image:image-20230802112413-31.png]]
++Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the "Next" button.
--=== 3.5.3 Configure NB-IoT Sensors ===
++== 1.3 Create Database Fields ==
++After creating the device, it is listed in the table of the fleet view. Now open the device by clicking on the entry in the list.
--* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%)    ~/~/  Set to mqtt Server and  Payload
++You will then see a device view with an empty dashboard. Now, the first thing we want to do is navigate to the Device configuration. To do this, use the tab bar and click on "Configuration".
--* (% style="color:blue" %)**AT+CLIENT=any value**
++[[image:image-20230802112413-16.png]]
--* (% style="color:blue" %)**AT+UNAME=any value**
++[[image:image-20230802112413-17.png]]
--* (% style="color:blue" %)**AT+PWD=any value**
++To create a first database field, please click on the "Add Field" button as marked in the screenshot above.
--* (% style="color:blue" %)**AT+PUBTOPIC=any value**
++This will open another modal asking for some required input for your first field.
--* (% style="color:blue" %)**AT+SUBTOPIC=any value**
++[[image:image-20230802112413-18.png]]
--== 3.6 ThingsBoard.Cloud (via MQTT) ==
++[[image:image-20230802112413-19.png]]
--=== 3.6.1 Configure ThingsBoard ===
++== 1.4 Set up Broker ==
--==== 3.6.1.1 Create Device ====
++The broker is running on mqtt.datacake.co on ports 1883 and 8883. Port 1883 is unsecured and should not be used in production environments. Port 8883 uses a CA signed server certificate.
++You will need an access token to log into the Datacake MQTT Broker. You can use your own personal token or create a token explicitly for individual devices or groups of devices.
--Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
++View your Personal Access Token
--[[image:image-20230802112413-32.png]]
++You can view your own token via the User-Settings-Menu. You can reach this menu by clicking on "Edit Profile" at the end of the list using the Workspace Selector:
++[[image:image-20230802112413-20.png]]
--==== 3.6.1.2 Create Uplink & Downlink Converter ====
++MQTT Client-ID
++The Datacake Broker manages the client IDs internally. You do not need to worry about a client ID. If your client optionally supports the specification of a client ID, please leave this specification blank. Your client then creates a randomly generated ID.
--(% style="color:blue" %)**Uplink Converter**
++AT+CLIENT=“Any value”
--The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
++AT+UNAME=Token
--To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
++AT+PWD=Token
--[[image:image-20230802112413-33.png||height="732" width="1302"]]
++[[image:image-20230802112413-21.png]]
--(% style="color:blue" %)**Downlink Converter**
++== 1.6 Create your first Subscription ==
--The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
++Subscribe
--[[image:image-20230802112413-34.png||height="734" width="1305"]]
++Data is published according to the following structure:
--(% style="color:red" %)**Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
++dtck~/~//
++Subscribe to topics using this structure to receive messages via MQTT when readings (via API or MQTT) arrive in the Datacake Cloud. Messages are published whenever there is a change to a corresponding database field.
--==== 3.6.1.3 MQTT Integration Setup ====
++[[image:image-20230802112413-22.png]]
--Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**;
--[[image:image-20230802112413-35.png||height="738" width="1312"]]
++[[image:image-20230802112413-23.png]]
--* The next steps is to add the recently created uplink and downlink converters;
++[[image:image-20230802112413-24.png]]
--[[image:image-20230802112413-36.png||height="736" width="1308"]]
--[[image:image-20230802112413-37.png||height="735" width="1307"]]
++example:
++AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
--(% style="color:blue" %)**Add a topic filter:**
++[[image:image-20230802112413-25.png]]
--tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
++== 1.7 Define Publish Topic ==
--You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
++Publish
--[[image:image-20230802112413-38.png||height="731" width="1300"]]
++To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure.
++Due to the nature of MQTT, the topic prefix differs as follows:
--=== 3.6.2 Simulate with MQTT.fx ===
++dtck-pub~/~//
++example:
--[[image:image-20230802112413-39.png]]
++AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
--[[image:image-20230802112413-40.png]]
++== 1.8 upload data ==
++[[image:image-20230802112413-26.png]]
--=== 3.6.3 Configure NB-IoT Sensor ===
++[[image:image-20230802112413-27.png]]
++[[image:image-20230802112413-28.png]]
--(% style="color:blue" %)**AT Commands**
++=   =
--* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)**  **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
++= 5. Node-Red (via MQTT) =
--* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>** (%%)
--* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
--* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
--* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
--* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
--Test Uplink by click the button for 1 second
++== 1.1 Configure Node-Red ==
--[[image:image-20230802112413-41.png]]
++[[image:image-20230802112413-29.png]]
--[[image:image-20230802112413-42.png]]
++[[image:image-20230802112413-30.png]]
--[[image:image-20230802112413-43.png]]
++== 1.2 Simulate Connection ==
++[[image:image-20230802112413-31.png]]
--== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
++== 1.3 Configure NB-IoT Sensors ==
--=== 3.7.1 Create device & Get Credentials ===
++* AT+PRO=3,0(hex format) or 3,5(json format)    ~/~/Set to mqtt Server and  Payload
++* AT+CLIENT=any value
++* AT+UNAME=any value
++* AT+PWD=any value
++* AT+PUBTOPIC=any value
++* AT+SUBTOPIC=any value
++= 6. ThingsBoard.Cloud (via MQTT) =
--We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
++== 1.1 Configure ThingsBoard ==
--[[image:image-20230802112413-44.png]]
++=== 1.1.1 Create Device ===
--[[image:image-20230802112413-45.png]]
++Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
++[[image:image-20230802112413-32.png]]
--Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
++=== 1.1.2 Create Uplink & Downlink Converter ===
--[[image:image-20230802112413-46.png]]
++Uplink Converter
++The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
--The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
++To create an uplink converter go to the Integrations center -> Data converters page and click “plus” button. Name it “MQTT Uplink Converter” and select type Uplink. Use debug mode for now.
--On the Connection Profile window, set the following information:
++[[image:image-20230802112413-33.png]]
--* (% style="color:blue" %)**Profile Name: “Any name”**
--* (% style="color:blue" %)**Broker Address: mqtt.tago.io**
++Downlink Converter
--* (% style="color:blue" %)**Broker Port: 8883**
++The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
--* (% style="color:blue" %)**Client ID: “Any value”**
++[[image:image-20230802112413-34.png]]
--On the section User credentials, set the following information:
++Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.
--* (% style="color:blue" %)**User Name: “Any value”** (%%)      ~/~/ Tago validates your user by the token only
++=== 1.1.3 MQTT Integration Setup ===
--* (% style="color:blue" %)**Password: “Your device token”**
++Go to the Integrations center -> Integrations page and click “plus” icon to add a new integration. Name it “MQTT Integration”, select type MQTT;
--* (% style="color:blue" %)**PUBTOPIC: “Any value”**
++[[image:image-20230802112413-35.png]]
--* (% style="color:blue" %)**SUBTOPIC: “Any value”**
++* The next steps is to add the recently created uplink and downlink converters;
--(% style="color:blue" %)**AT command:**
++[[image:image-20230802112413-36.png]]
--* **AT+PRO=3,0 or 3,5   **~/~/ hex format or json format
++[[image:image-20230802112413-37.png]]
--* **AT+SUBTOPIC=<device name>** **or User Defined**
--* **AT+PUBTOPIC=<device name>or User Defined**
--* **AT+CLIENT=<device name> or User Defined**
--* **AT+UNAME=<device name> or User Defined**
--* **AT+PWD=“Your device token”**
++Add a topic filter:
--=== 3.7.2 Simulate with MQTT.fx ===
--[[image:image-20230802112413-52.png]]
++tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
++You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
--[[image:image-20230808105300-2.png]]
++[[image:image-20230802112413-38.png]]
--Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
++== 1.2 Simulate with MQTT.fx ==
--[[image:image-20230808105217-1.png]]
++[[image:image-20230802112413-39.png]]
--[[image:image-20230808105329-3.png]]
++[[image:image-20230802112413-40.png]]
++== 1.3 Configure NB-IoT Sensor ==
--=== 3.7.3 tago data ===
++AT Commands
++AT+PRO=3,3  ~/~/ Use MQTT to connect to ThingsBoard.
--[[image:image-20230802112413-50.png]]
++AT+SUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
--[[image:image-20230802112413-51.png||height="184" width="696"]]
++AT+PUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
++Users do not need to fill in the client, username, and password. But the configuration information of the device requires setting the client, username, and password, which can be entered freely. (软件自动填充为 Device Name 吧).这边不用提示了，客户不需要输入。（大部分客户还是会自己去设置这个的，提高安全性）
--== 3.8 TCP Connection ==
++CLIENT :“Any value”
++User Name:“Any value”
--* **AT+PRO=4,0   ** ~/~/ Set to use TCP protocol to uplink(HEX format)
--* **AT+PRO=4,1   ** ~/~/ Set to use TCP protocol to uplink(JSON format)
--* **AT+SERVADDR=120.24.4.116,5600   **~/~/ to set TCP server address and port
++Password:“Any value”
--**Sensor Console Output when Uplink**
--[[image:image-20230807233631-1.png]]
++Test Uplink by click the button for 1 second
++[[image:image-20230802112413-41.png]]
--**See result in TCP Server**
++[[image:image-20230802112413-42.png]]
--[[image:image-20230807233631-2.png]]
++[[image:image-20230802112413-43.png]]
++= 7. [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) =
++
++== 5.1 Create device & Get Credentials ==
++
++We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
++
++[[image:image-20230802112413-44.png]]
++
++[[image:image-20230802112413-45.png]]
++
++=   =
++
++Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
++
++[[image:image-20230802112413-46.png]]
++
++
++On the Connection Profile window, set the following information: (这边加一个截图)
++
++* Profile Name: “Any name”
++* Broker Address: mqtt.tago.io
++* Broker Port: 1883
++* Client ID: “Any value”
++
++On the section User credentials, set the following information:(这边加一个截图)
++
++* User Name: “Any value” Tago validates your user by the token only
++* Password: “Your device token”
++* PUBTOPIC: “Any value”
++* SUBTOPIC: “Any value”
++
++== 5.2 Simulate with MQTT.fx ==
++
++[[image:image-20230802112413-47.png]]
++
++[[image:image-20230802112413-48.png]]
++
++Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format.
++
++[[image:image-20230802112413-49.png]]
++
++== 1.4. tago data ==
++
++
++[[image:image-20230802112413-50.png]]
++
++[[image:image-20230802112413-51.png]]
++
++== 1.4. TLS mode ==
++
++Users can choose to use SSL/TLS mode.
++
++On the SSL/TLS section, check the option Enable SSL/TLS, and click OK.
++
++The device needs to enable the TLS mode and set the AT+TLSMOD=1,0 command.
++
++* Profile Name: “Any name”
++* Broker Address: mqtt.tago.io
++* Broker Port: 8883
++* Client ID: “Any value”
++* User Name: “Any value” Tago validates your user by the token only
++* Password: “Your device token”
++* PUBTOPIC: “Any value”
++* SUBTOPIC: “Any value”
++
++[[image:image-20230802112413-52.png]]
++
++

image-20230807233631-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Edwin

Size

...	...	@@ -1,1 +1,0 @@
1		-21.9 KB

Content

image-20230807233631-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Edwin

Size

...	...	@@ -1,1 +1,0 @@
1		-9.6 KB

Content

image-20230808105217-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-68.5 KB

Content

image-20230808105300-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-70.1 KB

Content

image-20230808105329-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-21.1 KB

Content

image-20230808162301-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-76.9 KB

Content

image-20230808162342-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-63.8 KB

Content

image-20230808162421-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-59.2 KB

Content

image-20230808162727-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-54.2 KB

Content

image-20230808163035-5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-71.6 KB

Content

image-20230808163049-6.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-61.5 KB

Content

image-20230808163612-7.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-53.4 KB

Content

image-20230808170051-8.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-21.5 KB

Content

image-20230808170548-9.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.David

Size

...	...	@@ -1,1 +1,0 @@
1		-54.1 KB

Content

image-20230808205045-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Edwin

Size

...	...	@@ -1,1 +1,0 @@
1		-373.9 KB

Content

Changes for page General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Summary

Details

Applications

Navigation