Changes for page 01 Lua Functions

Last modified by Theodore Xu on 2023/10/26 10:51

From 5.9 to 5.8 From 5.11 to 5.10

From version 5.10

edited by Stone Wu
on 2022/07/12 09:30

Change comment: (Autosaved)

To version 5.9

edited by Stone Wu
on 2022/07/12 09:26

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -752,10 +752,12 @@
  **QoS value:**
--* 0: Only push messages once, messages may be lost or duplicated. It can be used for environmental sensor data, it doesn't matter if lose a record, because there will be a second push message soon. This method is mainly used for normal APP push, but if the user smart device is not connected when the message is pushed, the message will be discarded, and the smart device will not be received when it is networked again.
--* 1: The message is delivered at least once, but the message may be delivered repeatedly.
--* 2: The message was delivered exactly once. This level can be used in a billing system. In a billing system, repeated or missing messages can lead to incorrect results. This highest quality message push service can also be used for instant messaging APP pushes, ensuring that users only receive messages once.
++0: Only push messages once, messages may be lost or duplicated. It can be used for environmental sensor data, it doesn't matter if lose a record, because there will be a second push message soon. This method is mainly used for normal APP push, but if the user smart device is not connected when the message is pushed, the message will be discarded, and the smart device will not be received when it is networked again.
++1: The message is delivered at least once, but the message may be delivered repeatedly.
++
++2: The message was delivered exactly once. This level can be used in a billing system. In a billing system, repeated or missing messages can lead to incorrect results. This highest quality message push service can also be used for instant messaging APP pushes, ensuring that users only receive messages once.
++
  **Retain flag:**
 : not reserved;
@@ -763,11 +763,13 @@
 : reserved
  (((
--== **mqtt.create(string serverurl, string clientid)** ==
++== **4.1 mqtt.create(string serverurl, string clientid)** ==
  )))
--**Function:** Create an MQTT object
++**Function:**
++Create an MQTT object
++
  **Parameters:**
  //serverurl //Server url
@@ -789,13 +789,17 @@
  Failed: multi
  (((
--== **mqtt.close(mqtt obj)** ==
++== **4.2 mqtt.close(mqtt obj)** ==
  )))
--**Function:** Close the specified MQTT object (if the connected server will be disconnected automatically)
++**Function:**
--**Parameters: **//Obj //is the objeced returned by mqtt.create
++Close the specified MQTT object (if the connected server will be disconnected automatically)
++**Parameters:**
++
++//Obj //is the objeced returned by mqtt.create
++
  **Return：**
  Succeed: true
@@ -803,25 +803,32 @@
  Failed: multi
  (((
--== **mqtt:connect(table conn[, table lwt, table cart])** ==
++== **4.3 mqtt:connect(table conn[, table lwt, table cart])** ==
  )))
--**Function:**Establish a connection to the server
++**Function:**
++Establish a connection to the server
++
  **Parameters:**
  //conn //is a Lua table and needs to contain the following fields
--* //string conn.username//, user name
--* //string conn.password//, password
--* //number [conn.netway=0]//, networking method, if set error number will use Ethernet method
--** 0: Ethernet
--** 1: WIFI
--** 2: 4G
--** 3: 2G
--* //number [conn.keepalive=60]//, keep connected heartbeat interval, in seconds
--* //number [conn.cleansession=1]//, empty the session as described below:
++//string conn.username//, user name
++//string conn.password//, password
++
++//number [conn.netway=0]//, networking method, if set error number will use Ethernet method
++
++* 0: Ethernet
++* 1: WIFI
++* 2: 4G
++* 3: 2G
++
++//number [conn.keepalive=60]//, keep connected heartbeat interval, in seconds
++
++//number [conn.cleansession=1]//, empty the session as described below:
++
  This function is used to control the behavior when connecting and disconnecting, and the client and server will retain the session information. This information is used to guarantee "at least once" and "accurately once" delivery, as well as the subject of the client subscription, the user can choose to keep or ignore the session message, set as follows:
  * 1 (Empty): If a session exists and is 1, the previous session messages on the client and server are emptied.
@@ -829,11 +829,14 @@
  //lwt// (Last Will and Testament) is a Lua table and needs to contain the following fields
--* //string lwt.topic//, topic
--* //string lwt.message//, message
--* //number [lwt.qos=0]//, qos value
--* //number [lwt.retain=0]//, retain flag
++//string lwt.topic//, topic
++//string lwt.message//, message
++
++//number [lwt.qos=0]//, qos value
++
++//number [lwt.retain=0]//, retain flag
++
  **Return：**
  Succeed: true
@@ -841,13 +841,17 @@
  Failed: multi
  (((
--== **mqtt:disconnect([number timeout])** ==
++== **4.4 mqtt:disconnect([number timeout])** ==
  )))
--**Function:** Disconnect from the MQTT server
++**Function:**
--**Parameters: **//[timeout=10000] //Disconnect waiting timeout, in milliseconds
++Disconnect from the MQTT server
++**Parameters:**
++
++//[timeout=10000] //Disconnect waiting timeout, in milliseconds
++
  **Return：**
  Succeed: true
@@ -855,13 +855,17 @@
  Failed: multi
  (((
--== **mqtt:isconnected()** ==
++== **4.5 mqtt:isconnected()** ==
  )))
--**Function:** Test whether or not a client is currently connected to the MQTT server
++**Function:**
--**Parameters:** None
++Test whether or not a client is currently connected to the MQTT server
++**Parameters:**
++
++None
++
  **Return：**
  Succeed: true ~-~-Connected
@@ -869,11 +869,13 @@
  Failed: false ~-~- Unconnected and other unknowns
  (((
--== **mqtt:subscribe(string topic, number qos)** ==
++== **4.6 mqtt:subscribe(string topic, number qos)** ==
  )))
--**Function: **Subscribe to the topic (before the subscription, the user must first call the connect method to connect to the server)
++**Function:**
++Subscribe to the topic (before the subscription, the user must first call the connect method to connect to the server)
++
  **Parameters:**
  //topic//, topic name
@@ -887,11 +887,13 @@
  Failed: multi
  (((
--== **mqtt:unsubscribe(string topic)** ==
++== **4.7 mqtt:unsubscribe(string topic)** ==
  )))
--**Function:** Unsubscribe topic
++**Function:**
++Unsubscribe topic
++
  **Parameters:**
  //topic//, topic name
@@ -903,11 +903,13 @@
  Failed: multi
  (((
--== **mqtt:publish(string topic, string message, number qos, number retain[, number timeout])** ==
++== **4.8 mqtt:publish(string topic, string message, number qos, number retain[, number timeout])** ==
  )))
--**Function:** Publish message
++**Function:**
++Publish message
++
  **Parameters:**
  //topic//, topic name
@@ -927,13 +927,17 @@
  Failed: multi
  (((
--== **mqtt:close()** ==
++== **4.9 mqtt:close()** ==
  )))
--**Function:** Close the mqtt object (the connection to the server will be automatically disconnected)
++**Function:**
--**Parameters:** None
++Close the mqtt object (the connection to the server will be automatically disconnected)
++**Parameters:**
++
++None
++
  **Return：**
  Succeed: true
@@ -941,11 +941,13 @@
  Failed: multi
  (((
--== **mqtt:on(string method, function callback)** ==
++== **4.10 mqtt:on(string method, function callback)** ==
  )))
--**Function:** Register event callback function
++**Function:**
++Register event callback function
++
  **Parameters:**
  //method//, It can be message/arrived/offline, these 3 types of events

Changes for page 01 Lua Functions

Summary

Details

Navigation

Table of Contents