Changes for page LT-22222-L -- LoRa I/O Controller User Manual

Last modified by Saxer Lin on 2025/04/15 17:24

From version < 180.1 >

edited by Dilisi S
on 2024/11/09 06:08

To version < 186.1 >

edited by Dilisi S
on 2024/11/11 02:43

Change comment: Nov 10 edits part 1

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 2 added, 0 removed)
- thingseye-events.png
- thingseye-json.png

Details

Page properties

Content

@@ -126,21 +126,14 @@
  * 1 x Counting Port
  )))
--= 2. Assembling the Device =
++= 2. Assembling =
--== 2.1 What is included in the package? ==
++Attach the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise.
--The package includes the following items:
--
--* 1 x LT-22222-L I/O Controller
--* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
--* 1 x bracket for DIN rail mounting
--* 1 x programming cable
--
--Attach the LoRaWAN antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise.
--
  == 2.2 Terminals ==
++The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals.
++
  Upper screw terminal block (from left to right):
  (% style="width:634px" %)
@@ -167,26 +167,30 @@
  |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
  |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
--== 2.3 Powering the LT-22222-L ==
++== 2.3 Powering the device ==
--The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect the power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator (PWR) LED will turn on when the device is properly powered.
++The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.
++Powering on the device
--[[image:1653297104069-180.png]]
++Once powered, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
++{{warning}}
++We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.
++{{/warning}}
--= 3. Operation Mode =
--== 3.1 How does it work? ==
++[[image:1653297104069-180.png]]
++
++= 3. Registering with a LoRaWAN Network Server =
++
  By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports OTAA (Over-the-Air Activation), the most secure method for activating a device with a LoRaWAN network server. The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network, enabling the device to perform OTAA activation with the network server upon initial power-up and after any subsequent reboots.
--After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LE**D will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
++After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
  In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device.
--== 3.2 Registering with a LoRaWAN network server ==
--
  The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
  [[image:image-20220523172350-1.png||height="266" width="864"]]
@@ -201,28 +201,33 @@
  === 3.2.2 The Things Stack Sandbox (TTSS) ===
++The Things Stack Sandbox was formally called The Things Stack Community Edition.
++
  * Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
--* Create an application if you do not have one yet.
--* Register LT-22222-L with that application. Two registration options are available:
++* Create an application with The Things Stack if you do not have one yet.
++* Go to your application page and click on the **End devices** in the left menu.
++* On the End devices page, click on **+ Register end device**. Two registration options are available:
--====   ====
--
  ==== 3.2.2.1 Using the LoRaWAN Device Repository ====
--* Go to your application and click on the **Register end device** button.
  * On the **Register end device** page:
--** Select the option **Select the end device in the LoRaWAN Device Repository**.
--** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**.
--** Select the **Frequency plan** that matches your device.
++** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
++** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
++*** **End device brand**: Dragino Technology Co., Limited
++*** **Model**: LT22222-L I/O Controller
++*** **Hardware ver**: Unknown
++*** **Firmware ver**: 1.6.0
++*** **Profile (Region)**: Select the region that matches your device.
++** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
--* Page continued...
--** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
--** Enter the **DevEUI** in the **DevEUI** field.
--** Enter the **AppKey** in the **AppKey** field.
--** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
++* Register end device page continued...
++** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'.
++** In the **DevEUI** field, enter the **DevEUI**.
++** In the **AppKey** field, enter the **AppKey.**
++** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
  ** Under **After registration**, select the **View registered end device** option.
  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
@@ -229,25 +229,25 @@
  ====   ====
--==== 3.2.2.2 Entering device information manually ====
++==== 3.2.2.2 Adding device manually ====
  * On the **Register end device** page:
--** Select the **Enter end device specifies manually** option as the input method.
--** Select the **Frequency plan** that matches your device.
--** Select the **LoRaWAN version**.
--** Select the **Regional Parameters version**.
--** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
--** Select **Over the air activation (OTAA)** option under the **Activation mode**
--** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
++** Select the option **Enter end device specifies manually** under **Input method**.
++** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
++** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3**
++** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A**
++** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hidden section.
++** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
++** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
--* Page continued...
--** Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
--** Enter **DevEUI** in the **DevEUI** field.
--** Enter **AppKey** in the **AppKey** field.
--** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
++* Register end device page continued...
++** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'
++** In the **DevEUI** field, enter the **DevEUI**.
++** In the **AppKey** field, enter the **AppKey**.
++** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
  ** Under **After registration**, select the **View registered end device** option.
  ** Click the **Register end device** button.
@@ -262,15 +262,15 @@
  ==== 3.2.2.3 Joining ====
--Click on **Live data** in the left navigation. The Live data panel for your application will display.
++On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
--Power on your LT-22222-L. It will begin joining The Things Stack LoRaWAN network server. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).
++Now power on your LT-22222-L. It will begin joining The Things Stack. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).
  [[image:lt-22222-join-network.png||height="625" width="1000"]]
