Hermetry has its own LoRaWAN network server and join server. You connect your LoRaWAN gateways to it, add your end devices, and choose a codec that turns their radio frames into readings. Gateways and end devices are ordinary devices in Hermetry: they appear on the Devices page, count toward your device limit, and use the same dashboards, alarms and flows as every other device.
LoRaWAN is part of the IoT add-on.
What is supported
| Item | Support |
|---|---|
| Region | EU868 (Europe 863–870 MHz). This is the only region switched on. |
| LoRaWAN versions | 1.0.2, 1.0.3 and 1.0.4 |
| Activation | OTAA (over-the-air activation) and ABP (activation by personalisation) |
| Device classes | Class A and Class C |
| Gateway connection | Basics Station (LNS protocol) with a token, and licensed routers over their own secure link |
| Adding many devices | Pairing mode: devices that share one AppKey are added when they join, with an optional approval step |
| Downlinks | Raw application downlinks (hex or base64) on FPort 1–223, unconfirmed or confirmed |
| Decoding | A library of 106 codecs, your own table codecs, or no codec (raw payload to your flows) |
| Gateway health | Round trip, traffic, downlink results and duty-cycle use, stored as the gateway’s telemetry |
What is not supported
| Item | Status |
|---|---|
| Class B | Not supported. |
| Regions other than EU868 | Region data for other bands exists in the network server but is not switched on. You cannot choose another region. |
| LoRaWAN 1.1 | Not supported. A device set to 1.1 is refused. |
| The legacy UDP packet-forwarder protocol | Not supported. Gateways must use Basics Station (or be licensed routers). |
| Codecs that run scripts (JavaScript decoders) | Not accepted. Codecs are tables. |
| Downlink encoders (named commands that build the bytes for you) | Not available. You send the bytes yourself. |
| Local mode on the gateway and LoRaWAN relays | In development. See Local mode and relays. |
Where to start
- Read How LoRaWAN works in Hermetry for the big picture.
- Find your network server address.
- Add a gateway and connect it.
- Add your end devices: OTAA, ABP, or many at once with pairing mode.
- Check that the right codec decodes your sensor.
For a short guided path, see Connect your first LoRaWAN sensor.
Pages in this section
Gateways
- How LoRaWAN works in Hermetry
- Your network server address
- Add a LoRaWAN gateway
- Connect a Basics Station gateway
- Licensed routers as LoRaWAN gateways
- Gateway status, health and the map
- Gateway credentials, disable and delete
End devices
- LoRaWAN device profiles
- Add an OTAA device
- Add an ABP device
- Pairing mode
- Approving devices added by pairing
- How a device joins, step by step
- Device classes A and C
- The device’s LoRaWAN tab
- The frames log
Radio
Decoding
- Codecs: turning bytes into values
- The codec library
- Write your own codec
- Codecs API
- Cleaning up decoded values
Reference and help
- Troubleshooting joins
- Troubleshooting uplinks and downlinks
- LoRaWAN limits
- Local mode and relays
- LoRaWAN API
Permissions
| Permission | Lets a person | Default minimum role |
|---|---|---|
| View LoRaWAN gateways | See gateways, the gateway map and the setup values | User |
| Add, edit, disable and delete LoRaWAN gateways and rotate their tokens | Manage gateways | Admin |
| View LoRaWAN devices | See the LoRaWAN tabs of devices and profiles | User |
| Add, edit and delete LoRaWAN devices and set their AppKey | Add and change end devices, profile LoRaWAN settings, pairing mode, approvals | Admin |
| Reveal the AppKey of a LoRaWAN device | Read a stored AppKey through the API (every reveal is audited) | Admin |
| View the live LoRaWAN frames | Open the frames log | User |
| View LoRaWAN codecs and run the codec test bench | Browse codecs and test them | User |
| Add, change and delete your own LoRaWAN codecs | Publish and delete your codecs | Admin |