Applications and devices¶
An application is a group of devices whose data goes to the same place: it holds the integrations and MQTT credentials. Group by purpose or by customer, e.g. Building A sensors or Customer X, not by device model; that is what device profiles are for.
Before you start¶
Get these from the device's label, box or the manufacturer:
| Detail | What it is |
|---|---|
| DevEUI | The device's unique 16-hex-digit ID |
| JoinEUI (AppEUI) | 16 hex digits; often all zeros |
| AppKey | 32 hex digits; the device's secret root key for joining. Treat it like a password |
| Region and LoRaWAN version | To pick or create the right device profile |
Add the device¶
In the native UI:
- Applications → Add, if you don't have one yet.
- In the application, Add device: DevEUI, JoinEUI, the profile. For OTAA enter the AppKey (for LoRaWAN 1.0.x it goes in the Application key field shown for your MAC version).
- Power on the device, or reset it so it joins again.
- Open the device's LoRaWAN frames / Events tab to see live traffic. Live streams close after 15 minutes; reload the page to continue.
You should see a JoinRequest followed by a JoinAccept, then the first uplinks.
Device not joining?¶
- No JoinRequest at all: no gateway hears the device. Check a gateway is online and in range, and that it uses the same region (US915: sub-band 2).
- JoinRequest but no JoinAccept: the DevEUI, JoinEUI or AppKey doesn't match what's in the device, or the MAC version in the profile is wrong.
- Joins, then goes quiet: check the device's reporting interval; many ship with hours between uplinks. The manufacturer's configuration tool or downlink commands can shorten it for testing.
Registered devices count towards your plan's cap, including disabled ones.
Next: get your data out.