For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

Run your own LoRaWAN network inside Widgelix - gateways, device profiles and end devices.

The LoRaWAN Network Server (LNS) module lets your organization run LoRaWAN infrastructure directly in Widgelix, without an external network server such as The Things Stack or ChirpStack Cloud. Open it from the sidebar: LoRaWAN Server.

The page header shows the server status (Active once activated) and a main button that changes with the selected tab (+ Add gateway, + Add device profile or + Add device).

Tab
Purpose
Page

Gateways

Register and monitor LoRaWAN gateways (base stations).

Device profiles

Region, MAC version, activation and class settings shared by groups of devices.

Devices

Register end devices and their OTAA or ABP keys.

Every tab has a search field, Fit screen / Expand to size the table, and a Refresh button that reloads the data (e.g. Last seen timestamps) without reloading the page.

Access requirements

A user needs:

  1. Menu access: LoRaWAN Server enabled for their role.

  2. Module permissions on the LoRaWAN module:

Action
Required permission

View gateways, profiles and devices

LoRaWAN → Read

Activate the network server, add or edit entities

LoRaWAN → Write

Delete gateways, profiles or devices

LoRaWAN → Delete

The default Viewer role does not include LoRaWAN access. See Roles & Permissions.

Activating the network server

The network server is activated once per organization:

  1. Open LoRaWAN Server.

  2. If it is not active yet, click Activate on the Activate LoRaWAN Network Server screen.

Activation provisions the network server tenant and application for your organization and requires Write permission. Afterwards the status shows Active and the three tabs become available.

  1. Activate the network server.

  2. Create at least one device profile with the correct region and MAC version.

  3. Register your gateways and point their packet forwarders to the network server.

  4. Register the devices with their keys.

  5. Make sure each device also exists as an asset with the same DevEUI, so that its data is decoded and shown on dashboards.

How it connects to the rest of Widgelix

  • Assets: an LNS device is the radio registration; the asset with the same DevEUI holds the decoded data, dashboards and actions. When adding an LNS device you can pick it directly from your platform assets. In the asset's Settings → Connectivity select the Widgelix LoRaWAN Network Server.

  • Actions: the condition option Gateway connectivity alert (Gateway goes offline / online) is available when the network server is used. See Creating an Action.

  • Downlinks: downlinks created on the asset are queued through the network server.

  • Troubleshooting: see Troubleshooting for common problems and a setup checklist.

Last updated