For industrial LoRaWAN sensors, use OTAA (over-the-air activation) unless the device cannot join: each join gives it fresh session keys and clean frame counters. Use Class A for battery sensors that can wait for their next report to receive a command, and Class C for mains-powered actuators that must receive a command at once.
Both settings live in the device firmware and on the network server, and a mismatch gives you a sensor that is never heard or a command that never arrives. The terms below come from the LoRa Alliance’s LoRaWAN L2 1.0.4 specification. Wired Modbus and SNMP equipment is covered in my post on field devices behind a gateway.
What is the difference between OTAA and ABP?
OTAA devices join the network and get their session keys from the join; ABP (activation by personalisation) devices have their address and session keys written into them and send from the first frame. The specification says an end device implements OTAA, ABP or both.
| OTAA | ABP | |
|---|---|---|
| Stored in the device | DevEUI, JoinEUI and AppKey | DevAddr, NwkSKey and AppSKey |
| Session keys | New at every join | The same for the device’s whole life |
| Frame counters | Reset to 0 at every successful join | Must never be reset, and must survive power loss |
Because ABP devices cannot be rekeyed, the specification recommends OTAA for higher security applications, and it requires a unique NwkSKey and AppSKey per ABP device.
Why does an ABP sensor go quiet after a battery change?
Usually because it restarted its frame counter at 0. The network server accepts only counters that move forward, so the next frames look like replays and are dropped.
The specification forbids ABP devices from resetting their counters, even through a battery replacement, but many devices do it anyway. In Hermetry those frames show in the frames log as Replayed frame or Frame counter jumped, and Hermetry never re-syncs a counter by itself. Reset counters on the device’s LoRaWAN tab accepts the next uplink from 0 and is written to the audit log. Until the device sends again, a recorded old frame could be accepted once, so I press it only after confirming the device really restarted its counters. The steps are on the add an ABP device page.
The DevAddr of an ABP device must also belong to the network’s NetID. With NetID 000000 it must lie between 00000000 and 01FFFFFF, and Hermetry refuses an address outside that range.
Class A or Class C: which one does a sensor need?
Class A suits almost every battery sensor; Class C is for mains-powered devices that must act on a command without waiting. Every LoRaWAN device implements Class A, and Class B and C are optional additions to it.
- Class A: after each uplink the device opens two short receive windows, then sleeps. On Hermetry, RX1 opens 5 seconds after the uplink by default and RX2 one second later. A sensor that reports every hour receives a queued command up to an hour later.
- Class C: the receiver stays on except while the device transmits, which costs power and gives the lowest latency. Typical devices are valves, relays and other actuators.
On Hermetry a Class C downlink goes out at once on the RX2 channel (869.525 MHz at DR0 by default, at most 51 bytes), through the gateway that heard the device last, for up to 15 minutes after its last uplink by default. After that it waits for the next uplink, so a Class C valve still needs regular uplinks. A Class A device marked as C misses downlinks sent at once. The timings are on the device classes page.
Hermetry connects field devices to live dashboards, rules and alerts: IoT telemetry and SCADA in one platform. Its built-in LoRaWAN network server accepts OTAA devices and, since release 2.3.0, ABP devices and Class C downlinks, for LoRaWAN 1.0.2, 1.0.3 and 1.0.4. You choose the activation and the class in the same New device form.
My default for a new industrial sensor is OTAA and Class A. I pick Class C only for a mains-powered device that must obey within seconds, and ABP only when the firmware offers nothing else.
Frequently asked questions
Does Hermetry support LoRaWAN Class B?
No. Hermetry supports Class A and Class C. Class B, where the device opens receive slots on a schedule set by gateway beacons, is not supported, so a battery device that needs commands runs as Class A and receives after its uplinks.
Which LoRaWAN versions does Hermetry accept?
LoRaWAN 1.0.2, 1.0.3 and 1.0.4, for both OTAA and ABP devices, with 1.0.3 as the default for a device added by hand. LoRaWAN 1.1 is not accepted.
Can I change a LoRaWAN device’s class after adding it?
Yes. On the device’s LoRaWAN tab in Hermetry, change Class and select Save class. Devices added through pairing mode take the class of their profile. Match the class to what the firmware really runs.

