MQTT Data Push Service

Describe

1.The MQTT push service provided by Jointech is a service that sends device data to data users in real time. When the device uploads data, the push service will sense it immediately, organize and package the data, and send it to the MQTT server. The customer data receiving service obtains data from the MQTT server, and then the customer processes the data according to his own business.
2.The MQTT rule configuration interface is mainly used to facilitate users to configure which devices to use for MQTT push services
3.Subscription topic description

MQTT Rule Configuration

In this interface, users can configure the devices that need to be pushed by MQTT. By selecting the data source, users can select the devices that need to be pushed in multiple ways.

Data source description

1.All devices of the company

Indicates all devices under the current company and its subsidiaries

2.Company-owned devices

Indicates the current company and all the devices under it

3.Company specified devices

Indicates the designated devices under the current company and its subsidiaries

Subscription topic and payload description

Replace {accessKey} with the actual value assigned by the system and {deviceNum} with the ID of the device

1.Server address and description

2.Client account and password

The login account and password (after MD5 encryption) configured for the current MQTT rule can also be viewed directly in the details interface of the rule.

3.Subscription topic Description

3.1 Device status reporting

Topic：upload/{accessKey}/{deviceNum}/location
Description：devices positioning status data
e.g.：

{"assetId":"8052400203","battery":255,"cellSignal":31,"cells":"460,0,10352,188975300","direction":0,"expandInfo":"{\"angle\":\"null\",\"backBattery\":\"null\",\"fuels\":\"-1,-1,-1\",\"humidity\":\"0\",\"lux\":\"null\",\"networkType\":\"0\",\"pressure\":\"null\",\"reportType\":\"null\",\"temperature\":\"-1000.0\"}","gnssSignal":0,"gpsTime":"2025-02-07T07:26:30Z","latitude":22.6700711039462,"locType":2,"longitude":113.922999834147,"mileage":0,"recvTime":"2025-02-07T07:25:20.832Z","speed":0,"statusJson":"{\"lockRope\":0,\"lockStatus\":0}","voltage":"0.0"}

Json Field Description

Lock Status JSON Description

Vehicle status JSON description

JSON description of extension information

3.2 Device alarm reporting

Topic：upload/{accessKey}/{deviceNum}/alarm
Description：device alarm data, such as low battery, lock rope cut alarm
e.g.：

{"alarmType":44,"assetId":"8454601010","cells":"460,0,9383,149428936","dateTime":"2020-04-01T00:00:25Z","describe":"","fileIndex":"1585728025","latitude":22.6766686619127,"longitude":113.928864975252,"mileage":59,"speed":0}

Json Field Description

Alarm Type Description：

3.3 device event reporting

Topic：upload/{accessKey}/{deviceNum}/event
Description：device event data, such as unlocking and locked
e.g.：

{"assetId":"8454601010","card":"","cells":"460,0,9383,149428936","dateTime":"2025-02-07T06:54:52Z","describe":"","eventType":1,"latitude":22.6766686619127,"longitude":113.928864975252,"mileage":59,"password":"","speed":0,"unLockType":2}

Json Field Description

3.4 Command response report

Topic：upload/{accessKey}/{deviceNum}/cmd
Description：The device responds to the commands sent by the platform
Command response description：Different commands have different response results. For specific commands and their descriptions, please refer to the protocol document.
e.g.：

 //command operation success response
{"assetId":"794308010642","commandType":"BASE1","content":"[\"794308010642\",\"8\",\"001\",\"BASE\",\"1\",\"JT709A_20241115_HW-V1.2_RFID_7600_V2_8\",\"0\",\"Jointech\",\"LE20B05SIM7600M21-A_CUS_JT\",\"898604B81022C1046673\",\"868822046635957\",\"460\",\"0\",\"188975300\",\"10352\"]","dateTime":"2025-02-07T03:52:39.964Z"}
//command operation failed response （Device not online）
{"assetId":"8294630003","commandType":"MQTT_CMD","content":"Device not online！","dateTime":"2025-01-07T09:49:43.158Z"}
//command operation failed response （Device has not been registered）
{"assetId":"8294630481","commandType":"MQTT_CMD","content":"Device has not been registered！","dateTime":"2025-01-07T09:48:32.975Z"}

Json Field Description

3.5 Slave lock(sensor) data reporting

Topic：upload/{accessKey}/{deviceNum}/{subLockNum}/sublock
Description：Slave Device positioning data, including Device ID, positioning time, longitude and latitude, speed, mileage and other information
e.g.：

