Some FT8/Q65 multi-decoder spots omit sender/receiver callsigns from the JSON payload, but the MQTT topic routing path always carries them in positions 5 (sc) and 6 (rc): pskr/filter/v2/<band>/<mode>/<sc>/<rc>/<sl>/<rl>/<sa>/<ra> Client now extracts callsigns from the topic and threads them through Aggregator.ingest → Pskr.parse_spot, where they act as fallback when the JSON sc/rc keys are nil or empty. JSON payload values still take precedence when present — the topic is only used as a safety net. Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| fixtures | ||
| microwaveprop | ||
| microwaveprop_web | ||
| mix/tasks | ||
| support | ||
| test_helper.exs | ||