Glossary

This page explains terms you'll meet in the Pallax interface or in this documentation — not how the platform works behind the scenes. A term is only listed here if you actually encounter it somewhere; exactly where is noted at each entry.

AppKey

A secret key that a LoRaWAN device needs, together with DevEUI and JoinEUI, to connect to the network. You'll find it on the device itself or its included instructions.

You'll meet it: in the device wizard (Provision device), step "Device Configuration" — as the required field AppKey.

Blueprint

A template that the global search can also search for — alongside devices and gateways.

You'll meet it: in the global search's (⌘K) placeholder text: "Search devices, gateways, blueprints…".

Decoder

Translates a device's raw radio data into readable measurements (e.g. temperature instead of a byte sequence). Without an assigned decoder, a device shows only raw data.

You'll meet it: as its own menu item Decoder, in the Decoder missing filter on the device list, and in the Decoder column there. Explained further in Decoder.

DevEUI

A LoRaWAN device's unique identifier (64 bit, as a hexadecimal number). Together with JoinEUI and AppKey, it identifies your device to the network.

You'll meet it: in the device wizard as the required field DevEUI (64 bit hex), and on the device list via the search field "Search EUI, name, tag…".

Endpoint

A destination Pallax forwards your device data to — for example your own system or an external application.

You'll meet it: on the Cortex page, button Add Endpoint. Explained further in Cortex.

EUI

Short for "Extended Unique Identifier" — a globally unique identifier for a device or gateway, shown as a hexadecimal number. DevEUI and JoinEUI are both EUIs with different purposes.

You'll meet it: in the device list's search field ("Search EUI, name, tag…") and as part of DevEUI/JoinEUI in the device wizard.

Gateway

The device that receives your sensors' radio signals and forwards them to the network. A gateway itself doesn't measure anything — it connects your devices to Pallax.

You'll meet it: as its own asset kind in the device wizard, as the device type LoRaWAN Gateway on the device list, and on the Cockpit as its own node in the network topology.

JoinEUI

Also called AppEUI — together with DevEUI and AppKey, it identifies the application a LoRaWAN device joins.

You'll meet it: in the device wizard as the required field JoinEUI / AppEUI.

LoRaWAN

A wireless technology for devices that send small amounts of data over long distances, infrequently. One of two technologies you choose between when provisioning a device or gateway.

You'll meet it: in the device wizard as a technology option ("LoRaWAN — Long Range Wide Area Network"), and as a technology tag on the device list.

Mioty

A wireless technology for very large numbers of devices in a confined area. The second of the two technologies you choose between when provisioning a device or gateway.

You'll meet it: in the device wizard as a technology option ("Mioty — Massive IoT technology"), and as a source group in the Console.

Payload

The actual data a device sends — the raw form a decoder turns into readable measurements.

You'll meet it: as the tab Payload Decoders on the Decoder page.

Tenant

The administrative umbrella around your workspaces, users, and subscription — at its core, your company or organization account with Pallax.

You'll meet it: in the account menu as Tenant Management, which covers tenant details, subscription, and users, among other things. In depth in User & Tenant Administration.

Uplink

A message sent by a device or gateway — the path by which measurements arrive at Pallax. Its counterpart, a message to the device, doesn't appear in this documentation because it hasn't yet been observed in the interface.

You'll meet it: on the device detail page as Last uplink or "Awaiting first uplinks", and on the gateway detail page (tab Monitoring, with the Pallax Agent) as Uplink Queue.

Workspace

The level below your tenant where your gateways, devices, dashboards, and reports live. A tenant can have several workspaces; you grant access to them via workspace roles in Tenant Management.

You'll meet it: in the header, in the sidebar, in the workspace switcher when moving between several workspaces, and throughout this documentation (e.g. User & Tenant Administration, Setup).