Packet Feed Analyzer #93

New Issue

2026-10-05T01:56:52+02:00

adam commented

2026-10-05 01:56:52 +02:00

I'm pretty sure this 'best RSSI' is based on the RSSI of the 'last hop' and not attached to the actual transmit origin as it keeps changing based on origin and not showing based on RF source. AKA it's the reported RSSI of my nearest repeater, but the associated name is the packet originator making it seem like their signal is the best RSSI into my companion.

How to fix: associate 'best RSSI' based on direct-received adverts only or use 'last hop' association to identify the node the station is actually hearing best.

I'm pretty sure this 'best RSSI' is based on the RSSI of the 'last hop' and not attached to the actual transmit origin as it keeps changing based on origin and not showing based on RF source. AKA it's the reported RSSI of my nearest repeater, but the associated name is the packet originator making it seem like their signal is the best RSSI into my companion. How to fix: associate 'best RSSI' based on direct-received adverts only or use 'last hop' association to identify the node the station is actually hearing best. <img width="538" height="630" alt="Image" src="https://github.com/user-attachments/assets/b0ad62e2-2e5c-4720-a949-4e3b7ea55516" />

adam closed this issue

2026-10-05 01:56:52 +02:00

adam commented

2026-10-05 01:56:53 +02:00

Good call-out.

Good call-out.

adam commented

2026-10-05 01:56:54 +02:00

Phrased more clearly .

Phrased more clearly . <img width="379" height="114" alt="Image" src="https://github.com/user-attachments/assets/fce41f86-908d-4164-84de-dad3c7e04357" />

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#93