InnerWeb
Skip to main content

How to choose the LoRa watch beacon interval

The beacon interval is a single setting that affects battery life, the inactivity detection delay and channel occupancy at the same time. The default of 120 s works at most plants, but it helps to know when to shorten it and when to extend it.

30-3600 s
range of the beacon interval in the panel
Source: karta
120 s
default beacon interval
Source: karta
about 0.2%
airtime of the watch at a 120 s interval
Source: karta

What the watch does between beacons

The LoRa watch spends most of its time in deep sleep, which lets it work on battery for days rather than hours. By default it wakes up every 120 s, scans BLE for about 3 s and sends a frame with the visible transmitters, the battery level and the status.

The beacon interval is the time between consecutive wake-ups. Shortening it means more wake-ups, more BLE scans and more frames, and therefore higher battery use and greater channel occupancy. Lengthening it does the opposite, but postpones the location and inactivity information.

Three constraints that have to be balanced

The first constraint is the battery: the less often the watch wakes up, the longer it works. The second is the detection delay: the system learns about the location and battery state only from the next frame, so the beacon interval sets how fresh that data is. The third is the band: the 10% airtime limit and the channel occupancy by all the watches.

SOS and inactivity alarms do not wait for the periodic beacon: they are sent immediately, outside the cycle, and after completing the HTTP request the gateway sends back an acknowledgement of the result. The beacon interval therefore refreshes only the position, the battery and the online status, not the response time to an alarm.

Airtime limit for a single watch

A frame lasts about 230 ms on air. With the 10% airtime limit in the 869.4-869.65 MHz sub-band, the theoretical minimum gap is about 2.3 s. The panel range, 30-3600 s, is many times safer than that. At a 120 s interval the watch uses about 0.2% of its airtime.

Channel occupancy with more watches

The 10% limit applies to one transmitter, but all the watches share the channel. Example calculation for 100 watches: a 230 ms frame times 100 gives 23 s of transmission in each interval. At 120 s this is about 19% channel occupancy, at 60 s about 38%, and at 30 s about 77%. At such occupancy the risk of frame collisions rises, so for a large fleet a 30 s interval is not a good choice.

Number of frames per hour from one watch by beacon interval

Number of frames per hour from one watch by beacon intervalBar chart: frames per hour from a watch fall from 120 at a 30 s interval to 6 at a 600 s interval0255075100125frames/h30 s: 120 frames/h12030 s60 s: 60 frames/h6060 s120 s: 30 frames/h30120 s300 s: 12 frames/h12300 s600 s: 6 frames/h6600 s
Source: Example calculation: 3600 s divided by the beacon interval

How to choose the value step by step

Start with the default 120 s and check in the panel how often frames arrive from different places. Only then change the interval, preferably for one pilot group. The setting is central in the panel, within the range of 30-3600 s, and returns to the watch in the system response, so the devices do not need to be touched.

  • Define the largest acceptable delay in detecting inactivity and location for a given group of workers.
  • For a high-risk zone choose a shorter interval, for example 60 s, but only for a small group of watches. Treat 30 s as a diagnostic mode: the battery then lasts about one day of work.
  • For most workers keep 120 s, or extend it to 300 s if battery life matters more than the speed of location updates.
  • Calculate the channel occupancy: number of watches times 0.23 s, divided by the interval in seconds.
  • After a change, check the location accuracy, the arrival time of frames and the battery state after a week of work.

Audit evidence and common pitfalls

For the documentation it is enough to record the adopted interval, the justification for groups set differently, and the channel occupancy calculation. This supports showing that the settings were chosen deliberately for the risk and not picked at random.

The most common pitfall is shortening the interval for all watches after a single incident. The result is faster battery drain and greater channel occupancy with no real gain in safety. The second pitfall is ignoring the gateways: frames must also be passed to the system through repeater gateways, and duplicates are rejected.

Channel occupancy by 100 watches by beacon interval

Channel occupancy by 100 watches by beacon intervalHorizontal bar chart: channel occupancy is 76.7% at 30 s, 38.3% at 60 s, 19.2% at 120 s and 7.7% at 300 s020406080%30 s30 s: 76.7 %76.760 s60 s: 38.3 %38.3120 s120 s: 19.2 %19.2300 s300 s: 7.7 %7.7
Source: Example calculation: 100 watches, 230 ms frame, occupancy = 100 x 0.23 s / interval

Video

Frequently asked questions

Does a shorter interval always improve safety?

No. It shortens the location and inactivity delay, but increases battery use and channel occupancy. For most workers the default 120 s is a sensible compromise, and a shorter interval makes sense for small groups in risk zones.

Does changing the interval require touching the watches?

No. The interval is set centrally in the panel, and the new value returns to the watch in the system response to the next beacon.

What about a watch outside beacon range?

The frame is still sent, and the system substitutes the last known location. Battery, status and inactivity reach the system even outside beacon range.

Let us match the settings to your zones

We will go through the risk zones and the number of watches together, to choose beacon intervals and calculate the channel occupancy. Let us arrange a call.

Let's talk