edge The simulator is the authority here
This whole page is deleted when real hardware arrives. Nothing on it survives the swap — which is exactly why it is kept apart from the server view.
Capability matrix
Behaviour is selected by capability, never by device type. The asymmetry
below is the topology: a Tool Tag has ble but not
ble_scanner or cellular, so it can be heard and
cannot report.
| type | accelerometer | arm_disarm | battery | ble | ble_scanner | cellular | device_health | geofence | gnss | heartbeat | nfc | signal_strength | tamper_switch | temperature |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TOOL_TAG | ✓ | · | ✓ | ✓ | · | · | ✓ | · | · | ✓ | ✓ | ✓ | · | · |
| GUARD_TAG | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | · | ✓ | ✓ | ✓ |
Radio & coverage
| Usable BLE range | 21.5 m assumed |
| Path-loss exponent | 2.7 |
| Advertisements emitted | 120 |
| Heard by someone | 110 (91.7%) |
| Total sightings | 151 |
| Tags that went dark | 5 |
Range is derived from the path-loss parameters, never stated separately — an independent constant disagreed with the model once already.
Scanners (Guard Tags & gateways)
| device | type | online | duty cycle |
|---|---|---|---|
| GUARD-000000 | GUARD_TAG | yes | 100% |
| GUARD-000001 | GUARD_TAG | yes | 100% |
| GUARD-000002 | GUARD_TAG | yes | 100% |
| GUARD-000003 | GUARD_TAG | yes | 100% |
Tags (relayed — no link of their own)
| device | scanners in range | coverage | went dark |
|---|---|---|---|
| TOOL-000001 | 2 | overlapped | yes |
| TOOL-000002 | 2 | overlapped | — |
| TOOL-000003 | 1 | single | — |
| TOOL-000004 | 2 | overlapped | — |
| TOOL-000005 | 2 | overlapped | — |
| TOOL-000006 | 1 | single | yes |
| TOOL-000007 | 2 | overlapped | — |
| TOOL-000008 | 2 | overlapped | — |
| TOOL-000009 | 1 | single | — |
| TOOL-000010 | 1 | single | yes |
| TOOL-000011 | 1 | single | yes |
| TOOL-000012 | 1 | single | yes |
dark = no scanner in range. Everything such a tag emits is lost permanently; it holds no buffer.