Getting Started

Getting started with LoRaGuard

Create Account

Onboarding

1. Sign Up

Navigate to:

https://app.loraguard.com

Create an account and start the onboarding wizard.

2. Create an Organization

The first onboarding step is to define an organization. Organizations act as containers that group LoRaWAN applications, devices, gateways, and users.

Fields:

  • Organization Name (free text)

This can be changed or extended later.

3. Create an Application

Applications in LoRaGuard are containers for LoRaWAN devices that forward data via webhook.

Displayed capabilities:

  • Unique webhook URL for LNS integration

  • Automatic device discovery upon first uplinks

Field:

  • Application Name

Using the same name as in TTS helps with identification.

Note: Currently only The Things Stack (TTS) is supported. Additional network servers will follow.

4. Connect the Network Server

In the next step, LoRaGuard generates a unique Webhook URL for the application. This URL is required in the TTS Webhook configuration. See next chapter for detailed instructions on how to set up the webhook on your LNS.

Setting up LNS

The Things Stack

LoRaGuard currently only receives data from The Things Stack (TTS) via webhooks. A webhook must be set up in TTS for each TTS application that is to be monitored.

A single LoRaGuard application can serve multiple TTS applications. Recommendation: Separate by application for a better overview.

1a. Start LoRaGuard onboarding

During onboarding, an integration token is generated and a webhook URL is displayed. Example:

This URL serves as the base URL in the TTS webhook.

The URL can be viewed again at any time:

1b. Create a new Application

During creation of a new (additional) application on LoRaGuard organization, the webhook URL is displayed upon creation or in the application overview and settings page.

2. Select an application in TTS

In the TTS Console:

If you want to connect multiple TTS applications to LoRaGuard, repeat the steps.

3. Create webhook

In the TTS application:

As a template:

Configuration:

  • Webhook ID A freely selectable name, e.g., loraguard-integration

  • Webhook Format: JSON

  • Base URL Insert the webhook URL from LoRaGuard.

Example:

Authentication and downlink API key are not required.

4. Select event types

Activate only one event:

No other events. The optional path extension can be left blank.

5. Save

After saving, TTS will immediately send every uplink packet from this application to LoRaGuard.

The synchronization is visible in the LoRaGuard dashboard:

  • Number of devices

  • Number of gateways

  • RSSI / SNR trends

  • Duty cycle

  • Event summary (offline, signal drop, etc.)

Verify in Onboarding Wizard

The onboarding wizard will constantly look out for device uplinks arriving. Once it has found devices, you can move forward (or move forward anyways if you do not care on waiting for checks).

Delayed statistics after the first connection

Once the integration is set up and uplinks arrive, the first metrics do not appear immediately. LoRaGuard calculates statistics and scores at timed intervals to avoid unnecessary load on the database.

Typical note text in the interface:

Relevant metrics (Energy Score, Signal Score, Duty Cycle, Event Summary) are automatically filled in as soon as the first aggregation is complete.

6. Connect multiple applications (optional)

Simply repeat the process:

  • Open another application in TTS

  • Add webhook

  • Use the same LoRaGuard URL

For a clean separation, we recommend:

  • A separate LoRaGuard application for each TTS application

  • Separate tokens

7. Error patterns

Typical causes when no data appears:

  • Incorrect token in the URL

  • No “uplink message” activated

  • Incorrect TTS application selected

  • Firewall blocks outgoing requests (rare)

PreviousOverview

Last updated