WebHMI Docs

User Tools

Site Tools

level2:lvl2_broker

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
level2:lvl2_broker [2021/03/11 17:32] – [AirGate configuration] emozolyaklevel2:lvl2_broker [2021/03/11 17:45] (current) – [AirPoint configuration] emozolyak
Line 10: Line 10:
 Topic's format : //Mounting point_level**/**Device_level**/**Register_level// Topic's format : //Mounting point_level**/**Device_level**/**Register_level//
   *Mounting point is a pass for device data to L2 IoT account   *Mounting point is a pass for device data to L2 IoT account
-  *Device_level is an unique id of the deives+  *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.    *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.  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&400 |}}+{{level2:1_settings_level2.png?direct}}
  
 ===== Example of L2 IoT integration ===== ===== Example of L2 IoT integration =====
Line 40: Line 40:
  
 ==== AirPoint configuration ==== ==== 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.  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) 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.  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. 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. 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. 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. Now you can configure registers to log and create a [[level2:screens|Level2 Screen]] to visualize the data aqused from AirPoint.
level2/lvl2_broker.1615483923.txt.gz · Last modified: 2021/03/11 17:32 by emozolyak
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki