Skip to content

v1.6.1 - Multibyte Decoder Migration and Routing Compatibility

Choose a tag to compare

View all tags
@yellowcooln yellowcooln released this 11 Mar 15:32
· 99 commits to main since this release
v1.6.1
3289aad
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v1.6.1

This release updates the map to use a patched MeshCore decoder with multibyte repeater-prefix support, preparing the app for upcoming 2-byte and 3-byte routing changes.

Highlights

  • Replaced the official @michaelhart/meshcore-decoder package with meshcore-decoder-multibyte-patch
  • Added route prefix support for:
    • 1-byte prefixes: AB
    • 2-byte prefixes: ABCD
    • 3-byte prefixes: ABCDEF
  • Updated route normalization and matching so mixed-width paths can be resolved in the same network
  • Expanded route tests to cover mixed 1/2/3-byte path handling and exact-prefix matching

Why this release

MeshCore is moving toward multibyte repeater prefixes. The previous official decoder was a blocker for that rollout.
This release switches the map to a patched decoder that can ingest and decode those path formats now.

Current support status

  • Multibyte path ingest is working in development
  • Live path strings with 1-byte, 2-byte, and 3-byte segments have been observed during testing
  • The app is intended to be ready for upcoming multibyte repeater rollouts
  • Not tested in a mixed-network environment. I am currently unable to test this in my mesh. Please open an Issue if you encounter any problems related to this feature.

Notes

  • Show Hops now documents and expects plain prefix display such as AB, ABCD, and ABCDEF
  • This release focuses on decoder and routing compatibility and does not introduce UI features
Assets 2
Loading