Skip to content

EmComm Layout Phase 2: Local APRS, Net Operations, Messaging & Logging #829

@accius

Description

@accius

EmComm Layout — Phase 2+ Feature Roadmap

Following the initial EmComm layout release in v26.1.1, we've received detailed feedback from the user who originally requested the feature. This issue tracks the next phases of development.

Full roadmap: docs/emcomm-roadmap.md

Core Design Principle

Local-first. Each station runs OHC locally. Internet may be unavailable during emergencies — all core EmComm functions must work over RF alone.


Phase 2 — Local APRS Integration

  • Local APRS daemon (critical path) — rig-bridge plugin connecting to Direwolf, hardware TNC, or AGWPE for bidirectional APRS over RF without internet
  • Fixed vs mobile station icons — parse APRS symbol table to show appropriate icons (EOC 🏛️, mobile 🚗, person 🧑, HT 📻)
  • APRS source selector — Settings toggle: Internet only, Local RF only, or Both (merged/deduped)

Phase 3 — Net Operations

  • Net check-in/check-out via APRS — APRSThursday-style messaging to EMCOMM (CQ/U commands)
  • Operator status board — roster panel showing checked-in operators, location, last heard, status, resources

Phase 4 — Messaging

  • Click-to-message from map — click any APRS station → compose and send APRS message via local daemon
  • Message thread view — per-callsign conversation history with delivery confirmation
  • Group messaging — broadcast to all net participants

Phase 5 — Logging & Documentation

  • Message log — all APRS messages stored with timestamps, searchable
  • Event log export — CSV/PDF download for After Action Reviews (AAR)
  • Resource history — track resource token changes over time (shelter capacity trends, etc.)

Phase 6 — Telemetry & Sensors (Future)

  • APRS telemetry parsing — temperature, battery, signal strength from T# frames
  • Custom sensor integration — IoT sensors via APRS (O2 tank levels, flood gauges, weather stations)
  • Token request protocol — field stations query current token definitions via APRS message

Architecture

Radio/TNC ←→ APRS Daemon (rig-bridge plugin) ←→ OpenHamClock ←→ APRS-IS (optional)

The local APRS daemon (Phase 2.1) is the critical path — everything else builds on it. If you have experience with Direwolf, KISS protocol, or APRS packet parsing, your contribution would be especially valuable.

Context

  • Original EmComm layout: shipped in v26.1.1
  • User feedback received 2026-03-24
  • Current status: Phase 1 (display-only) is complete and in production

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions