Skip to content

Fix duplicate callsign in RX.DIRECTED TCP messages#123

Merged
wmiler merged 1 commit into
JS8Call-improved:masterfrom
mgochoa57:fix/tcp-duplicate-callsign
Jan 8, 2026
Merged

Fix duplicate callsign in RX.DIRECTED TCP messages#123
wmiler merged 1 commit into
JS8Call-improved:masterfrom
mgochoa57:fix/tcp-duplicate-callsign

Conversation

@mgochoa57

Copy link
Copy Markdown
Collaborator

Summary

Fixed bug where the callsign was duplicated in TCP output for RX.DIRECTED messages.

The Problem

The TEXT param in the RX.DIRECTED JSON message contained the full formatted string (which already includes the FROM callsign). When TCP clients reconstruct the display using FROM + ": " + TEXT, the callsign appears twice.

DIRECTED.txt (correct):
2025-12-06 16:07:27 14.078000 2025 -03 K9BTR: N0ASH HEARTBEAT SNR -19 ♢
2025-12-06 16:07:27 14.078000 2025 +06 WA3YWU: N0ASH HEARTBEAT SNR -06 ♢

TCP output (buggy):
2025-12-06 16:07:27 14.078000 2025 -03 K9BTR: K9BTR: N0ASH HEARTBEAT SNR -19 ♢
2025-12-06 16:07:27 14.078000 2025 +06 WA3YWU: WA3YWU: N0ASH HEARTBEAT SNR -06 ♢

The Fix

Changed TEXT param from "text" (full formatted message) to "d.text" (message body only).

  TEXT param contained the full formatted message including FROM prefix,
  causing duplication when clients reconstruct the message. Changed to
  use d.text (message body) instead.
@wmiler wmiler merged commit 09281f7 into JS8Call-improved:master Jan 8, 2026
@mgochoa57 mgochoa57 deleted the fix/tcp-duplicate-callsign branch January 29, 2026 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants