New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

Choosing a LoRaWAN platform for industrial monitoring

What a LoRaWAN platform is made of, the questions to ask before you choose one, and how Hermetry handles gateways, the network server, codecs and alarms.

In short: a LoRaWAN platform has to do two jobs: run the network (receive frames through gateways, keep each device’s session and keys, plan downlinks) and turn the frames into readings people use (decode them, store them, show them and alarm on them). Before you choose one, check how the two jobs are joined, which gateways and devices it supports, how it decodes payloads, and where your data is kept.

The parts of a LoRaWAN system

  • End devices (sensors) send short radio frames and listen briefly for answers.
  • Gateways hear every frame in range and forward it over the internet. A gateway does not know which devices are yours.
  • The network server checks each frame, merges the copies heard by several gateways, keeps the device’s session and frame counters, and plans downlinks. Its join server answers the join requests of OTAA devices.
  • The codec turns the bytes of a frame into named values, such as temperature and humidity.
  • The application stores the values, draws the dashboards and runs the alarm rules.

One platform, or several pieces

Some projects run a network server on its own and connect a separate application to it. That works, but every reading crosses one more boundary, and devices, keys and users are managed in two places. A platform with a built-in network server keeps the device, its session, its readings and its alarms in one place. Whichever you choose, ask the questions below.

Questions to ask before you choose

  • Which frequency plan? LoRaWAN uses different frequencies in different regions; the plan must match your gateways and devices.
  • Which gateways? Can you bring standard gateways (for example over the LoRa Basics Station protocol), and does the platform watch their health?
  • Which devices? LoRaWAN version, OTAA or ABP activation, and the device classes you need (Class A for battery sensors, Class C for devices that must receive at any time).
  • How are payloads decoded? Is there a library of codecs for common sensors, and can you write your own when a sensor is missing?
  • What happens to a reading next? Storage, dashboards, alarm rules with severities and escalation, and an API for other systems.
  • Where is the data kept? Which region, and does it stay there.
  • How is it priced? Per device, per message, per gateway? A gateway that counts as a device changes the sums.

How Hermetry handles it

  • Built-in network server. Hermetry runs its own LoRaWAN network server with a join server: OTAA and ABP devices, LoRaWAN 1.0.2 to 1.0.4. Copies of a frame heard by several gateways are merged within your organisation only.
  • Your gateways. Add a Basics Station gateway by its EUI and put the address and token Hermetry gives you on it. A licensed router with a LoRa radio can also be a gateway. Gateway health is stored like any reading, so an offline gateway raises a normal alarm.
  • Codecs. A library of 106 codecs for common sensors decodes their payloads without setup when the maker and port match; for anything else you can write your own codec.
  • One place for the rest. Decoded values are stored on the device and feed dashboards, SCADA screens and alarm rules like any other reading.
  • Data region. Each organisation’s data stays in the region it chose.
  • Pricing. Gateways and end devices count toward your plan’s device limit; a licensed router serving as a gateway counts once.

Frequently asked questions

Do I need my own LoRaWAN network server?

Not with Hermetry: its network server is built in. You add your gateways and devices, and the readings arrive on the devices.

Can I use the gateways I already have?

Gateways that speak the LoRa Basics Station protocol can be added by their EUI; licensed routers with a LoRa radio can be gateways too.

What if a sensor is not in the codec library?

Write your own codec. Until a frame can be decoded, its raw payload is kept as hex, so nothing is lost.

Does a gateway count as a device?

Yes, toward your plan’s device limit, like an end device. A licensed router serving as a gateway counts once.

Read more: How LoRaWAN works in Hermetry, Add a LoRaWAN gateway, The codec library, Regions and frequency plans, Connect your first LoRaWAN sensor, and the use case Cold room and freezer temperature monitoring.

Share

See your field data live this week

Start a trial in your region with your first devices, or book a demo and bring your own use case.