v1.6.5 - Role Accuracy, Version Logging, and Multibyte Hash Fixes
This release improves device role detection accuracy, makes it easier to verify the running version, and fixes low-range multibyte route hash handling.
Changes
- Made MQTT role detection strict for accuracy
- Roles are now assigned only from explicit role fields and numeric MeshCore role codes
- Removed weak role guessing from names, model strings, origin text, and descriptions
- Added runtime version logging
- Server startup logs now print the running map version
- Browser console now prints the running map version
- Version is sourced from
VERSION.txt
- Fixed backend route hash normalization to respect decoder
pathLength- Preserves low-range 2-byte IDs like
00AB - Preserves low-range 3-byte IDs like
0000AB - Prevents these values from collapsing to shorter prefixes and failing route lookup
- Preserves low-range 2-byte IDs like
Why this release
Some nodes were being mislabeled due to weak MQTT metadata, and low-range multibyte repeater IDs could silently fail route resolution #26 . This release makes role detection more reliable and fixes width-aware route hash handling for multibyte paths.
Testing
- Added regression tests for:
- Strict role detection
- Version injection into the frontend
- Low-range 2-byte and 3-byte route hash padding
- Full test suite passing:
55 passed