Each card is a gateway room. Tags listed use smoothed RSSI room assignment. After guided 4-corner calibration, the mini map on each calibrated room shows tag dots at estimated in-room position (RSSI vs corner references).
One profile per room (up to 50). Easiest: use guided calibration — step 1 tap where the BLE gateway is on the room map (each outlet is different), then four corners: we highlight each corner, you move there and tap one button; we capture 2.5s per corner (same as manual) and merge all four into one room vector. Advanced: single Sample 2.5s still works. With two or more calibrated rooms, room pick uses a joint z-score across rooms (shared μ/σ per gateway) plus a pair margin so two similar rooms do not flip-flop. Reject threshold below still applies to mean-centered dB fit. Server: data/fingerprints.json or DASHBOARD_FINGERPRINTS_PATH.
Pick a tracked tag you will wear or hold at each corner during the wizard (same hardware you care about later is best). RSSI shape differs by device; one profile is shared by all tags. You need live packets from that MAC before starting.
Room numbers follow the server gateway list order (same MAC → same room index every load). Tag estimated room = smoothed RSSI winner with sticky hysteresis across those gateways.
Live signal vector magnitude (SVM) from MOKO-style x_axis_data / y_axis_data / z_axis_data (tracked tags only).
Pipeline: optional near–free-fall dip → impact spike (high SVM) → post-impact settle (SVM returns close to 1g and stays tight for a hold time), then a confidence gate from strong impact, free-fall hint, or orientation change.
W6 docs say the wristband can broadcast real-time 3-axis accelerometer data for fall recognition; these defaults are a wrist-oriented starting point, not a waist/chest model.
| Tag | MAC | SVM (g) | Phase | Peak (g) | Alerts |
|---|---|---|---|---|---|
| Waiting for accelerometer rows from tracked tags… | |||||
Live snapshot from gateway-ingestor (/health via this dashboard).
Prod / dev show allowlist versions and MAC counts pushed or reconciled on the ingestor.
Forwarding reflects ingestor env (not your API process). Batch and allowlist reconcile URLs below come from the ingestor container env (same as the worker uses for POST / GET).
With INGEST_QUEUE_MODE=redis, redis_enqueued means batches reached Redis; this panel also shows stream length, pending entries, and dead-letter count.
Queue flush removes all pending stream entries and recreates worker consumer groups.
| Time | Route | Action | Count | Batch / detail |
|---|---|---|---|---|
| Open this tab to load events… | ||||
Tip: to verify HTTP delivery to your API, watch ingest-worker container logs or add metrics on your batch endpoint.