Summary

• _onPositionReceive() now checks precisionBits before updating the local node's position
• Prevents low-precision map report echoes from overwriting the local GPS position
• Remote node positions are still updated normally (any broadcast from them reflects their current state)

Problem

When other nodes relay our position via map reports at reduced precision (e.g., precisionBits: 13), the library blindly overwrites our locally-stored high-precision GPS position (precisionBits: 32). This causes:

• Local node position jumping to a nearby but incorrect location
• Multiple nodes appearing at the same truncated coordinates
• Position accuracy degrading from ~1m to ~1km after 10-15 seconds of mesh traffic

This only affects the local node — since we have the GPS internally, any lower-precision update is always an echo from the mesh, never fresh data. Remote nodes legitimately send their own positions at whatever precision their GPS provides, so those updates should always be accepted.

Fix

Added a check in _onPositionReceive() that detects if the position update is for the local node (by comparing asDict["from"] to iface.myInfo.my_node_num). For the local node only, it compares precisionBits and rejects updates with lower precision. Remote node positions continue to be updated unconditionally.

Test plan

• Connect to a Meshtastic device with GPS via the Python library
• Read local node position immediately after connection (should be high precision, e.g., 32 bits)
• Wait for mesh traffic with low-precision map report echoes
• Verify local node position is NOT overwritten by lower-precision echo
• Verify remote node positions ARE still updated normally (including lower-precision updates)

Fixes #910

🤖 Generated with Claude Code