Summary

Multiple bugs in position history rendering and interaction, confirmed on v4.11.6.

Bug 1: Position history points vanish when tail duration exceeds ~2 days

Steps to reproduce:

1. Enable Position History on the map
2. Set tail (position history time) to 1d 17h — points render correctly as dots on the line
3. Increase tail to 2d 3h — individual points disappear; only line segments remain

Expected: All recorded position points render as dots regardless of tail duration
Actual: Points go missing above a certain tail threshold (~2 days); line segments still draw but point markers are dropped

Screenshots attached — image 2 (1d 17h, points visible) vs image 3 (2d 3h, points gone).

Bug 2: Hover and click on position history points non-functional

Steps to reproduce:

1. Enable Position History
2. Mouse-over a position history point — no tooltip appears
3. Click a position history point — no popup appears

Expected: Hover shows timestamp/hops/SNR; click shows point detail
Actual: No interaction response on individual points

(Clicking a line segment does open a popup, so click handling on the line works but not on points.)

Bug 3: Incorrect velocity in position segment popups

Steps to reproduce:

1. Enable Position History
2. Click on a position history line segment

Expected: Velocity reflects actual movement between the two position reports
Actual: Velocity shows physically implausible values (e.g. 90 km/h, 94 km/h, 125.9 km/h) for a node that is stationary or moving slowly

Screenshot attached showing segment popup with 125.9 km/h.

Bug 4: SNR not shown for directly-heard nodes (0 hops)

Steps to reproduce:

1. Request position from a node that replies directly (0 hops)
2. View the node on the map / position history

Expected: SNR is displayed when a node is heard directly (0 hops); packet monitor confirms SNR data is present in the packet
Actual: Hop count shows 0 (correct) but SNR field is blank/missing

Confirmed on v4.11.0 and v4.11.6. Both position-request replies and normal position packets omit SNR. Receiving node firmware: 2.7.25.

Environment

• MeshMonitor version: 4.11.6
• Meshtastic firmware: 2.7.25

Authored by NodeZero 0️⃣