Skip to content

Add repeater echo tracking to session ping logs#34

Merged
MrAlders0n merged 7 commits into
devfrom
copilot/add-session-ping-echo-tracker
Dec 18, 2025
Merged

Add repeater echo tracking to session ping logs#34
MrAlders0n merged 7 commits into
devfrom
copilot/add-session-ping-echo-tracker

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Dec 18, 2025

Session pings now capture which repeaters relay each message by listening to LogRxData events for 7 seconds post-ping, extracting repeater IDs and SNR values from packet paths.

Implementation

  • Added LogRxData event listener that parses GRP_TXT packets for repeater telemetry
  • Extracts repeater ID from first byte of packet path with validation (0-255, integer)
  • Tracks SNR values (-12 to +12 dB), keeping highest value for duplicate repeaters
  • Appends formatted repeater list to session log entry after 7-second collection window
  • Changed timestamp format to ISO 8601 without milliseconds

Example output

2025-12-18T14:32:45Z  47.79400  -3.42800  [25(-8),21(-5),14(3)]

Error handling

  • Packet parsing failures caught and logged without breaking listener
  • Input validation for SNR type and repeater ID range
  • Null checks prevent race conditions if tracking stops mid-collection
  • Cleanup on disconnect removes listeners and timers
Original prompt

This section details on the original issue you should resolve

<issue_title>[Feature]: Session Ping Echo Repeater Tracker</issue_title>
<issue_description>### What feature do you want?

Add the ability to track and display which repeaters receive and relay session ping messages. After each ping, continuously listen to the rx_log stream for 7 seconds to detect all echo responses from repeaters. Extract and log each repeater's ID and SNR, then append this repeater telemetry to the session ping output in the following format:

${nowStr} ${lat. toFixed(5)} ${lon.toFixed(5)} [RepeaterID-1(-SNR),RepeaterID-2(-SNR),...]

Example:

2025-12-18T14:32:45Z  47.79400  -3.42800  [25(-112),21(-109)]

Why do you need it?

This feature improves real-time situational awareness and network diagnostics by showing which repeaters actively received and relayed a ping. It helps users assess current repeater coverage, verify field network health, and troubleshoot link reliability.

How important is this?

Medium - Nice to have

Anything else?

No response</issue_description>

Comments on the Issue (you are @copilot in this section)

  • Fixes MrAlders0n/MeshCore-GOME-WarDriver#33

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Copilot AI and others added 6 commits December 18, 2025 03:39
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Copilot AI changed the title [WIP] Add session ping echo repeater tracker feature Add repeater echo tracking to session ping logs Dec 18, 2025
Copilot AI requested a review from MrAlders0n December 18, 2025 03:51
@MrAlders0n MrAlders0n marked this pull request as ready for review December 18, 2025 03:52
@MrAlders0n MrAlders0n merged commit 71c94a6 into dev Dec 18, 2025
@MrAlders0n MrAlders0n deleted the copilot/add-session-ping-echo-tracker branch December 18, 2025 11:36
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