Skip to content

🚀 MeshMapper Update (March 8, 2026)

Expect Bugs

This release includes significant changes to how MeshMapper handles repeater identification across the entire solution — from data ingestion to map rendering. While extensively tested, edge cases are likely. If you encounter any issues, please report them.

🌐 Server & Map

✨ New Features

  • Dynamic Hop Bytes Support — The MeshMapper backend and map now fully support 1, 2, and 3-byte repeater hop identification across all features. This requires repeaters and companions running firmware v1.14.0 or newer.

    • Collision detection, coverage mapping, leaderboards, all use the hop byte length
    • The region's Hop Bytes setting is configurable in the region admin panel under Settings

  • Per-Repeater Hop Byte Tracking — MeshMapper now tracks hop bytes on a per-repeater basis. When a repeater is heard with a longer ID than previously seen, its hop bytes value is automatically updated. This allows regions to transition gradually from 1-byte to multi-byte firmware.

Image

  • Smart Collision Detection — Collision detection now uses per-repeater hop bytes to determine if two repeaters are truly in conflict. Two repeaters are only considered colliding if they are indistinguishable at the longer of their two hop byte lengths. For example, AB (1-byte) and AB12 (2-byte) are no longer flagged as duplicates.

  • Hop Bytes Advanced Filter — A new "Hop Bytes" dropdown has been added to the advanced search panel on the map, allowing users to filter repeater markers by their hop byte value (1, 2, or 3).

Image

  • Repeater List Grid Update — The Repeater List grid in Region Info now filters out multi-byte repeaters from 1-byte cells to avoid false "taken" indicators. New 1-byte, 2-byte, and 3-byte repeater lists are available to help regions in coordinating firmware upgrades.

Image