2 Commits (dev)

Author	SHA1	Message	Date
Strycher	8920cf928f	feat(#439): read per-message RSSI from reserved2 and show it on the Path screen ... Firmware #465 now writes RX RSSI into reserved2 (byte[3]) of the v3 contact-msg-recv frame as a clamped int8 dBm, 0 when unset (MyMesh.cpp:550-551). Read it in the parse instead of skipping: gate on != 0 (RSSI is always negative for a real RX, so 0 = no data), null for device-composed outgoing messages. reserved1 (byte[2]) is untouched — that's #429's outgoing flag; RSSI lives in byte[3] after the res1/res2 collision fix (#464/#465). The Message.rssi field, persistence, param-passing, and the (hidden- while-null) RSSI row on the Packet Path screen were all staged in #438, so this is just the wire read + 3 gate tests. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2 months ago
Strycher	f935a48ef0	feat(#438): show path type + SNR on the message Path screen ... Tapping a DM opens the Path screen; it now shows the RF details the app was already receiving but discarding: - SNR: captured from the v3 contact-msg-recv frame (was skipBytes(1)). Firmware sends (int8)(snr_dB*4), so dB = byte/4.0 (MyMesh.cpp:512) — the old commented-out code multiplied by 4, which was 16x wrong. - Path type: firmware sends path_len 0xFF for a direct/routed frame and the hop count for a flood (MyMesh.cpp:545). The app collapsed 0xFF->0, colliding "direct" with "flood, 0 hops". Capture the distinction into Message.isFloodRoute so the Path row reads "direct (routed)" vs "flood, N hops". - RSSI: row wired to Message.rssi but left null — the wire byte is a hardcoded reserved 0 today; populated once firmware ships it (#439). Message gains snr/rssi/isFloodRoute (nullable, additive, persisted like rxTime). 10 tests cover scaling, the 0xFF discriminator, and copyWith. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2 months ago