Skip to content

fix: allow TRACE packets to reach engine for MQTT/LetsMesh publishing #171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dmduran12 wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

fix: allow TRACE packets to reach engine for MQTT/LetsMesh publishing #171

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions repeater/packet_router.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -164,11 +164,15 @@ async def _route_packet(self, packet):

# Route to specific handlers for parsing only
if payload_type == TraceHandler.payload_type():
# Process trace packet
# Process trace packet for local display (terminal RTT/SNR)
if self.daemon.trace_helper:
await self.daemon.trace_helper.process_trace_packet(packet)
# Skip engine processing for trace packets - they're handled by trace helper
processed_by_injection = True
# Allow the engine to record + publish this packet to MQTT/LetsMesh.
# mark_do_not_retransmit prevents RF re-broadcast (same pattern as
# ControlHandler at line 180). The trace request and response have
# different packet hashes, so the response won't be flagged as a
# duplicate of the request by the engine's seen-cache.
packet.mark_do_not_retransmit()
# Do not call _record_for_ui: TraceHelper.log_trace_record already persists the
# trace path from the payload. record_packet_only would treat packet.path (SNR bytes)
# as routing hashes and log bogus duplicate rows.
Expand Down