SiteTrackingFleet reference stack

Bench test

Pending bench test — Validation status.

Fleet dashboard for site vehicles / mobile assets. Device type: site_tracker. Detail mode: tracking.

---

Telemetry contract

Key	Unit	Notes
latitude	°	WGS84
longitude	°	WGS84
speed_kmh	km/h	Ground speed
battery_pct	%	Tracker battery

Sample generators use India-ish lat/lon bands for demo only.

---

Industry map baseline (seeded)

Home and detail dashboards seed:

Surface	Widget	Config highlights
Fleet home	map (fleet-map)	enableClustering, staleAfterMinutes: 15, showGeofences, lat/lon + speed/battery popups
Detail	map	Live position for selected tracker
Detail	routeMap	enablePlayback, detectStops, colorBySpeed, history path

Map capabilities

• Clustering — MapLibre cluster layers when many trackers are on screen
• Stale / offline — amber markers when last fix older than staleAfterMinutes; chip shows stale count
• Geofences — overlay from GET /api/geofences (migration 0041); monitor raises enter/exit alarms (GEOFENCE_MONITOR_ENABLED)
• Route playback — scrubber + play/pause on historical path
• Stops / trips — client-side segmentation from speed / dwell
• Speed colors — path segments colored by speed_kmh
• Reverse geocode (opt-in) — Nominatim, rate-limited; enable in widget config

---

Reference hardware (pending bench test)

Role	Class / example	Protocol
Primary	LTE GPS tracker (Queclink / Teltonika class)	MQTT / HTTP over 4G
Fleet OBD	OBD-II + BLE gateway phone/edge	MQTT
Asset tag	Battery GPS + LoRaWAN	P6 webhook
Yard Modbus GPS	Rare industrial GPS Modbus module	RTU → DTU

Status: Pending bench test — primary path is P4 LTE MQTT, not Modbus.

---

Connectivity options

Profile	Edge	Link	Status
P4	Native LTE tracker	4G MQTT/HTTP	Pending (recommended)
P6	LoRaWAN GPS tag	LoRa → ChirpStack → webhook	Pending
P5	Yard gateway relays tags	WiFi / Ethernet	BYO
P2	ESP32 + GPS UART (lab only)	WiFi	Pending
P1	Modbus GPS + 4G DTU	4G	BYO

---

Wiring — P4 (LTE tracker)

flowchart LR
  AC[Autoconnecto]
  TRK[LTE GPS tracker]
  SIM[Cellular SIM]
  SAT[GNSS]
  TRK --- SIM
  TRK --- SAT
  TRK <-->|MQTT TLS| AC

Step	Action
1	Create device type site_tracker; copy MQTT token
2	Point tracker broker to Autoconnecto; map JSON → keys
3	Confirm lat/lon update interval (e.g. 10–60 s moving)
4	Optional: create yard geofences via POST /api/geofences

---

Wiring — P6 (LoRaWAN)

Configure ChirpStack HTTP integration (device connectivity); decode payload to latitude / longitude / speed_kmh / battery_pct.

---

Checklist

• [ ] Device type site_tracker
• [ ] Coordinates in decimal degrees (not scaled integers)
• [ ] Map / routeMap widgets bind latitude / longitude / speed_kmh
• [ ] Migration 0041_geofences.sql applied for geofence overlay + alarms
• [ ] Reseed SiteTrackingFleet after pulling tracking seed changes

Related

• Connectivity profiles · Route map widget
• Backend: GEOFENCE_MONITOR_ENABLED (see backend ENVIRONMENT.md geofence monitor section)