InnerWeb
Skip to main content

Implementation notes: LoRaWAN and ChirpStack in a plant

Adding the ChirpStack network server to a location system is a decision for larger sites or for clients who require the standard, not a default step. IT and OT teams should know what changes and what stays: the radio layer and the network server change, while the system and the panel remain.

700 to 900 PLN
indicative cost of a gateway with a concentrator
Source: spec card
1000+
watches per gateway (upper end of capacity)
Source: spec card

When LoRaWAN makes sense

LoRaWAN with the ChirpStack network server (MIT licence, self-hosted) is an option on request, not the standard. It returns to the table when a site exceeds about 200 to 300 watches, or when the client requires the standard. For smaller sites, the InnerWeb protocol with a simple gateway remains simpler to maintain.

The choice is made per site. A mixed mode on a single watch does not exist, but the system and the panel are shared by sites on both protocols.

What changes and what stays

The watch changes only the firmware of its radio layer, and the hardware stays. The inactivity logic, the BLE scan and the application data format stay unchanged. The system as the backend does not change: a bridge decodes the data from the network server and sends it to the existing pulse and SOS entry points.

On the infrastructure side three new elements appear: gateways with an SX1302 or SX1303 concentrator and 8 EU868 channels with adaptive data rate (ADR), a ChirpStack server maintained in the client's infrastructure, and a bridge between the server and the system.

Indicative gateway hardware cost for 600 watches

Indicative gateway hardware cost for 600 watchesHorizontal bar chart: two simple gateways about 200 PLN, two LoRaWAN gateways between 1400 and 1800 PLN0500100015002000PLN2 simple gateways2 simple gateways: 200 PLN2002 LoRaWAN gateways, lowerbound2 LoRaWAN gateways, lower bound: 1400 PLN14002 LoRaWAN gateways, upperbound2 LoRaWAN gateways, upper bound: 1800 PLN1800
Source: Sample calculation on indicative ranges from 2025 to 2026 deployments; price quoted individually

Deployment steps

Below are the steps from the point of view of the IT and OT teams.

Step 1: decision and scope

Record the reason for the choice: the number of watches, a requirement of the standard, the IT policy. Decide which sites get LoRaWAN and which stay on the InnerWeb protocol.

Step 2: server and gateways

Set up ChirpStack on your own infrastructure and mount gateways with a concentrator. The indicative cost of a gateway is about 700 to 900 PLN, against about 100 PLN for a simple gateway, but capacity grows from a few hundred to over 1000 watches per gateway. These are indicative ranges from 2025 to 2026 deployments; the price is quoted individually.

Step 3: keys and device joining

Keys are issued per device through the OTAA join procedure. Plan how the keys are stored and registered for each watch before the devices are handed to employees.

Step 4: the bridge to the system

Configure a bridge that decodes the data from the network server and passes it to the existing pulse and SOS entry points. Check that a pulse from a watch appears in the panel in the same form as before.

Step 5: SOS and tests

This step needs the most attention. The system response returns in a window after the next uplink, so after SOS the watch sends an additional empty uplink about 3 to 5 s later to receive the result. Test the time from pressing the button to the confirmation on the watch, from the furthest points of the site.

Pitfalls for the IT and OT teams

The most common stumbling points are key management, the SOS response time, and the division of responsibility for the server.

  • The network server is a new element to maintain: updates, backups and monitoring. Decide who runs it, the client's IT or the integrator.
  • SOS on LoRaWAN needs a design: without an extra uplink the watch will not receive confirmation, and the user will not know whether the alarm arrived.
  • Adaptive data rate (ADR) changes the watch's radio parameters over time, so the frame airtime and the channel occupancy are not fixed as they are in the InnerWeb protocol with its set SF9.
  • OTAA keys must be protected: a leaked key allows impersonation of the device.
  • Do not mix protocols on one watch, and do not assume that existing watches with old firmware will work on a LoRaWAN network without an update.

Sample calculation: how many gateways

Take a site with 600 watches. With the capacity of a concentrator gateway in the range of a few hundred watches, at least 2 gateways are needed for capacity, and in practice more for range. The indicative hardware cost for that is 1400 to 1800 PLN for two gateways, without the server, antennas and installation. For comparison, two simple gateways cost about 200 PLN, but they cannot serve that number of watches on one channel.

The number of gateways follows from the range of the site, not only from the number of watches, so this calculation is always followed by a coverage test.

Checklist

Video

Frequently asked questions

Is ChirpStack paid?

ChirpStack is available under the MIT licence and runs self-hosted in the client's infrastructure. The cost lies in running the server and the gateways, not in the licence.

Do the watches need replacing when moving to LoRaWAN?

No. Only the radio layer firmware changes, and the hardware stays.

How does SOS confirmation work on LoRaWAN?

The system response returns in a window after the next uplink, so the watch sends an additional empty uplink about 3 to 5 s after SOS to receive the result.

Sources

Let's consider LoRaWAN for your site

We will go through the steps, the keys and the SOS tests with your IT and OT team, and compare this option with the InnerWeb protocol. We invite you to a conversation.

Let's talk