level2:lvl2_broker
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
level2:lvl2_broker [2021/02/12 16:27] – atolstov | level2:lvl2_broker [2021/03/11 17:42] – [Introduction] 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' | + | |
- | </ | ||
==== Introduction ==== | ==== Introduction ==== | ||
- | There is a WebHMI | + | 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' |
+ | |||
+ | 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' | ||
+ | *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. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== Example of L2 IoT integration ===== | ||
+ | |||
- | {{ : | ||
==== AirGate configuration ==== | ==== AirGate configuration ==== | ||
To start with you need to take AirGate and set it to configuration mode. | To start with you need to take AirGate and set it to configuration mode. | ||
Line 18: | Line 29: | ||
- | + | {{ : | |
- | {{ : | + | |
Go to " | Go to " | ||
- | {{ : | + | {{ : |
If you prefer, you can use a WiFi connection via AirGate. Otherwise, leave it empty and work with Ethernet only. | If you prefer, you can use a WiFi connection via AirGate. Otherwise, leave it empty and work with Ethernet only. | ||
Copy and paste Broker' | Copy and paste Broker' | ||
If you leave IP Addresses forms empty it will be configured via DHCP. | If you leave IP Addresses forms empty it will be configured via DHCP. | ||
- | {{ : | + | {{ : |
You can also select " | You can also select " | ||
==== AirPoint configuration ==== | ==== AirPoint configuration ==== | ||
- | {{ : | + | {{ : |
In the account' | In the account' | ||
Copy the AirPoints ID. It is topic' | Copy the AirPoints ID. It is topic' | ||
- | {{ : | + | {{ : |
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. | ||
- | {{ : | + | {{ : |
Check the registers you need from your device. | Check the registers you need from your device. | ||
- | {{ : | + | {{ : |
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. | ||
- | {{ : | + | {{ : |
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: | Now you can configure registers to log and create a [[level2: |
level2/lvl2_broker.txt · Last modified: 2021/03/11 17:45 by emozolyak