{"assetId":"8052400203","battery":41,"direction":0,"eventType":3,"gpsTime":"2025-02-07T07:16:07Z","humidity":0,"latitude":-0.0,"locRope":0,"locStatus":0,"locTimes":54,"longitude":-0.0,"recvTime":"2025-02-07T07:14:57.315Z","rssi":15,"sensorType":4,"speed":0,"statusJson":"{\"lockRope\":0,\"gateway\":0}","subAssetID":"E0171E0366","subGpsTime":"2025-02-07T07:15:14Z","subGpsTimestamp":1738912514000,"temperature":-1000.0,"voltage":"3.75"}

JsonField Description

statusJson Field Description

“FStatusJson”:”{"bottomDisassembly":0,"emergencyKey":0,"lockMotor":0,"structuralDisassembly":0,"gateway":0,"lockValve":0}”

3.6 Platform send command

Topic：download/{accessKey}/{deviceNum}/cmd
Description：Send command to the terminal data
command Description：Different device types have different command functions. For specific commands and their descriptions, please refer to the protocol documentation.
e.g.：

(794308010642,1,001,BASE,1)

Code Sample

Introducing paho dependency

<dependency>
    <groupId>org.eclipse.paho</groupId>
    <artifactId>org.eclipse.paho.client.mqttv3</artifactId>
    <version>1.2.0</version>
</dependency>

Establishing an MQTT connection
When establishing a connection, you need to use AccessId, secret, topic, and clientId, which are all assigned by the system. AccessId corresponds to the client’s user, and secret corresponds to the client’s password.

String user         = "u8vngl";//user
String password     = "xxxxxx";//password(MD5-32)
String topic        = "upload/{accessKey}/{deviceNum}/location";
//String topic = "upload/B176C0FF1DFF41D0126BFF7908C76E17/8041254836/location"; //Subscribe to the location data of this device
//String topic = "upload/B176C0FF1DFF41D0126BFF7908C76E17/+/location"; //Subscribe to the location data of this configuration device
//String topic = "upload/B176C0FF1DFF41D0126BFF7908C76E17/#"; //Subscribe to the location, alarm, event and other data of this configuration device

int qos             = 1;//qos2 consumes more energy, please use 1 or 0
String broker       = "mqtt://mqtt.assetscontrols.com:1883";//mqtt server address
String clientId     = "u8vngl_consumer";  //User-defined client name
//When qos is 1 or 2, mqttclient uses
MemoryPersistence persistence = new MemoryPersistence();

try {
    MqttClient client = new MqttClient(broker, clientId, persistence);
    MqttConnectOptions connOpts = new MqttConnectOptions();
    connOpts.setUserName(user);
    connOpts.setPassword(password.toCharArray());
    //When cleanSession is false, the next time you log in with the same clientId, you will    // be able to retrieve all stored messages
   //If true, you will retrieve the last message marked as retained
   //Set cleanSession to true during debugging and testing, and false during production
    connOpts.setCleanSession(false);
    connOpts.setAutomaticReconnect(true);//Set up automatic reconnection
    client.setCallback(new MqttCallback());//Get subscription messages
    client.connect(connOpts);
    client.subscribe(topic, qos);//Subscribe the topic
} catch(MqttException me) {
    me.printStackTrace();
}

Get subscription messages
Paho gets messages by implementing the MqttCallback interface, which gets messages through the messageArrived method

@Override
public void messageArrived(String topic, MqttMessage message) throws Exception {
    //Please put the processing of /message into other threads. If too much time is spent in this method, it will affect the response of qos 1 or 2, making the server think that the message is not successfully delivered.
    System.out.println("topic:" + topic + " msg:" + message);
}


/**
 * [Important Tips]
 * Processing logic after connection loss
 * 1、Reconnect
 * 2、Resubscribe to Topic Data
 * @param cause
 */
@Override
public void connectionLost(Throwable cause) {
    cause.printStackTrace();
    while (true) {
        try {
            //Reconnect
            if (!client.isConnected()) {
                client.reconnect();
            }
            //Resubscribe to Topic Data
            if (client.isConnected()) {
                client.subscribe(topic, qos);
                System.out.println("has resubscribed");
                break;
            }
            TimeUnit.SECONDS.sleep(100);
        } catch (MqttException | InterruptedException e1) {
            e1.printStackTrace();
        }
        System.out.println("client not connect");
    }
}