New: the AI firewall watches every module and explains each incident in plain words. See how it works

The device’s LoRaWAN tab

Everything on an end device's LoRaWAN tab – identity, join state, codec, class, keys, latest reception, recent frames and actions.

Every LoRaWAN end device has a LoRaWAN tab on its device page. It shows who the device is on the network, how it was last heard, and its recent frames, and it holds the LoRaWAN actions. The same tab on a gateway shows the gateway instead; see Gateway status, health and the map.

Open Devices, open the device and select LoRaWAN. Viewing needs the permission to view LoRaWAN devices; every change needs the permission to add, edit and delete LoRaWAN devices. Without it, the fields are read-only and the buttons are hidden.

A device without a LoRaWAN record shows This device has no LoRaWAN record. Add LoRaWAN devices and gateways with New device on the Devices page.

Actions at the top

ButtonShown forDoes
ApproveA device pairing mode added that waits for approvalLets it join. See Approving devices added by pairing.
Reset sessionOTAA devicesEnds the session; the device must join again.
Reset countersABP devicesClears the frame counters after the device restarted them. See Add an ABP device.
RemoveEvery deviceRemoves the device, its keys and its session and releases its DevEUI. Its readings stay.

Each action asks you to confirm first and is audited.

Note

A LoRaWAN device cannot be deleted with the generic device delete. Use Remove here, which removes the LoRaWAN record first.

Identity

The heading LoRaWAN carries the join badge (see How a device joins).

FieldShows
DevEUIThe device EUI, with a copy button
JoinEUIThe JoinEUI
ActivationOTAA or ABP
DevAddrThe device’s current network address
LoRaWAN version, classFor example 1.0.3 · A
Frame counters up / downThe last uplink counter and the next downlink counter
Last uplinkWhen the last uplink was accepted, or Never
AppKey (OTAA)Stored encrypted, never shown, or The profile’s shared key for devices added by pairing
Session keys (ABP)Stored encrypted, never shown
Counters last reset (ABP)When the counters were last reset, or Never

Codec

Choose the device’s Codec and select Save:

  • Automatic (by maker and port): the profile’s codec, or, if the profile is also automatic, the codec that claims the device’s maker and FPort. Your own codecs are preferred over the library’s.
  • None (raw payload to the flows): no decoding; the payload arrives as hex under raw.
  • A library codec or one of yours (Yours).

See Codecs: turning bytes into values.

Class

Choose A (battery, answers after each uplink) or C (mains powered, always listening) and select Save class. See Device classes A and C.

Keys

Type new keys into the write-only fields and select Replace keys:

ActivationFieldsEffect
OTAANew AppKeyApplies from the device’s next join. The DevNonce history starts over.
ABPDevAddr, New NwkSKey, New AppSKeyStarts a new session with counters at 0.

Hermetry asks first: set the same values in the device, or it stops being heard. If you cancel, the tab says Nothing was changed. Stored keys are never shown.

Latest reception

One row per gateway that heard the device’s last uplink, best SNR first:

ColumnShows
GatewayThe gateway’s name (or EUI)
RSSI (dBm)Received signal strength. Closer to 0 is stronger.
SNR (dB)Signal-to-noise ratio. Higher is better; LoRa still decodes below 0.
Chosen for the downlink✓ on the gateway that answered this uplink

Only the last uplink is shown. Reception history is kept only if one of your flows saves the lora.* keys; with Add the radio values on in the profile and the default root flow, it is.

Recent frames

The device’s frames from the last day, newest first, read again every 10 seconds while the tab is open and the page is visible (up to 50). Columns, types and results are the same as in the frames log.

Through the API

RequestDoes
GET /tenant/<tenantId>/api/iot/lorawan/devices/<deviceId>The device’s LoRaWAN record and live session (never a key)
PATCH …/devices/<deviceId>Change name, joinEui, macVersion, class, codecId, anyJoinEui, or keys (appKey, or devAddr + nwkSKey + appSKey)
DELETE …/devices/<deviceId>/sessionReset session (OTAA)
DELETE …/devices/<deviceId>/countersReset counters (ABP)
POST …/devices/<deviceId>/keyReveal the AppKey (separate permission, audited)
DELETE …/devices/<deviceId>Remove

See the LoRaWAN API.