Two protocols, one system
By default the watch works on the InnerWeb v2 protocol: frames encrypted with AES-128-CCM, with an 8-byte authentication code and replay counters. The alternative is LoRaWAN with the ChirpStack network server (MIT licence, self-hosted). It is an option on request, not the standard.
A mixed mode on a single watch does not exist. The choice applies to a site: a small site stays on the InnerWeb protocol, while a large one may get LoRaWAN. The system and the panel are shared, so a group of plants does not have to maintain two applications.
Recommendations for the integrator
The recommendations below follow from the decisions for small sites and from the description of the LoRaWAN option.
Recommendation 1: small sites stay on the InnerWeb protocol
For sites with up to a few dozen watches, an additional network server is one more element to maintain, with no benefit. The InnerWeb protocol works with a simple gateway and does not need a LoRaWAN server.
Recommendation 2: about 200 to 300 watches is the signal to talk about LoRaWAN
The option returns to the table when a site exceeds about 200 to 300 watches, or when the client requires the standard. This is not a hard boundary, only the point at which gateway capacity and key management start to matter.
Recommendation 3: a client's standards requirement decides
If the group's IT policy requires an open standard and device management through a network server, LoRaWAN is justified regardless of the number of watches.
Recommendation 4: do not mix protocols on one watch
Changing the protocol means changing the firmware of the radio layer of the watch. The hardware stays, and the inactivity logic, the BLE scan and the application data format stay unchanged, but a single watch works in one mode.
Recommendation 5: plan SOS separately for LoRaWAN
In LoRaWAN 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. This path requires its own design and testing, which the InnerWeb protocol does not need.
Indicative gateway hardware cost: InnerWeb protocol vs LoRaWAN
Parameter comparison
The LoRaWAN option uses a gateway with an SX1302 or SX1303 concentrator and 8 EU868 channels with adaptive data rate (ADR). Keys are issued by the OTAA join procedure per device. The indicative cost of such a gateway is about 700 to 900 PLN, against about 100 PLN for a simple gateway with a single radio. Capacity grows from a few hundred to over 1000 watches per gateway.
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. This means that moving one site from the InnerWeb protocol to LoRaWAN requires no changes at the others.
How to decide across a group of plants
Start with an inventory: the number of watches per site, the presence of Wi-Fi on the grounds, and the requirements of the IT policy. For each site, record the choice and the reason. A shared panel lets you compare the results of the sites, so data from the pilots supports the next decisions.
As long as no site has full Wi-Fi coverage or exceeds the threshold, the default choice is the InnerWeb protocol. The backhaul is built only at the first site without full coverage, by default as a repeater gateway.
Video
Frequently asked questions
Is LoRaWAN the standard in the system?
No. It is an option on request, considered for sites above about 200 to 300 watches or where the client requires the standard.
Can protocols be mixed within one site?
Not on a single watch. The choice is made per site, and the system and the panel are shared by all sites in the group.
Does changing the protocol require replacing the watches?
No. The radio layer firmware changes, while the hardware, the BLE scan and the inactivity logic stay.
Sources
Let's choose a protocol for each site
We will run an inventory of your sites with you and indicate the protocol for each of them. We invite you to a conversation with our team.
Let's talk