Skip to content

v1.8.4 - Route Rendering Restore, Panel Minimization, and LOS Fresnel Guidance

Choose a tag to compare

@yellowcooln yellowcooln released this 17 Apr 19:15
· 49 commits to main since this release
5973579

This release restores route rendering on meshes affected by a regression introduced after v1.7.0, adds mobile-friendly panel minimization, and brings Fresnel-zone guidance into the LOS profile.

Routing Fix

  • Fixed the post-v1.7.0 regression where some networks stopped showing routes that had previously rendered in v1.6.6
  • The regression came from stricter handling of ambiguous 1-byte hop prefixes in decoded path hashes
  • By default, the map still handles colliding 1-byte prefixes conservatively to avoid incorrect hop guesses on larger meshes
  • Added a new environment variable: ROUTE_ALLOW_AMBIGUOUS_ONE_BYTE_FALLBACK
  • Default: false
  • When set to true, this restores the older pre-v1.7.0 closest/time-based fallback for ambiguous 1-byte hop prefixes
  • Use this if your mesh has valid routes that stopped rendering because multiple nodes share the same first-byte prefix and the conservative resolver is too strict for your network
  • This environment variable is documented in the docs, included in .env.example, and passed through docker-compose.yaml

New Features

  • Issue #55: LOS and Propagation panels can now be minimized without turning the tool off
  • Issue #55: the same minimize/expand control was extended to History, Peers, and Route Details so panels can get out of the way while the feature stays active
  • Issue #56: the LOS elevation profile now draws upper and lower Fresnel-zone lines, similar to the MeshCore app
  • Issue #56: LOS profile hover now shows Fresnel radius alongside terrain and LOS height
  • Fresnel rendering is segment-local for multi-pin LOS routes, so chained LOS paths do not get incorrect full-route Fresnel curves

Follow-up Fixes

  • Fixed the panel regression introduced during the new minimize-control work
  • History sliders continue to work
  • Peers opens correctly again
  • Route Details now clears when Show hops is turned off
  • LOS point selection works again
  • Propagation opens correctly again

Configuration

New environment variable in this release:

  • ROUTE_ALLOW_AMBIGUOUS_ONE_BYTE_FALLBACK=false

Purpose:

  • restores legacy route fallback for colliding 1-byte hop prefixes when needed

Recommended default:

  • keep it false unless your mesh specifically lost route rendering after the stricter prefix logic

Notes

  • Version metadata and release notes were updated for v1.8.4
  • The dev branch includes the route fix, the new panel controls, LOS Fresnel lines, and the follow-up regression fixes