LoRaWAN Industrial Deployment Guide

Start with the measurement

Industrial LoRaWAN projects fail when the radio plan is written before the measurement. Decide whether you need leak, level, flow, or pressure. The industrial solution page and the catalog list the kits; this guide covers how they share one network server.

Survey RF paths in plant rooms and outdoor pads. Metal rooms may need an antenna outside the panel or a gateway in the corridor. Do not buy a second gateway until the survey says the first cannot hear the node.

Join, decode, and trend

Join with OTAA. Paste each model’s decoder once on ChirpStack or The Things Network, then clone only onto identical hardware. A rising frame counter with empty fields is a codec problem. A stuck counter is a silent node.

Export on an interval you can maintain. Faster uplinks shorten battery life and can hit duty-cycle limits. Stock trials start at 100 units so you can prove one profile before branding at 500.

Hand-off to operations

Give operations the room names, decoder version, and a red-row rule that matches the site limit — not a second invented limit in the IoT platform. Replacement sensors keep the same asset name when the DevEUI changes so year-two trends stay comparable.

Destination-market documentation is a separate pack. Ask for it on the quote rather than assuming every carton carries every mark.

Security and change control

Treat AppKeys like passwords. Do not paste them into public tickets or screenshot them into chat. Rotate documentation when a contractor leaves the project.

Version the decoder file next to firmware. When a destination customer opens a ticket six months later, mismatched codecs look like dead radios.

Keep a simple change log: gateway ID, profile name, decoder revision, and the date the first room went live. That log shortens every future expansion.

FAQ

OTAA or ABP?

Stock kits default to OTAA. Do not invent ABP session keys for a standard join.

Where are decoder field maps?

The public decoder library lists named fields for all 11 kits. Byte offsets in the shipped file win if examples differ.

How do I separate join failure from codec error?

See the ChirpStack and TTN integration pages. Frame counter behavior is the fastest tell.

When do I need a second gateway?

Only after a survey shows the first cannot hear the node. Metal rooms often need an antenna outside the panel first.

What should operations receive at hand-off?

Room names, decoder version, red-row rules matching site limits, and an asset register that survives DevEUI swaps.