This tutorial provides a step-by-step guide to integrate The Things Network (TTN) v3 with the TagoIO Platform. By following these instructions, you will enable uplink and downlink operations, allowing data exchange between your LoRaWAN devices and the TagoIO application.
Go to your TTN v3 console and create a new Integration. You can create a new integration under the menu Integrations > Webhooks > Add Webhook.
Configure the Webhook:
Field
Description
Webhook ID
Enter a unique identifier (e.g., tagoio-integration).
Webhook Format
Select JSON from the dropdown menu.
Downlink API Key
Enter a preferred value. This key facilitates downlink operations to your devices via TagoIO.
Additional Headers
Add a header for Authorization and set its value to the authorization token you copied in Step 1.
Webhook Endpoint
Use the endpoint format ttn.middleware.REGION.tago.io. Replace REGION with your deployment region (e.g., us-e1, eu-w1). For a list of available regions, visit TagoIO Network Integration.
In your Webhook configuration, you can activate any event type, but we recommend enabling the, “Uplink message” and "Location solved” event type and add “uplink” to the Webhook settings. This configuration allows the Webhook to automatically forward the data to TagoIO whenever your device transmits data to the network.
After filling in all the fields, click Save to create the webhook integration.
The endpoint ttn.middleware.tago.io points to the USA region. As we are committed to continuing support for this endpoint, we recommend that users in the USA region update their webhooks to ttn.middleware.us-e1.tago.io.
Step 3: Add Device in TagoIO
To integrate your device with the TagoIO Platform, follow these guidelines:
Ensure Device EUI Consistency:
When creating the device in TagoIO, use the exact same Device EUI that is configured in TTN/TTI.
The Device EUI must match exactly to establish a successful connection between TTN and TagoIO.
Select the Appropriate Network and Device Type:
Choose the LoRaWAN TTI/TTN v3 Network during the device setup process.
Select the correct device type from the available options. If your device is not listed, you can add support through connectors.
Add Device Support via Connectors (If Necessary):
If your device type is not available in the default list, enhance its compatibility by utilizing connectors.
For more information on available connectors and how to use them, refer to the Connector Overview.
For detailed instructions on adding devices, visit the Adding Devices page.
Finalizing Setup
Power On Your Devices:
Turn on your LoRaWAN device and gateway to initiate data transmission.
Verify Data Reception:
In TagoIO, navigate to the Device and into the Data tab to confirm that data is being received.
Alternatively, use the Live Inspector within your device settings to monitor incoming data in real-time.
With data successfully flowing into TagoIO, you can start creating Dashboards, Analyses, and Actions to visualize and manage your device data effectively.
It’s not yet clear to me if and how I can get other data than uplink messages e.g. from the LoRa cloud location solver. In the TTN v3 Tago.IO webhook I enabled the solver but I do not see any data variables that correspond to the solver data
Hello @vitor . The uplink is working for me without any issue. However I am trying to use the downlink from TagoIO to TTN V3 and it is not working.
I tried both procedures described in the documentation in (Downlink for LoRaWAN™):
1- From device/Configuration Parameters; I am getting this error on TTN side
* \_downward
23:26:27
device-ota-v3
Drop downlink data message
Invalid `downlinks[0]`: embedded message failed validation: Invalid `f_port`: value must be inside range \[1, 255\]
* arrow\_downward
23:26:27
device-ota-v3
Receive downlink data message
Payload
55
Actions
2- From Dashboard by installing an Analysis: I am getting this error when I try to do the install:
An error has ocurred while installing the template: (1621031587004) Sorry, Internal Error
Hi,
I’m checking this issue regarding the downlink analysis.
You can open an issue at TagoIO to keep track of when it is fixed, or I’ll update you through here later today.
I`ve noticed some customers having problem with downlinks at TTN.
Since this integration automatically collects downlink URL and downlink Key from the uplink, the downlinks will not work if the uplink doesn`t include those parameters.
I suggest contacting TTN if you need support to include this information in your uplink, but the issue can be fixed on TagoIO side as well.
In order to fix on TagoIO side, follow the instructions:
Go to your device at TagoIO.
Access the Configuration parameters tab.
Create two new rows by clicking in the + button.
In the first row, enter downlink_url as the key, and enter a valid downlink URL from TTN.
In the secodn row, enter downlink_key as the key, and enter a valid downlink key from TTN.
Hope you are doing ok! I am new at this so pls pardon my ignorance. I have a Laird RG1xx and some radiobridge temp sensors (RBS306-ATH-EXT) that I want to collect data to create dashboard. My question is if I need to input them directly in tago or do I need them on TTN? I have the gateway already online in TTN but don’t know if the integration that you are discussing here is the one I need to create to be able to get the information to create the dashboards.
Pls if you can let me know if you can point me in the right direction.
You don’t necessarily need to add it to TTN, it depends on your device’s manual. Most LoRaWAN devices can be used with any Network depending on your gateway. If you want to connect it directly to TagoIO, I’d recommend using the Generic HTTPS network since it has less restrictions.
I followed the instructions and with my first LoRa device everything is fine (I only use uplink). Then I wanted to add a second LoRa device. The data from the second device is somehow not appearing in Tago. I generated a second authorization for TTN in Tago and a second webhook in TTN, Then it works with the second device. I thought a single authorization and a single webhook in TTN would be sufficient for any number of devices. Is there maybe a bug? Can someone confirm that a single authorization and webhook is sufficient for any number of devices?
You only need a single Authorization code for all of your devices, make sure the second device is within the same application and using the same webhook over at TTN.
The endpoint ttn.middleware.tago.io points to the USA region. As we are committed to continuing support for this endpoint, we recommend that users in the USA region update their webhooks to ttn.middleware.us-e1.tago.io.
