fix(images): modify images url

en/201908/emq-and-yottacloud-retrospect-and-prospect-of-iot-energy-consumption-monitoring-project.md

@@ -25,7 +25,7 @@ Before the project, the plant also carried out energy consumption data collectio
 3. Data collection and display should be guaranteed in real time.
 
 
-![11png.png](https://static.emqx.net/images/4268d9fe7ca2967311d6d9cd94af1a94.png)
+![11png.png](https://assets.emqx.com/images/4268d9fe7ca2967311d6d9cd94af1a94.png)
 
 The project implementation is based on Guizhou YottaCloud's SME cloud platform and EMQ's IoT equipment management and application enablement platform. Guizhou YottaCloud is responsible for the overall project implementation and monitoring platform application development:
 
@@ -37,7 +37,7 @@ The project implementation is based on Guizhou YottaCloud's SME cloud platform a
 - Application layer: Provide real-time monitoring of large-screen and mobile-side small Apps for various industrial meters, and real-time monitoring of data such as electricity meters, gas meters, and photovoltaic power. The application layer implements the threshold setting and alarm capability of the meter data by setting business rules at the platform level, and pushes the alarm message to the plant management personnel in time when the meter reports that the data is overloaded.
   Due to the obsolescence of some of the meters in the plant area, the data acquisition interface cannot be provided. In order to ensure the coverage of the collection, YottaCloud and the plant coordinated and designed the manual meter reading process, and integrated into the automatic acquisition application to achieve unified data aggregation of manual and automatic meter reading.
 
-![22.png](https://static.emqx.net/images/3bc20e77535a89689ff02f5baf4ab447.png)
+![22.png](https://assets.emqx.com/images/3bc20e77535a89689ff02f5baf4ab447.png)
 
 The first stage of the project covered the energy consumption monitoring of the three plants in the Wahaha Guiyang base, deploying 11 industrial gateways, automatically collecting more than 200 electric meters and gas meters,with more than 5,000 data collection points.
 

en/201908/emqx-helps-operators-build-large-scale-nb-iot-platform.md

@@ -28,6 +28,6 @@ In this project, EMQX IoT Message Middleware is the core component of the platfo
 
 EMQX's innovative distributed clustering solution enables automatic addition of new nodes and automatic deletion of faulty nodes, which effectively guarantees the automatic expansion and long-term stable operation of the AEP platform's access capacity and improves the reliability of the carrier's customer service.
 
-![WX20190803150105.png](https://static.emqx.net/images/900e7fe329d84d87e25b631d3bcf6879.png)
+![WX20190803150105.png](https://assets.emqx.com/images/900e7fe329d84d87e25b631d3bcf6879.png)
 
 EMQX has the capabilities of mass equipment access, 10 million high concurrency, IoT full protocol stack, and millisecond low latency that enable the carrier-grade IoT platform to be built in a few months, and effectively supports the landing and commercial operation of the operator's NB-IoT and even the whole IoT platform strategy.

en/201908/mqtt5-new-features-properties-and-loads.md

@@ -8,46 +8,46 @@ The payload of the PUBLISH packet is responsible for storing the message content
 
 **The new properties of the variable header of the CONNECT packet are:**
 
-![1.jpg](https://static.emqx.net/images/52a7175d131df25693c1498c3f287658.jpg)
+![1.jpg](https://assets.emqx.com/images/52a7175d131df25693c1498c3f287658.jpg)
 
 In the Payload of the CONNECT packet, some fields have changed, and the [Will message](https://www.emqx.com/en/blog/use-of-mqtt-will-message) has become a Will Payload. Will properties are added to Payload to define the behavior of a will message.
 
 **The new will properties are:**
 
-![2.jpg](https://static.emqx.net/images/29880f8724b075a58f27caca155c4b9a.jpg)
+![2.jpg](https://assets.emqx.com/images/29880f8724b075a58f27caca155c4b9a.jpg)
 
 ### CONNACK packet
 
 **CONNACK packet does not have Payload, and the properties contained in the variable header are:**
 
-![3.jpg](https://static.emqx.net/images/247af99b45d686958b8ca509be45aa6c.jpg)
+![3.jpg](https://assets.emqx.com/images/247af99b45d686958b8ca509be45aa6c.jpg)
 
 
 ### PUBLISH packet
 
 **The properties of the variable header of the PUBLISH message are:**
 
-![PUBLISH 报文  .jpg](https://static.emqx.net/images/804db596039856802b2073d95f4779a9.jpg)
+![PUBLISH 报文  .jpg](https://assets.emqx.com/images/804db596039856802b2073d95f4779a9.jpg)
 
 
 
 ### PUBACK, PUBREC, PUBREL, PUBCOMP, SUBACK, UNSUBACK PACKET
 
 **PUBACK, PUBREC, PUBREL, PUBCOMP, SUBACK, UNSUBACK all have the following three properties:**
 
-![PUBACK, PUBREC, PUBREL, PUBCOMP, SUBACK, UNSUBACK 报文.jpg](https://static.emqx.net/images/d5fa746bdd091a885b2560884d6da0fc.jpg)
+![PUBACK, PUBREC, PUBREL, PUBCOMP, SUBACK, UNSUBACK 报文.jpg](https://assets.emqx.com/images/d5fa746bdd091a885b2560884d6da0fc.jpg)
 
 
 ### SUBSCRIBE packet
 
 **The properties of the SUBSCRIBE message also exist in the variable header.**
 
-![11.png](https://static.emqx.net/images/b6b2ae013d4ca398689f9e87bc3ea536.png)
+![11.png](https://assets.emqx.com/images/b6b2ae013d4ca398689f9e87bc3ea536.png)
 
 
 The Payload in the SUBSCRIBE packet in MQTT 5.0 contains the [Subscription Options](https://www.emqx.com/en/blog/subscription-identifier-and-subscription-options).
 
-![SUBSCRIBE 报文2.jpg](https://static.emqx.net/images/a019ca4b636fc8782087c8174854945c.jpg)
+![SUBSCRIBE 报文2.jpg](https://assets.emqx.com/images/a019ca4b636fc8782087c8174854945c.jpg)
 
 
 
@@ -73,7 +73,7 @@ The server will treat the packet as a malformed packet.
 
 **The DISCONNECT packet is a new packet from MQTT 5.0. Its introduction means that the mqtt broker has the ability to actively disconnect. The properties of the DISCONNECT packet are:**
 
-![DISCONNECT 报文新增.jpg](https://static.emqx.net/images/fe76d0003f158a53f9fee55a67d1a794.jpg)
+![DISCONNECT 报文新增.jpg](https://assets.emqx.com/images/fe76d0003f158a53f9fee55a67d1a794.jpg)
 
 
 <section class="promotion">

en/201909/2019-smart-china-expo-emq-intel-mec-iot-edge-solution.md

@@ -2,9 +2,9 @@ The 2019 China International Intelligence Industry Expo (hereinafter referred to
 
 Intel Intelligence Innovation Zone relies on Chongqing Intelligence Expo to bring together op science and technology innovation projects, show cutting-edge technology applications and create intelligent and diversified intelligent future scenarios and communities. Notably, the "Intel Intelligence Innovation Zone" shows the EMQ IoT MEC edge device access and management platform.
 
-![ping.jpg](https://static.emqx.net/images/e1faf74e8756f0c2965c3880fcaae306.jpg)
+![ping.jpg](https://assets.emqx.com/images/e1faf74e8756f0c2965c3880fcaae306.jpg)
 
-![39321567417129_.pic_hd.jpg](https://static.emqx.net/images/7d2a2daab7ce2306a379bed2ad80a372.jpg)
+![39321567417129_.pic_hd.jpg](https://assets.emqx.com/images/7d2a2daab7ce2306a379bed2ad80a372.jpg)
 
 ## EMQ  Company Profile
 
@@ -16,7 +16,7 @@ For the Iot In the 5G era, MEC (Multiple Access Edge Computing) technology is th
 
 At 2019 Intelligence Expo, EMQ showed the ability to implement IoT edge cloud device access and edge-end streaming data in the edge cloud virtualization environment provided by the Intel® Xeon processor's MEC system. EMQX Cloud-edge integrated solution based on IOT protocol such as MQTT can realize unified remote management and scheduling of edge nodes through cloud management platform, providing access and data processing service capabilities for massive IoT access and high-reliability low-latency connection scenarios in 5G era. .   
 
-![WX20190904091901.png](https://static.emqx.net/images/b4f68941832c0f64c63c646da308fad0.png)
+![WX20190904091901.png](https://assets.emqx.com/images/b4f68941832c0f64c63c646da308fad0.png)
 
 EMQX Edge can access all kinds of devices at the edge end through industrial protocols such as MQTT, MQTT-SN and [Modbus](https://www.emqx.com/en/blog/building-modbus-based-iiot-app-with-neuron), and realize edge processing and storage of data through the stream data processing engine and edge computing nodes at the edge. The control platform at the cloud remotely monitor and schedule the distributed edge nodes through MQTT or HTTP protocol, and push the edge computing service code such as data flow processing rules to the edge end through the cloud management platform to realize cloud-edge integrated management.
 

en/201909/bridging-mosquitto-to-emqx-cluster.md

@@ -11,7 +11,7 @@ Therefore, Mosquitto is not suitable for the [MQTT broker](https://www.emqx.com/
 Assuming we have an EMQX server'emqx1'and a Mosquitto server, we need to create a bridge on Mosquitto to forward all ''sensor" topic messages to the'emqx1' server and subscribe to all "control" topics from EMQX.
 
 
-![Artboard.jpg](https://static.emqx.net/images/7a8cbb9dec7ef185338b5e577861b627.jpg)
+![Artboard.jpg](https://assets.emqx.com/images/7a8cbb9dec7ef185338b5e577861b627.jpg)
 
 
 **EMQX**  

en/201909/emq-new-version-in-september-emqx-enterprise-3-4-0-function-overview.md

@@ -23,7 +23,7 @@ In order to support the introduction of more new functions and the  improvement
 - Optimize rule creation steps, provide creation wizards to facilitate quick learning of the enterprise, and clarify the rules engine application relationship;
 - Added alarm management, globally displays the current number of alarms, and provides historical alarm record troubleshooting, which is convenient for discovering problems and solving problems and avoiding the risks caused by alarms.
 
-![11111.png](https://static.emqx.net/images/d737da2ec945d7e8e4aa630264d172b9.png)
+![11111.png](https://assets.emqx.com/images/d737da2ec945d7e8e4aa630264d172b9.png)
 
 
 
@@ -33,14 +33,14 @@ Prior to 3.4.0, all modifications to the EMQX main configuration `etc/emqx.conf`
 
 After evaluation, EMQ lists dozens of configuration items that do not affect system stability but have hot configuration requirements, and provide hot configuration capabilities in Dashboard and REST APIs.
 
-![2.png](https://static.emqx.net/images/b89c633085a8e75c186c091d1c50a283.png)
+![2.png](https://assets.emqx.com/images/b89c633085a8e75c186c091d1c50a283.png)
 
 
 
 ### Cluster management is supported by Dashboard
 
 In this version,  management functions are added for clusters. The visual interface provides invitation and kick-out functions for clusters in manual cluster mode. Cluster parameters are displayed in other automatic cluster modes, which greatly facilitates monitoring  management and the reference configuration of new nodes..
-![Dashboard.png](https://static.emqx.net/images/a2be9d0a7ebb7f4e8c22b959f65176a6.png)
+![Dashboard.png](https://assets.emqx.com/images/a2be9d0a7ebb7f4e8c22b959f65176a6.png)
 
 
 
@@ -54,7 +54,7 @@ To address this pain point, a set of Broker's built-in, real-time codec system S
 
 Schematic diagram for use with both Schema and rules engine:
 
-![Schema Registry .png](https://static.emqx.net/images/e295802e25b24d1c66c85b664b155bb4.png)
+![Schema Registry .png](https://assets.emqx.com/images/e295802e25b24d1c66c85b664b155bb4.png)
 
 
 
@@ -66,7 +66,7 @@ At present, three kinds of protocol parsing methods are supported by EMQX :
 - The third-party codec service delivers the original message data through the TCP and HTTP communication to the external codec service, waiting for the coded data to be returned, and then conducting the subsequent logic. The third-party service can be a self-built codec gateway or even a hot Serverless application in cloud computing.
 
 
-![4.png](https://static.emqx.net/images/ae6f8f44bfff90d96a714beccf888647.png)
+![4.png](https://assets.emqx.com/images/ae6f8f44bfff90d96a714beccf888647.png)
 
 
 
@@ -88,7 +88,7 @@ The new vehicle networking protocol access JT/T808, with full name "JT/T 808-201
 
 Schematic diagram of JT/T808 protocol access architecture:
 
-![ JT:T808.png](https://static.emqx.net/images/54516d671cbb83d5a21312903517adca.png)
+![ JT:T808.png](https://assets.emqx.com/images/54516d671cbb83d5a21312903517adca.png)
 
 
 

en/201909/emqx-rule-engine-series-storing-messages-to-cassandra-database.md

@@ -11,7 +11,7 @@ Installation Reference of Cassandra：https://cassandra.apache.org/doc/latest/ge
 ## Principle overview
 
 By configuring the rules engine, EMQX stores messages that meet certain criteria under a given topic into the Cassandra database. The message flow diagram is as follows:
-![Artboard.png](https://static.emqx.net/images/347f6b4787038e60ff443409df36b76a.png)
+![Artboard.png](https://assets.emqx.com/images/347f6b4787038e60ff443409df36b76a.png)
 
 among them:
 
@@ -117,14 +117,14 @@ CREATE TABLE emqx_rule_engine_output.use_statistics (
 
 Open the EMQX Dashboard, go to the **Resources** page of the left menu, click the **New** button, select the Cassandra resource type to create:
 
-![cassrescreate2x.jpg](https://static.emqx.net/images/4b22f6ad34e1d1fccf392bb7f5d2d64b.jpg)
+![cassrescreate2x.jpg](https://assets.emqx.com/images/4b22f6ad34e1d1fccf392bb7f5d2d64b.jpg)
 
 
 
 The network environment of the nodes in the EMQX cluster may be different. After the resources are created successfully, click the **Status button ** in the list to check the connection status of each node. If the resources on the node are unavailable, check whether the configuration is correct and the network connectivity is correct, and click the **Reconnect** button to manually reconnect.
 
 
-![cassresstatus2x.jpg](https://static.emqx.net/images/45a380b895ca101d9dd722eccba84306.jpg)
+![cassresstatus2x.jpg](https://assets.emqx.com/images/45a380b895ca101d9dd722eccba84306.jpg)
 
 
 ### Create a rule
@@ -133,7 +133,7 @@ Go to the **Rules** page on the left menu and click the **New** button to create
 
 After selecting the trigger event, we can see the optional fields and sample SQL on the interface:
 
-![rulecondition2x.jpg](https://static.emqx.net/images/a700543920da98477e073a5e05d6376c.jpg)
+![rulecondition2x.jpg](https://assets.emqx.com/images/a700543920da98477e073a5e05d6376c.jpg)
 
 #### Screen the required fields
 
@@ -201,7 +201,7 @@ The payload data is as follows, note to change the `tachometer` value to satisfy
 
 Click the **SQL Test** toggle button, change `topic` and `payload` to the information in the scenario, and click the **Test** button to view the data output:
 
-![rulesqltest2x.jpg](https://static.emqx.net/images/b635b3c57aa0a9f2528c29c3fe259fbc.jpg)
+![rulesqltest2x.jpg](https://assets.emqx.com/images/b635b3c57aa0a9f2528c29c3fe259fbc.jpg)
 
 
 
@@ -234,7 +234,7 @@ INSERT INTO use_statistics (msgid, client_id, speed, tachometer, ts) VALUES (${i
 ```
 
 
-![cassrulecreate2x.jpg](https://static.emqx.net/images/37d7961092f8690847197561d07ca8be.jpg)
+![cassrulecreate2x.jpg](https://assets.emqx.com/images/37d7961092f8690847197561d07ca8be.jpg)
 
 
 
@@ -273,14 +273,14 @@ Switch to the **Tools => Websocket** page and use any information client to conn
   ```
 
 
-![WechatIMG2206.png](https://static.emqx.net/images/f3aeefde473e6ea328bb31b313fd6b17.png)
+![WechatIMG2206.png](https://assets.emqx.com/images/f3aeefde473e6ea328bb31b313fd6b17.png)
 
 
 
 Click the **Send** button. At this time, the value of `tachometer` in the message body satisfies the condition of `tachometer > 8000` set above. The current rule has been hit and the statistic value plus one.
 
 View the data table records in the Cassandra command line to get the following data:
-![cassruleresult2x.png](https://static.emqx.net/images/9ef015e4beb934fc94ba3581b042efa1.png)
+![cassruleresult2x.png](https://assets.emqx.com/images/9ef015e4beb934fc94ba3581b042efa1.png)
 
 So far, we have implemented a business development to store messages to the Cassandra database through the rules engine.
 

en/201910/emq-iot-edge-streaming-data-processing-software-kuiper-was-open-sourced.md

@@ -38,7 +38,7 @@ As shown in the following figure, Kuiper Server consists of three parts:
 - RPC interface: The RPC interface is mainly used for interaction with client command line tools, including streaming definition and management, rule definition and management, query tools, etc.
 - Rest API interface: The Rest API is mainly used for future management interfaces and interactions in the planned management interface, including streaming definition and management, rule definition and management, query tools, etc.
 
-![components.jpg](https://static.emqx.net/images/0683da520685cd30efd34595da22f4a4.jpg)
+![components.jpg](https://assets.emqx.com/images/0683da520685cd30efd34595da22f4a4.jpg)
 
 
 ## Overview of Kuiper Usage Steps

en/201910/emqx-rule-engine-series-store-messages-to-dynamodb-database.md

@@ -127,19 +127,19 @@ $ aws dynamodb list-tables --region us-west-2 --endpoint-url http://127.0.0.1:80
 
 Open EMQX Dashboard, go to the **Resources** page on the left menu, click the **New** button, type DynamoDB server information for resource creation.
 
-![image01.jpg](https://static.emqx.net/images/22f62479759058690bf6dd468e715a80.jpg)
+![image01.jpg](https://assets.emqx.com/images/22f62479759058690bf6dd468e715a80.jpg)
 
 The network environment of the nodes in the EMQX cluster may be different. After the resources are created successfully, click the **Status** button  in the list to check the connection status of each node. If the resources on the node are unavailable, check whether the configuration is correct and the network connectivity is correct, and click the **Reconnect** button to manually reconnect.
 
-![image02.jpg](https://static.emqx.net/images/a5973e08b0b26d85eb60505610193714.jpg)
+![image02.jpg](https://assets.emqx.com/images/a5973e08b0b26d85eb60505610193714.jpg)
 
 ### Create rules
 
 Go to the left menu of  **rules**  page, click  **new**  button to create rules. Select trigger event  of **message publishing** to trigger this rule for data processing when the message is published.
 
 After selecting the trigger event, we can see the optional field and sample SQL in the interface:
 
-![image03.jpg](https://static.emqx.net/images/1c72e2ec615041b9919dc28b500e5c98.jpg)
+![image03.jpg](https://assets.emqx.com/images/1c72e2ec615041b9919dc28b500e5c98.jpg)
 
 #### Screen the required fields
 
@@ -201,7 +201,7 @@ The payload data is as follows, note to change the `tachometer` value to satisfy
 
 Click the **SQL Test** toggle button, change `topic` and `payload` to be the information in the scenario, and click the **Test** button to view the data output:
 
-![image04.jpg](https://static.emqx.net/images/dc409088b0c06d6aadf0863501d91132.jpg)
+![image04.jpg](https://assets.emqx.com/images/dc409088b0c06d6aadf0863501d91132.jpg)
 
 The test output data is:
 
@@ -223,7 +223,7 @@ After the input and output of SQL condition  is correct, we continue to add the
 
 Click the **Add** button in the response action, select the **Save data to DynamoDB** action, select the resource  just selected, fill the DynamoDB table name, Hash Key, and Range Key.
 
-![image05.jpg](https://static.emqx.net/images/73ccf170e50c8caeaaa7134f4c573b6d.jpg)
+![image05.jpg](https://assets.emqx.com/images/73ccf170e50c8caeaaa7134f4c573b6d.jpg)
 
 ## Test
 
@@ -255,13 +255,13 @@ Switch to **tools -> Websocket** page, connect to EMQX with any client, and send
   "ts": 1563268202
 }
 ```
-![image06.jpg](https://static.emqx.net/images/c11f9cc66c213e5c9ceec676c6216328.jpg)
+![image06.jpg](https://assets.emqx.com/images/c11f9cc66c213e5c9ceec676c6216328.jpg)
 
 Click the **Send** button. After sending successfully, the statistic of hit under  current rule is 1.
 
 View the data table records with the aws cli command to get the following data:
 
-![image07.png](https://static.emqx.net/images/d19a7472d896f9822571908f6ad0651c.png)
+![image07.png](https://assets.emqx.com/images/d19a7472d896f9822571908f6ad0651c.png)
 So far, we have implemented the business development of using the rules engine to store messages to DynamoDB.