Differences

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

--- level2:lvl2_broker [2021/03/11 17:20] – atolstov
+++ level2:lvl2_broker [2021/03/11 17:45] (current) – [AirPoint configuration] emozolyak
@@ Line 6: / Line 6: @@
 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. 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.
+Each Level2 account has a setting to filter out topics, related to the account and associated devices. This attribute is called Mounting point.
-{{ :level2:1_settings_level2.png?direct&400 |}}
-<WRAP center round box 60%>
-MQTT Address: 46.101.154.93 \\
-Port: 1883 \\
 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 =====
-</WRAP>
 ==== AirGate configuration ====
 To start with you need to take AirGate and set it to configuration mode.
@@ Line 21: / Line 27: @@
 By the way, it is can be another gateway (AirGate) preconfigured in your area. [[:level2:lvl2_broker#airpoint_configuration|So you can skip this steps]].
 </WRAP>
@@ Line 35: / Line 40: @@
 ==== AirPoint configuration ====
-{{ :level2:5_settings_packet.png?direct&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?direct&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?direct&400 |}}
+{{:level2:7_regs_co2.png?direct}}
 Check the registers you need from your device.
-{{ :level2:8_reg_empty.png?direct&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?direct&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.