LoRaWAN Class A, B and C: which device class to choose?
LoRaWAN device classes decide when a device listens. Class A uses the least power, Class B listens on a schedule, and Class C listens almost continuously and needs mains power.
Request a demoRenokta Ekibi ·

- 1. Describe the deviceDecide whether the device is battery-powered or mains-powered.
- 2. Command needAsk whether the network must send commands and how much delay is acceptable.
- 3. Select the classPick Class A, B or C according to the need.
- 4. Network supportVerify that the gateway and network server support the class.
- 5. Pilot checkMeasure battery use and command delay in a pilot installation.
LoRaWAN device classes define when an end device listens for messages from the network. Class A listens only briefly after its own transmission and uses the least energy. Class B adds scheduled listening slots. Class C listens almost all the time, so it needs a continuous power supply.
Why does the device class matter?
The class sets both how fast the network can send a command to a device and how much energy the device uses. Keeping the radio on consumes power; listening less extends battery life but delays downlink messages. Choosing a class therefore comes down to how quickly you need to reach the device.
Most LoRaWAN traffic flows from the device to the network. Downlink messages serve rarer jobs such as changing a setting, acknowledging a message or switching an output.
How does Class A work?
Class A is the base class every LoRaWAN device must support. The device sends a measurement whenever it needs to, then opens two short receive windows one after the other and switches the radio off. The network can only reply inside those windows.
- Power: Because listening happens only right after an uplink, this class has the lowest energy use.
- Latency: A command from the network waits until the device's next transmission.
- Typical use: battery-powered sensors that send infrequently, such as temperature, humidity, door and water leak sensors.
When is Class B needed?
Class B adds receive slots at scheduled intervals on top of the Class A windows. To keep these slots aligned, the device synchronizes its clock with beacons sent by the gateway.
- Power: It uses more energy than Class A and less than Class C.
- Latency: A command can be delivered in the next scheduled slot, so the delay is predictable.
- Typical use: valve or meter applications that must be reachable at regular intervals without listening all the time.
Class B support has to exist in the gateway, the network server and the device firmware together, so confirm that each component supports it before you plan around it.
Which devices suit Class C?
A Class C device keeps its receive window open whenever it is not transmitting. Commands arrive almost immediately, but with the radio always on you should not expect years of battery life.
- Power: It needs mains, a solar panel or another continuous supply.
- Latency: This class has the lowest delay for downlink messages.
- Typical use: relays, contactors, lighting control and other devices switched remotely.
Which class should you pick, and when?
If the device runs on a battery and mainly reports measurements, choose Class A. If you must send commands to it, first decide how quickly each command has to arrive.
- No commands, or delay is acceptable: Class A.
- Commands can arrive with a predictable delay and the device is battery-powered: Class B.
- Commands must arrive right away and the device has continuous power: Class C.
Different classes can coexist in one project. Sensors can be Class A while a relay or valve controller is Class C. When you plan gateway load, remember that Class C downlinks also use airtime.
What mistakes are common when choosing a class?
The most common mistake is picking Class C for every device "just in case". That drains batteries quickly and needlessly demands mains power. The opposite also happens: if a relay that must react immediately is set to Class A, the command waits until the next uplink and the expected reaction never comes.
- Choosing a class without asking whether commands are needed.
- Expecting Class C behavior from a battery-powered device.
- Not verifying gateway and server support for Class B beforehand.
- Overlooking that downlink messages also use airtime and gateway capacity.
How does the class affect battery life?
The longer a device listens, the more energy it uses, so the same battery lasts much longer in a Class A device than in a Class C one. The exact duration depends on the device, reporting interval, temperature and signal conditions, so quoting a figure would be misleading. The manufacturer's datasheet and a short pilot measurement are the most reliable sources here.
In short, the class sets the balance between battery life and command speed. For most battery sensors Class A is the right choice; for controlled outputs you may need Class B or C. If you want to work out the right mix for your project, you can request a needs discovery from our LoRaWAN sensor infrastructure solution page.
Frequently asked questions
- What is the difference between LoRaWAN Class A, B and C?
- The difference is when the device listens. Class A listens only after sending, Class B also listens at scheduled times, and Class C listens almost continuously.
- Which class suits battery-powered sensors?
- Class A usually suits battery-powered sensors. The radio stays on only briefly after each transmission, so energy use is the lowest.
- Can a Class C device run on a battery?
- A Class C device listens continuously, so long battery life should not be expected. Mains or another continuous power source is recommended.
- Can different classes share one network?
- Yes, devices of different classes can work on the same network. Confirm beforehand that the gateway and network server support the classes you plan to use.
- What does Class B need from the gateway?
- Class B devices align their clocks using beacons. The gateway and the network server therefore have to support Class B.
