Repository navigation
Bug Fixes
Relay Node Tracking
- Missing relay nodes fixed: Relay observations were silently dropped when packets arrived before the DB finished loading candidates. Now creates placeholder entries for unknown relay bytes so no data is lost.
- Signal filter fallback: When all viable candidates were filtered out by RSSI signal matching, relay observations were discarded. Now falls back to any non-CLIENT_MUTE candidate.
- CLIENT_MUTE no longer hides relay rows: A CLIENT_MUTE node with high direct-packet score could become the "best" candidate for a relay byte, causing the entire row to be filtered out — even when a valid ROUTER candidate existed. Best candidate selection now excludes CLIENT_MUTE nodes.
- Detail dialog star fix: The winner star in the candidate detail dialog no longer goes to CLIENT_MUTE nodes. Non-muted candidates are sorted first, and the star is only awarded to the top non-muted candidate.
DB Role Parsing (from v0.4.0)
- Fixed protobuf enum name mismatch:
TAKnotATAK,TAK_TRACKERnotATAK_TRACKER - Added
ROUTER_LATEandCLIENT_BASEroles - CLIENT role (0) now stored so nodes show "Client" instead of "Unknown"
Full Changelog: v0.4.0...v0.4.1