Differences

This shows you the differences between two versions of the page.

--- level2:lvl2_broker [2021/02/12 16:27] – atolstov
+++ level2:lvl2_broker [2021/03/11 17:45] (current) – [AirPoint configuration] emozolyak
@@ Line 1: / Line 1: @@
-===== MQTT Broker =====
+===== Level2 IoT Core MQTT Broker =====
-<WRAP center round box 60%>
-MQTT Address: 46.101.154.93 \\
-Port: 1883 \\
-Topic's format : //Mounting point_level**/**Device_level**/**Register_level//
-</WRAP>
 ==== Introduction ====
-There is a WebHMI MQTT Broker to connect devices such as AirPoints, AirGates or a custom devices among one or more Level2 account's nodes.
+There is a MQTT broker and powerful IoT tool in the Level2 services - to connect devices such as AirPoints, AirGates or a custom devices among one or more Level2 account's nodes.
+Please refer to MQTT arcticle.
+Each Level2 account has a setting to filter out topics, related to the account and associated devices. This attribute is called Mounting point.
+Topic's format : //Mounting point_level**/**Device_level**/**Register_level//
+  *Mounting point is a pass for device data to L2 IoT account
+  *Device_level is an unique id of the devices
+  *Register level is a useful part of the topic, like value, or key-value string etc.
+If you your device is to be connected to L2 IoT Core its Mqtt settings should match those in the mqtt integration settings in the Level2 account.
+{{level2:1_settings_level2.png?direct}}
+===== Example of L2 IoT integration =====
-{{ :level2:1_settings_level2.png?400 |}}
 ==== AirGate configuration ====
 To start with you need to take AirGate and set it to configuration mode.
@@ Line 18: / Line 29: @@
+{{ :level2:2_192.168.4.1.png?direct&400 |}}
-{{ :level2:2_192.168.4.1.png?400 |}}
 Go to "Configure WiFi"
-{{ :level2:3_192.168.4.1_wifi.png?400 |}}
+{{ :level2:3_192.168.4.1_wifi.png?direct&400 |}}
 If you prefer, you can use a WiFi connection via AirGate. Otherwise, leave it empty and work with Ethernet only.
 Copy and paste Broker's Login, password and Mounting Point to set it up to you Level2 account.
 If you leave IP Addresses forms empty it will be configured via DHCP.
-{{ :level2:4_erase_and_see_the_settings.png?400 |}}
+{{ :level2:4_erase_and_see_the_settings.png?direct&400 |}}
 You can also select "Info" menu entry and see the networking info.
 ==== AirPoint configuration ====
-{{ :level2:5_settings_packet.png?400 |}}
+{{:level2:5_settings_packet.png?direct}}
 In the account's page "Connection" you will in the "MQTT Client" console message from device, if AirGate configured well and AirPoint's packet was captured by AirGate and delivered to MQTT Broker.
 Copy the AirPoints ID. It is topic's second level hierarchy enrty starting with AP (e.g. ID875-872-697/**AP2A674195F0**/json)
-{{ :level2:6_ap_settings.png?400 |}}
+{{:level2:6_ap_settings.png?direct}}
 Paste ID and enter info about device to indicate the place where is it installed.
-{{ :level2:7_regs_co2.png?400 |}}
+{{:level2:7_regs_co2.png?direct}}
 Check the registers you need from your device.
-{{ :level2:8_reg_empty.png?400 |}}
+{{:level2:8_reg_empty.png?direct}}
 There is a registers editor, where you can add or remove them and also set it is properties, such as value type, multiplicator and shift, alarm states, Telegram alert thresholds, Mirroring to another much shorter topic or set is as a resource.
-{{ :level2:9_reg_read_ap.png?400 |}}
+{{:level2:9_reg_read_ap.png?direct}}
 Test your devices again with new packet.
 Now you can configure registers to log and create a [[level2:screens|Level2 Screen]] to visualize the data aqused from AirPoint.