The situation
Scenario: in a production plant the administrator notices that a worker's watch on the yard has not reported its position for several hours. The worker did not call for help, and the system shows the last known position as outdated with its time stamp. The administrator's question: was the device discharged, out of coverage, switched off, or did the app stop working.
This is an example scenario, built on the behaviour of the device log function. The figures come from the function description and an observed configuration, not from a specific event.
What the log records
The watch keeps an event log: sensor decisions, the course of an alarm and heartbeat transmissions. It sends it to the server in batches, which makes it possible to reconstruct the course of an alarm after the fact. Apart from the log, the device periodically sends the beacons it hears, signal strength, battery level and status, from which the platform knows the worker's position.
For the administrator the log answers the question of what the device was doing while the server knew nothing about it. This matters, because silence on the server side does not prove that the device was not working.
Stillness alarm thresholds on the device
Diagnosis method step by step
Below is a breakdown by case, in the order in which they most often appear in real rollouts.
Step 1: check the last heartbeat
Establish the time of the last message from the device and the battery level at that moment. A low battery just before the silence points to discharge.
Step 2: review the log batches
The log is sent every third heartbeat cycle, that is approx. 78 s at a 26 s interval, up to 89 entries per batch. Find the last batch that was sent and see what was recorded just before the silence.
Step 3: assess the log window
The device queue holds 89 entries, so after approx. 2 hours without connectivity the start of the gap disappears. If the gap lasted longer, the log shows only the end, and the beginning will not be available.
Step 4: check the stillness logic
The stillness alarm on the device works independently of the server. In the observed configuration it vibrates after 120 s without movement, and after 233 s without confirmation from the server it turns into a short pulse every 34 s. It does not vibrate while charging or at rest. The record of these events answers the question of whether the worker was warned.
What the log can and cannot do
The log reconstructs the course after the fact, but it cannot fill a gap that was not recorded. With a break longer than the queue window the beginning is lost. This limitation is worth knowing when designing procedures: do not promise that after a day of silence you will reconstruct every minute.
The log also does not replace an assessment of why power or coverage failed. It requires comparison with the data about beacons, the charger and the work at the given location.
Diagnosis note template
After each diagnosis, record five items: the time of the last heartbeat, the battery level at that time, the last log batch, the conclusion about the cause and the corrective action. After several such notes, patterns become visible: frequent discharges in one branch, coverage gaps in one place, configuration errors after an update. The patterns translate into changes in the issuing procedure, beacon placement or fleet profile, not just repair of a single watch.
Conclusions for the administrator
First, the heartbeat interval and the batch size determine how far back you can look. With 89 entries and approx. 2 hours the window is short. Second, the stillness alarm works locally, so the warning to the worker may have worked despite the server's silence. Third, the procedure should assume a review of the log in the first hours after an incident, before the gap grows.
Agree in the team who checks the log and within what time after a loss of connectivity. Combine this diagnostics with the watch issuing checklist, because some causes of silence (discharge, wrong configuration) come from actions before the shift.
Video
Frequently asked questions
Does server silence mean the watch was not working?
No. The stillness alarm works on the device independently of the server, and the log records events even without connectivity, within the queue limit.
How far back does the log reach?
The queue holds 89 entries, so after approx. 2 hours without connectivity the start of the gap disappears.
What does the heartbeat send?
The beacons it hears, signal strength, battery level and the device status.
Does this case describe a real plant?
No. It is a scenario based on the function parameters and an observed configuration.
Let's talk about devices at your plant
We will show how to match devices to roles and how the system connects them on one map. Book a conversation with the InnerWeb team.
Let's talk