--By default, you will receive an uplink data message every 10 minutes.
++By default, you will receive an uplink data message from the device every 10 minutes.
  Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object.
@@ -279,6 +279,10 @@
  If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **End devices** > **LT-22222-L** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
++{{info}}
++The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters.
++{{/info}}
++
  [[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
@@ -544,13 +544,13 @@
  (((
  **In addition to that,  below are the commands for AVI1 Counting:**
--(% style="color:blue" %)**AT+SETCNT=3,60**(%%)**           (Sets AVI Count to 60)**
++(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI Count to 60)**
--(% style="color:blue" %)**AT+VOLMAX=20000**(%%)**       (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
--(% style="color:blue" %)**AT+VOLMAX=20000,0**(%%)**    (If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
--(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)**    (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
  )))
@@ -614,15 +614,17 @@
  For example, if you configured the following commands:
--* **AT+MOD=1 **            **~-~->**   The normal working mode
++* **AT+MOD=1 **            **~-~->**   The default work mode
  * **AT+ADDMOD6=1**   **~-~->**   Enable trigger mode
  The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. LT will send uplink packets in two cases:
 . Periodically uplink (Based on TDC time). The payload is the same as in normal mode (MOD=1 for the commands above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks.
--1. Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**CONFIRMED uplinks.**
++1. (((
++Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**confirmed uplinks.**
++)))
--(% style="color:#037691" %)**AT Command to set Trigger Condition**:
++(% style="color:#037691" %)**AT Commands to set Trigger Condition**:
  (% style="color:#4f81bd" %)**Trigger based on voltage**:
@@ -794,51 +794,67 @@
  )))
--== 3.4 Configure LT via AT Commands or Downlinks ==
++== 3.4 Configure LT-22222-L via AT Commands or Downlinks ==
--
  (((
--User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks.
++You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
  )))
  (((
  (((
--There are two kinds of Commands:
++There are two tytes of commands:
  )))
  )))
--* (% style="color:blue" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
++* (% style="color:blue" %)**Common commands**(%%):
--* (% style="color:blue" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
++* (% style="color:blue" %)**Sensor-related commands**(%%):
--=== 3.4.1 Common Commands ===
++=== 3.4.1 Common commands ===
  (((
--These commands should be available for all Dragino sensors, such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]].
++These are available for each sensors and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s.
  )))
++=== 3.4.2 Sensor-related commands ===
--=== 3.4.2 Sensor related commands ===
++These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload.
  ==== 3.4.2.1 Set Transmit Interval ====
  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
--* (% style="color:#037691" %)**AT command:**
++(% style="color:#037691" %)**AT command**
--(% style="color:blue" %)**AT+TDC=N**
++(% style="width:500px" %)
++|Command|AT+TDC<time>
++|Response|
++|Parameters|<time> uplink interval is in milliseconds
++|Example|(((
++AT+TDC=30000
--where N is the time in milliseconds.
++Sets the uplink interval to 30,000 milliseconds (30 seconds)
++)))
--**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
++(% style="color:#037691" %)**Downlink payload**
++(% style="width:500px" %)
++|Payload|(((
++<prefix><time>
++)))
++|Parameters|(((
++<prefix> 0x01
--* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
++<time> uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
++)))
++|Example|(((
++01 **00 75 30**
--(% style="color:blue" %)**0x01 aa bb cc  **(%%)**   ~/~/ Same as AT+TDC=0x(aa bb cc)**
++Sets the uplink interval to 30,000 milliseconds (30 seconds)
++Note: 00 75 30 (hex) = 30000 (dec)
++)))
--
  ==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
@@ -859,8 +859,8 @@
  ==== 3.4.2.3 Poll an uplink ====
++Requests the device to send an uplink.
--Asks the device to send an uplink.
  * (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
@@ -874,7 +874,6 @@
  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
--
  Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
@@ -892,9 +892,8 @@
  ==== 3.4.2.5 Poll trigger settings ====
++Polls the trigger settings.
--Polls the trigger settings
--
  * (% style="color:#037691" %)**AT Command:**
  There is no AT Command for this feature.
@@ -905,11 +905,10 @@
--==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
++==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as a trigger ====
++Enable or disable DI1/DI2/DI2 as a trigger.
--Enable or Disable DI1/DI2/DI2 as trigger,
--
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
  **Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
@@ -921,11 +921,10 @@
--==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
++==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
++Sets DI1 or DI3 (for LT-33222-L) as a trigger.
--Set DI1 or DI3(for LT-33222-L) trigger.
--
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b**
  (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
@@ -940,12 +940,10 @@
  (% style="color:blue" %)**0x09 01 aa bb cc    ** (%%)    ~/~/ same as AT+TRIG1=aa,0x(bb cc)
++==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
--==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
++Sets DI2 as a trigger.
--
--Sets DI2 trigger.
--
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
  (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
@@ -960,12 +960,10 @@
  (% style="color:blue" %)**0x09 02 aa bb cc   **  (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc)
++==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
--==== 3.4.2.9 Trigger – Set AC (current) as trigger ====
++Sets the current trigger based on the AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--
--Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM**
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
@@ -976,9 +976,8 @@
  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
++Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--Set current trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--
  * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM    **(%%)**        See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
@@ -986,10 +986,8 @@
  (% style="color:blue" %)**0x AA 00 aa bb cc dd ee ff gg hh    ** (%%) ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--
  ==== 3.4.2.11 Trigger – Set minimum interval ====
--
  Sets AV and AC trigger minimum interval.  Device won't response to the second trigger within this set time after the first trigger.
  * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+ATDC=5        ** ~/~/ (%%)Device won't response the second trigger within 5 minute after the first trigger.
@@ -1006,6 +1006,7 @@
  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
++Controls the digital outputs DO1, DO2, and DO3
  * (% style="color:#037691" %)**AT Command**
@@ -1383,25 +1383,25 @@
  == 3.5 Integrating with ThingsEye.io ==
--The Things Stack applications can be integrated with ThingsEye.io. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
++The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
--=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
++=== 3.5.1 Configuring The Things Stack ===
--We use The Things Stack Sandbox for demonstating the configuration but  other
++We use The Things Stack Sandbox in this example:
--* In **The Things Stack Sandbox**, select your application under **Applications**.
--* Select **MQTT** under **Integrations**.
--* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one.
--* For the **Password**, click the **Generate new API key** button to generate a password. You can see it by clicking on the **eye** button. The API key works as the password.
++* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
++* Select **MQTT** under **Integrations** in the left menu.
++* In the **Connection information **section, under **Connection credentials**, The Things Stack displays an auto-generated **username**. You can use it or provide a new one.
++* Click the **Generate new API key** button to generate a password. You can view it by clicking on the **visibility toggle/eye** icon. The API key works as the password.
--NOTE. The username and  password (API key) you created here are required in the next section.
++{{info}}
++The username and  password (API key) you created here are required in the next section.
++{{/info}}
  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
  === 3.5.2 Configuring ThingsEye.io ===
--This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server.
--
  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
  * Under the **Integrations center**, click **Integrations**.
  * Click the **Add integration** button (the button with the **+** symbol).
@@ -1438,9 +1438,9 @@
  **Downlink data converter (this is an optional step):**
  * Click the **Create new** button if it is not selected by default.
--* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
++* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name.
  * Click the **JavaScript** button.
--* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here.
++* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]].
  * Click the **Next** button. You will be navigated to the **Connection** tab.
  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
@@ -1450,7 +1450,7 @@
  * Choose **Region** from the **Host type**.
  * Enter the **cluster** of your **The Things Stack** in the **Region** textbox. You can find the cluster in the url (e.g., https:~/~/**eu1**.cloud.thethings.network/...).
--* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The username and password can be found on the MQTT integration page of your The Things Stack account (see Configuring MQTT Connection information with The Things Stack Sandbox).
++* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see Configuring The Things Stack).
  * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
  [[image:message-1.png]]
@@ -1469,7 +1469,7 @@
  **Viewing integration details**:
--Click on your integration from the list. The Integration details window will appear with the Details tab selected. The Details tab shows all the settings you have provided for this integration.
++Click on your integration from the list. The **Integration details** window will appear with the **Details **tab selected. The **Details **tab shows all the settings you have provided for this integration.
  [[image:integration-details.png||height="686" width="1000"]]
@@ -1476,24 +1476,25 @@
  If you want to edit the settings you have provided, click on the **Toggle edit mode** button. Once you have done click on the **Apply changes **button.
--Note: See also ThingsEye documentation.
++{{info}}
++See also ThingsEye documentation.
++{{/info}}
--
  **Viewing events:**
--This tab  displays all the uplink messages from the LT-22222-L.
++The **Events **tab displays all the uplink messages from the LT-22222-L.
--* Click on the **Events **tab.
  * Select **Debug **from the **Event type** dropdown.
  * Select the** time frame** from the **time window**.
--[insert image]
++[[image:thingseye-events.png||height="686" width="1000"]]
--- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
--[insert image]
++* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
++[[image:thingseye-json.png||width="1000"]]
++
  **Deleting the integration**:
  If you want to delete this integration, click the **Delete integratio**n button.
@@ -2226,10 +2226,10 @@
  **Package includes**:
--* LT-22222-L I/O Controller x 1
--* Stick Antenna for LoRa RF part x 1
--* Bracket for controller x1
--* 3.5mm Programming cable x 1
++* 1 x LT-22222-L I/O Controller
++* 1 x LoRa antenna matched to the frequency of the LT-22222-L
++* 1 x bracket for DIN rail mounting
++* 1 x 3.5mm programming cable
  **Dimension and weight**:

thingseye-events.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+530.6 KB

Content

thingseye-json.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+554.8 KB

Content

Changes for page LT-22222-L -- LoRa I/O Controller User Manual

Summary

Details

Applications

Navigation