This release focuses on security hardening and dependency maintenance.
\nfastapi==0.136.3uvicorn[standard]==0.49.0httpx==0.28.1httpx2==2.3.0 for dev tests so FastAPI/Starlette TestClient runs without the deprecated-httpx warning.98 passed, 2 skippedFull Changelog: https://github.com/yellowcooln/meshcore-mqtt-live-map/compare/v1.9.2...v.1.9.3
\n" }, { "version": "v1.9.2", "name": "v1.9.2 - Route History Fixes, LOS Coordinates, and Peers Panel Cleanup", "datetime": "2026-05-28T02:14:45Z", "url": "https://github.com/yellowcooln/meshcore-mqtt-live-map/releases/tag/v1.9.2", "prerelease": false, "notes": "## v1.9.2 - Route History Fixes, LOS Coordinates, and Peers Panel Cleanup\r\n\r\n### Highlights\r\n\r\nThis release fixes Route History disable behavior, improves LOS point entry, and cleans up the Peers panel with feedback from the community.\r\n\r\n---\r\n\r\n### Added\r\n\r\n* Added direct latitude/longitude entry to the LOS panel\r\n Related: #71\r\n\r\n* Added per-pin LOS height input for above-ground-level values\r\n Related: #71\r\n\r\n* Added `PEERS_DEFAULT_OPEN=false` so admins can choose whether the Peers tool starts active on page load\r\n Related: #72\r\n\r\n* Added a MQTT-only filter beside the MQTT online legend item\r\n\r\n * Shows only MQTT-online nodes\r\n * Hides:\r\n\r\n * Non-MQTT markers\r\n * Trails\r\n * Routes\r\n * Hop markers\r\n * Route details\r\n * Peer lines\r\n * Does not save to browser storage\r\n * Is not included in share links\r\n\r\n---\r\n\r\n### Changed\r\n\r\n* Improved LOS point editing so pins can be:\r\n\r\n * Added\r\n * Selected\r\n * Dragged\r\n * Updated directly from the coordinate editor\r\n Related: #71\r\n\r\n* Kept LOS and Propagation as separate tools so obstruction checks and RF coverage planning remain independent workflows\r\n Related: #71\r\n\r\n* Reworked the Peers panel layout based on ideas and testing from Stormlove / @beachmiles\r\n Related: #72\r\n\r\n* Moved **Clear peers** into the Peers panel header beside **Minimize**\r\n Related: #72\r\n\r\n* Updated the Peers panel title to use the selected node name, with the 24h window displayed underneath\r\n Related: #72\r\n\r\n* Updated Incoming/Outgoing headings to display:\r\n\r\n * Rx/Tx packet totals\r\n * Unique peer counts\r\n * Blue/purple line hints\r\n\r\n* Updated peer row stats to display:\r\n\r\n * Count\r\n * Percent\r\n * Distance\r\n\r\n* Tuned Peers panel scrolling so long peer lists scroll inside capped Incoming/Outgoing sections instead of forcing the full panel height on mobile\r\n Related: #72\r\n\r\n---\r\n\r\n### Fixed\r\n\r\n* Fixed Docker Compose deployments not passing Route History environment variables into the container\r\n Related: #68\r\n\r\n* Fixed `ROUTE_HISTORY_ENABLED=false` so it now fully disables:\r\n\r\n * History button\r\n * History panel\r\n * `/snapshot` history payloads\r\n * WebSocket history payloads\r\n * Route-history file growth from live traffic\r\n\r\n* Fixed Peers counts going empty when Route History was disabled and older history buckets expired\r\n Related: #68\r\n\r\n* Peers now use dedicated rolling peer-history buckets, so peer counts continue updating from live routes even when Route History is disabled\r\n Related: #68\r\n\r\n---\r\n\r\n### Credits\r\n\r\nThanks to Stormlove / @beachmiles for the Peers panel cleanup ideas, testing, and follow-up feedback in #72.\r\n\r\n## What's Changed\r\n* fix route history env passthrough by @yellowcooln in https://github.com/yellowcooln/meshcore-mqtt-live-map/pull/70\r\n* Enhance peers panel and fix related issues in v1.9.2 by @yellowcooln in https://github.com/yellowcooln/meshcore-mqtt-live-map/pull/73\r\n\r\n\r\n**Full Changelog**: https://github.com/yellowcooln/meshcore-mqtt-live-map/compare/v1.9.1...v1.9.2", "notesHtml": "This release fixes Route History disable behavior, improves LOS point entry, and cleans up the Peers panel with feedback from the community.
\nAdded direct latitude/longitude entry to the LOS panel\nRelated: #71
\nAdded per-pin LOS height input for above-ground-level values\nRelated: #71
\nAdded PEERS_DEFAULT_OPEN=false so admins can choose whether the Peers tool starts active on page load\nRelated: #72
Added a MQTT-only filter beside the MQTT online legend item
\nShows only MQTT-online nodes
\nHides:
\nDoes not save to browser storage
\nIs not included in share links
\nImproved LOS point editing so pins can be:
\nKept LOS and Propagation as separate tools so obstruction checks and RF coverage planning remain independent workflows\nRelated: #71
\nReworked the Peers panel layout based on ideas and testing from Stormlove / @beachmiles\nRelated: #72
\nMoved Clear peers into the Peers panel header beside Minimize\nRelated: #72
\nUpdated the Peers panel title to use the selected node name, with the 24h window displayed underneath\nRelated: #72
\nUpdated Incoming/Outgoing headings to display:
\nUpdated peer row stats to display:
\nTuned Peers panel scrolling so long peer lists scroll inside capped Incoming/Outgoing sections instead of forcing the full panel height on mobile\nRelated: #72
\nFixed Docker Compose deployments not passing Route History environment variables into the container\nRelated: #68
\nFixed ROUTE_HISTORY_ENABLED=false so it now fully disables:
/snapshot history payloadsFixed Peers counts going empty when Route History was disabled and older history buckets expired\nRelated: #68
\nPeers now use dedicated rolling peer-history buckets, so peer counts continue updating from live routes even when Route History is disabled\nRelated: #68
\nThanks to Stormlove / @beachmiles for the Peers panel cleanup ideas, testing, and follow-up feedback in #72.
\nFull Changelog: https://github.com/yellowcooln/meshcore-mqtt-live-map/compare/v1.9.1...v1.9.2
\n" }, { "version": "v1.9.1", "name": "v1.9.1 - Full Route History Disable Support", "datetime": "2026-05-08T19:15:07Z", "url": "https://github.com/yellowcooln/meshcore-mqtt-live-map/releases/tag/v1.9.1", "prerelease": false, "notes": "### Fixed\r\n\r\n* Fixed issue #68: `ROUTE_HISTORY_ENABLED=false` now disables Route History end-to-end instead of only stopping new history recording\r\n* When Route History is disabled:\r\n\r\n * The History tool button is removed\r\n * The History panel does not load\r\n * `history=on` in the URL no longer re-enables the feature\r\n * `/snapshot` no longer returns `history_edges` or a nonzero history window\r\n * The realtime WebSocket snapshot no longer publishes history payloads\r\n\r\n---\r\n\r\n### Behavior Change\r\n\r\n`ROUTE_HISTORY_ENABLED` now behaves as a true feature flag for both:\r\n\r\n* Backend history payloads\r\n* Frontend History tool/UI\r\n\r\nThis makes it practical to disable Route History entirely on:\r\n\r\n* High-volume meshes\r\n* Lower-resource deployments\r\n\r\n---\r\n\r\n### Config\r\n\r\nUse:\r\n\r\n`ROUTE_HISTORY_ENABLED=false`\r\n\r\nThis now fully disables:\r\n\r\n* History tool UI\r\n* History snapshot payloads\r\n* History panel activation\r\n* Hidden frontend history state\r\n\r\n---\r\n\r\n### Validation\r\n\r\n* `pytest -q tests/test_api_auth.py tests/test_websocket_snapshot.py`\r\n\r\n * `13 passed`\r\n* `node --check backend/static/app.js`\r\n* `python3 -m py_compile backend/*.py`\r\n\r\n## What's Changed\r\n* v1.9.1 disable route history end-to-end by @yellowcooln in https://github.com/yellowcooln/meshcore-mqtt-live-map/pull/69\r\n\r\n\r\n**Full Changelog**: https://github.com/yellowcooln/meshcore-mqtt-live-map/compare/v1.9.0...v1.9.1", "notesHtml": "Fixed issue #68: ROUTE_HISTORY_ENABLED=false now disables Route History end-to-end instead of only stopping new history recording
When Route History is disabled:
\nhistory=on in the URL no longer re-enables the feature/snapshot no longer returns history_edges or a nonzero history windowROUTE_HISTORY_ENABLED now behaves as a true feature flag for both:
This makes it practical to disable Route History entirely on:
\nUse:
\nROUTE_HISTORY_ENABLED=false
This now fully disables:
\npytest -q tests/test_api_auth.py tests/test_websocket_snapshot.py
13 passednode --check backend/static/app.js
python3 -m py_compile backend/*.py
Full Changelog: https://github.com/yellowcooln/meshcore-mqtt-live-map/compare/v1.9.0...v1.9.1
\n" }, { "version": "v1.9.0", "name": "v1.9.0 - Subpath Hosting, Direct Node Links, and Peer Distances", "datetime": "2026-05-06T18:15:56Z", "url": "https://github.com/yellowcooln/meshcore-mqtt-live-map/releases/tag/v1.9.0", "prerelease": false, "notes": "This release adds proper subpath hosting support and improves node sharing and peer visibility.\r\n\r\n---\r\n\r\n## Subpath Hosting\r\n\r\nAdded `APP_BASE_PATH`, allowing the map to be hosted from a subpath such as:\r\n\r\n`/livemap`\r\n\r\ninstead of only from `/`.\r\n\r\nThis work originated from:\r\n\r\n* PR #65 by @chrisdavis2110\r\n\r\n#### Covered Areas\r\n\r\n* App shell URLs\r\n* Static asset URLs\r\n* WebSocket path\r\n* Service worker registration and scope\r\n* Manifest URL, `start_url`, and scope\r\n* Turnstile verification flow\r\n* Auth cookie path\r\n* Preview/share image URLs\r\n\r\nThis release also includes follow-up fixes so preview and Open Graph image URLs work correctly when using both:\r\n\r\n* `APP_BASE_PATH`\r\n* Public site URLs\r\n\r\n---\r\n\r\n## Direct Node Links and Peer Distances\r\n\r\nThis work originated from:\r\n\r\n* PR #66 by @mitchellmoss\r\n\r\nNode popups now include direct map-link actions:\r\n\r\n* Copy node link\r\n* Copy repeater link\r\n\r\nThe generated links preserve current map state plus a target device.\r\n\r\nOpening a shared link now:\r\n\r\n* Automatically enables node visibility if hidden\r\n* Focuses the target device\r\n* Zooms to it\r\n* Opens its popup\r\n\r\n#### Supported Link Parameters\r\n\r\n* `node`\r\n* `repeater`\r\n* `device`\r\n* `device_id`\r\n* `public_key`\r\n* `pubkey`\r\n\r\n\r\nThe Peers tool now shows distance when both endpoints have coordinates.\r\n\r\n### Backend\r\n\r\n* `/peers/{device_id}` now includes:\r\n\r\n * `distance_m`\r\n\r\n### Frontend\r\n\r\n* Renders peer distance using the currently selected unit system:\r\n\r\n * Kilometers\r\n * Miles\r\n\r\n\r\n---\r\n\r\n## Compatibility\r\n\r\nFor normal root-hosted installs:\r\n\r\n* No configuration changes required\r\n* Existing `/` deployments behave the same\r\n* `APP_BASE_PATH` remains dormant unless explicitly configured\r\n\r\n---\r\n\r\n## What's Changed\r\n* feat: APP_BASE_PATH config to set app as subpath by @chrisdavis2110 in https://github.com/yellowcooln/meshcore-mqtt-live-map/pull/65\r\n* [codex] Add direct node links and peer distances by @mitchellmoss in https://github.com/yellowcooln/meshcore-mqtt-live-map/pull/66\r\n\r\n\r\n**Full Changelog**: https://github.com/yellowcooln/meshcore-mqtt-live-map/compare/v1.8.6...v1.9.0", "notesHtml": "This release adds proper subpath hosting support and improves node sharing and peer visibility.
\nAdded APP_BASE_PATH, allowing the map to be hosted from a subpath such as:
/livemap
instead of only from /.
This work originated from:
\nstart_url, and scopeThis release also includes follow-up fixes so preview and Open Graph image URLs work correctly when using both:
\nAPP_BASE_PATHThis work originated from:
\nNode popups now include direct map-link actions:
\nThe generated links preserve current map state plus a target device.
\nOpening a shared link now:
\nnoderepeaterdevicedevice_idpublic_keypubkeyThe Peers tool now shows distance when both endpoints have coordinates.
\n/peers/{device_id} now includes:
distance_mRenders peer distance using the currently selected unit system:
\nFor normal root-hosted installs:
\n/ deployments behave the sameAPP_BASE_PATH remains dormant unless explicitly configuredFull Changelog: https://github.com/yellowcooln/meshcore-mqtt-live-map/compare/v1.8.6...v1.9.0
\n" }, { "version": "v1.8.6", "name": "v1.8.6 - Route Filtering + Containerized Deployment (Multi-Arch)", "datetime": "2026-05-02T17:56:35Z", "url": "https://github.com/yellowcooln/meshcore-mqtt-live-map/releases/tag/v1.8.6", "prerelease": false, "notes": "This release combines the unreleased v1.8.5 container/deployment work with the new v1.8.6 route filtering feature.\r\n\r\n### Container and Deployment\r\n\r\n* Published image:\r\n\r\n * `yellowcooln/meshcore-mqtt-live-map`\r\n* Multi-arch image support:\r\n\r\n * `linux/amd64`\r\n * `linux/arm64`\r\n* Added image-based deployment examples (no local build required):\r\n\r\n * `deploy/docker-compose.image.yaml`\r\n * `deploy/swarm-stack.yaml`\r\n * `deploy/kubernetes-meshmap.yaml`\r\n* Adjusted Docker publish workflow:\r\n\r\n * Docs-only changes no longer trigger rebuild/publish\r\n * Image-relevant changes still trigger builds\r\n\r\n### New Route Filtering\r\n\r\n* Added issue #59: Path bytes filter in the HUD\r\n* Routes can now be filtered by decoded path-hash width:\r\n\r\n * All\r\n * 1-byte\r\n * 2-byte\r\n * 3-byte\r\n* Filter applies consistently to:\r\n\r\n * Route lines\r\n * Hop markers\r\n * Route Details\r\n * HUD route counts\r\n* Mixed-width paths remain visible if at least one hop matches the selected width\r\n* Share links now include:\r\n\r\n * `route_bytes=all|1b|2b|3b`\r\n\r\n### Route Filter Stability Fixes\r\n\r\n* Fixed route redraw behavior so switching byte filters does not stack stale path lines\r\n* Default page loads now reset to **All** unless `route_bytes` is explicitly present in the URL\r\n\r\n * Prevents stale browser state from hiding routes unexpectedly\r\n\r\n### Notes\r\n\r\n* Version metadata and documentation updated for v1.8.6\r\n* This release includes:\r\n\r\n * v1.8.5 container/deployment work\r\n * v1.8.6 path-byte route filtering", "notesHtml": "This release combines the unreleased v1.8.5 container/deployment work with the new v1.8.6 route filtering feature.
\nPublished image:
\nyellowcooln/meshcore-mqtt-live-mapMulti-arch image support:
\nlinux/amd64linux/arm64Added image-based deployment examples (no local build required):
\ndeploy/docker-compose.image.yamldeploy/swarm-stack.yamldeploy/kubernetes-meshmap.yamlAdjusted Docker publish workflow:
\nAdded issue #59: Path bytes filter in the HUD
\nRoutes can now be filtered by decoded path-hash width:
\nFilter applies consistently to:
\nMixed-width paths remain visible if at least one hop matches the selected width
\nShare links now include:
\nroute_bytes=all|1b|2b|3bFixed route redraw behavior so switching byte filters does not stack stale path lines
\nDefault page loads now reset to All unless route_bytes is explicitly present in the URL
Version metadata and documentation updated for v1.8.6
\nThis release includes:
\nThis 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.
v1.7.0 regression where some networks stopped showing routes that had previously rendered in v1.6.6ROUTE_ALLOW_AMBIGUOUS_ONE_BYTE_FALLBACKfalsetrue, this restores the older pre-v1.7.0 closest/time-based fallback for ambiguous 1-byte hop prefixes.env.example, and passed through docker-compose.yamlNew environment variable in this release:
\nROUTE_ALLOW_AMBIGUOUS_ONE_BYTE_FALLBACK=falsePurpose:
\nRecommended default:
\nfalse unless your mesh specifically lost route rendering after the stricter prefix logicv1.8.4dev branch includes the route fix, the new panel controls, LOS Fresnel lines, and the follow-up regression fixesThis release fixes the LOS tool so it no longer ignores Earth curvature, and it cleans up the related configuration and documentation.
\n/los fallback so live interaction and server responses stay consistentLOS_CURVATURE_ENABLEDLOS_CURVATURE_FACTORDefaults when unset:
\nLOS_CURVATURE_ENABLED=trueLOS_CURVATURE_FACTOR=1.333333docker-compose.yaml so all LOS-related environment variables are actually passed into the container:LOS_ELEVATION_URLLOS_ELEVATION_PROXY_URLLOS_SAMPLE_MINLOS_SAMPLE_MAXLOS_SAMPLE_STEP_METERSELEVATION_CACHE_TTLLOS_CURVATURE_ENABLEDLOS_CURVATURE_FACTORLOS_PEAKS_MAX.env.example with the new LOS curvature environment variablesmeshcore-mqtt-broker: the live map normally uses a broker SUBSCRIBER_N username/password pair, not node-style signed publisher authv1.8.3pytest -q → 92 passed, 2 skippednode --check backend/static/app.jspython3 -m py_compile backend/*.pyThis release adds node QR and contact sharing support, and fixes several map behavior issues.
\nQR_CODE_BUTTON_ENABLED=true to show a Generate QR Code action/qr PNG generation with existing prod-token protection/peers/{device_id} still reflects adjacency from route point_ids even when a hop cannot be drawn on the mapThis release resolves the current open issue set and improves live route visualization.
\n/peers/{device_id}?limit= now accepts any positive value/waka or /arcade in the search box and pressing EnterThis release adds automatic backups, expands the LOS tool into a chained path workflow, restores the official MeshCore decoder, and improves MeshMapper coverage behavior.
\n.tar.gz archives@michaelhart/meshcore-decoder84 passed, 2 skippedAutomatic runtime backups are now supported as timestamped .tar.gz archives. This release also adds backup-specific environment controls, changes the default backup location to /backup, adds retention pruning for older archives, and mounts ./backup:/backup in docker-compose.yaml.
Backups include live-state files such as:
\nstate.jsondevice_roles.jsondevice_coords.jsonneighbor_overrides.jsonchannel_secrets.jsonmap_boundary.jsonroute_history.jsonlcoverage_cache.jsonNew backup environment variables:
\nBACKUP_ENABLEDBACKUP_INTERVAL_SECONDSBACKUP_DIRBACKUP_RETENTION_DAYSThe LOS tool now supports multiple chained pins as part of issue #41. Elevation profiles span the full chained path instead of only the active segment, height inputs are stored per pin, and intermediate pin movement now correctly recalculates both adjacent segments.
\nThis release also removes the old Keep A LOS workflow, adds Remove last pin, and updates helper text and labels to match the chained-pin model.
The runtime decoder has been switched back to the official @michaelhart/meshcore-decoder, which now supports the multibyte path decoding needed by the map.
MeshMapper coverage rendering now expands returned squares to better match MeshMapper’s displayed footprint. Styling was also tuned to keep the fuller footprint while making coverage easier to read.
\n" }, { "version": "v1.7.8.1", "name": "v1.7.8.1 - Peers Clear Fix", "datetime": "2026-03-25T00:11:46Z", "url": "https://github.com/yellowcooln/meshcore-mqtt-live-map/releases/tag/v1.7.8.1", "prerelease": false, "notes": "## v1.7.8.1\r\n\r\n This release fixes issue #38 in the Peers tool.\r\n\r\n### Changes\r\n- Fixed issue #38: the `Clear peers` action now removes both incoming and outgoing peer lines even when the same peer appears in both directions\r\n\r\n### Why this release\r\nThe Peers tool tracked lines by peer ID only. When the same peer appeared in both incoming and outgoing lists, one line could overwrite the other in the internal line map, so clearing peers did not remove everything.", "notesHtml": "This release fixes issue #38 in the Peers tool.
\nClear peers action now removes both incoming and outgoing peer lines even when the same peer appears in both directionsThe Peers tool tracked lines by peer ID only. When the same peer appeared in both incoming and outgoing lists, one line could overwrite the other in the internal line map, so clearing peers did not remove everything.
\n" }, { "version": "v1.7.8", "name": "v1.7.8 - MeshMapper Coverage Legend and Browser Performance Improvements", "datetime": "2026-03-24T19:42:25Z", "url": "https://github.com/yellowcooln/meshcore-mqtt-live-map/releases/tag/v1.7.8", "prerelease": false, "notes": "## v1.7.8\r\n\r\nThis release improves MeshMapper coverage presentation and reduces browser rendering overhead, especially on larger maps and mobile devices.\r\n\r\n### Changes\r\n\r\n- Adjusted MeshMapper coverage rendering to better match the native MeshMapper look:\r\n - Removed visible square borders\r\n - Increased fill density for a more solid coverage blob\r\n- Added a MeshMapper coverage legend in the HUD:\r\n - Shown only when Coverage is enabled and the active provider is MeshMapper\r\n - Includes:\r\n - `BIDIR`\r\n - `DISC / TRACE`\r\n - `TX`\r\n - `RX`\r\n - `DEAD`\r\n - `DROP`\r\n- Improved browser-side rendering performance:\r\n - Enabled Leaflet canvas-backed rendering where it does not change visible behavior\r\n - Kept animated route and trail lines on SVG so existing visual motion remains unchanged\r\n - Added viewport culling for off-screen nodes and coverage tiles\r\n - Batched realtime WebSocket updates using `requestAnimationFrame`\r\n - Batched stats updates to avoid repeated recalculation during burst traffic\r\n\r\n### Notes\r\n\r\n- These performance changes are browser-side only and do not increase server load\r\n- MeshMapper rendering changes apply only when the Coverage provider is MeshMapper\r\n- Legacy coverage rendering remains unchanged\r\n\r\n### Docs\r\n\r\n- Clarified that `MQTT_TOPIC` supports comma-separated values for subscribing to multiple topic trees, for example:\r\n - `meshcore/BOS/#,meshcore/CON/#`", "notesHtml": "This release improves MeshMapper coverage presentation and reduces browser rendering overhead, especially on larger maps and mobile devices.
\nBIDIRDISC / TRACETXRXDEADDROPrequestAnimationFrameMQTT_TOPIC supports comma-separated values for subscribing to multiple topic trees, for example:meshcore/BOS/#,meshcore/CON/#This release adds optional polygon-based map boundaries while keeping the existing radius filter as the default.
\nAdded MAP_BOUNDARY_MODE with support for:
radius (default)polygonAdded MAP_BOUNDARY_FILE for loading polygon boundary JSON
Added MAP_BOUNDARY_SHOW to control boundary overlay visibility
Polygon boundaries now apply consistently to:
\nAdded frontend polygon overlay rendering from backend-injected boundary JSON
\nAdded map_boundary.example.json as the reference schema
Added a standalone boundary builder:
\ntools/map-boundary-builder.htmlAdded hosted boundary builder:
\n\n{\n \"name\": \"Example Boundary\",\n \"points\": [\n [42.4705, -71.2902],\n [42.4112, -71.4046],\n [42.2987, -71.3651]\n ]\n}\nMAP_BOUNDARY_MODE=polygon\nMAP_BOUNDARY_FILE=/data/map_boundary.json\nMAP_BOUNDARY_SHOW=true\nMAP_BOUNDARY_MODE=polygon is setAdded boundary module tests
\nAdded frontend config injection coverage for boundary mode
\nTest suite passing:
\n82 passed, 2 skippedThis release makes the Peers tool default list size configurable via environment variable. #31
\nPEERS_DEFAULT_LIMIT/peers/{device_id} now uses PEERS_DEFAULT_LIMIT when no ?limit= query is provided?limit= still overrides the environment default50PEERS_DEFAULT_LIMIT=25\nDefault remains 8 if the environment variable is not set\nThis change only affects the default number of peers returned and does not impact peer counting logic
\n" }, { "version": "v.1.7.5", "name": "v1.7.5 - Route Details, Channel Secrets, and Packet Analyzer Links", "datetime": "2026-03-22T22:31:42Z", "url": "https://github.com/yellowcooln/meshcore-mqtt-live-map/releases/tag/v.1.7.5", "prerelease": false, "notes": "This release improves Route Details, adds channel secret file support for decrypting sender names, and introduces optional packet analyzer links.\r\n\r\n### Changes\r\n\r\n- Added `CHANNEL_SECRETS_FILE` support for loading channel secrets from a file instead of a long environment variable\r\n- Added a shipped `channel_secrets.example.json` with example channel entries\r\n- Replaced per-packet Node decoder process spawning with a persistent decoder worker\r\n- Reused the loaded channel key store across packets to reduce decode overhead\r\n- Route Details can now show a display-only sender-name row as hop `0` when the packet includes a decrypted sender name but not a stable sender identity\r\n- Route Details now preserves companion endpoints more accurately, including non-spatial endpoint rows for companions without GPS coordinates\r\n- Route Details hop counts now match the visible rows when sender companion rows are present\r\n- Route Details now shows the full packet hash in the header instead of truncating it\r\n- Route Details now prefers the MQTT packet hash over a shorter decoder `messageHash`\r\n- Added optional `PACKET_ANALYZER_URL` so packet hashes in Route Details can link to an external analyzer\r\n- Fixed the production route payload so Route Details keeps the packet hash and sender name instead of falling back to the internal `hash:receiver` route ID\r\n- Made the node popup `Location:` line clickable to copy `Location:This release improves Route Details, adds channel secret file support for decrypting sender names, and introduces optional packet analyzer links.
\nCHANNEL_SECRETS_FILE support for loading channel secrets from a file instead of a long environment variablechannel_secrets.example.json with example channel entries0 when the packet includes a decrypted sender name but not a stable sender identitymessageHashPACKET_ANALYZER_URL so packet hashes in Route Details can link to an external analyzerhash:receiver route IDLocation: line clickable to copy Location: <lat>, <lon> to the clipboardOptional channel secrets file (for decrypting sender names from supported group-text packets):
\nCHANNEL_SECRETS_FILE=/data/channel_secrets.json\nCopy channel_secrets.example.json to your chosen path and keep only the channels you want to ship.
Optional packet analyzer link base (used for Route Details hashes):
\nPACKET_ANALYZER_URL=https://analyzer.letsmesh.net/packets?packet_hash=\n76 passed, 2 skippedThis release adds MeshMapper coverage support, maintains legacy coverage map compatibility, and improves route accuracy on older 1-byte networks.
\nAll new ENV's in https://github.com/yellowcooln/meshcore-mqtt-live-map/blob/main/VERSIONS.md#v170-03-20-2026
\n/get-sampleshttps://meshmapper.net/coverage.phpCOVERAGE_MAX_AGE_DAYSN days are served to the map30 daysThis release fixes a long-standing peer history retention bug that caused the Peers tool to lose older data prematurely on high-volume meshes.
\n/peers statistics off raw route_history_segmentsROUTE_HISTORY_MAX_SEGMENTSOn larger meshes, the Peers tool could report a 24-hour window while actually only retaining a few hours of data due to early truncation by ROUTE_HISTORY_MAX_SEGMENTS.
This release separates peer statistics from route segment limits, ensuring accurate long-term visibility.
57 passedThis release improves device role detection accuracy, makes it easier to verify the running version, and fixes low-range multibyte route hash handling.
\nVERSION.txtpathLength00AB0000ABSome 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.
\n55 passedThis release improves route-details accuracy and strengthens device role detection from MQTT data.
\npoint_ids directly for hop attributionABABCDABCDEFpoint_id / point_label data for easier hop verificationThis release focuses on making route-details popups more accurate and reducing prefix/name mismatches in the hop list.
\n" }, { "version": "v1.6.1", "name": "v1.6.1 - Multibyte Decoder Migration and Routing Compatibility", "datetime": "2026-03-11T15:32:45Z", "url": "https://github.com/yellowcooln/meshcore-mqtt-live-map/releases/tag/v1.6.1", "prerelease": false, "notes": "## v1.6.1\r\n\r\nThis 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.\r\n\r\n### Highlights\r\n\r\n- Replaced the official `@michaelhart/meshcore-decoder` package with [`meshcore-decoder-multibyte-patch`](https://www.npmjs.com/package/meshcore-decoder-multibyte-patch)\r\n- Added route prefix support for:\r\n - 1-byte prefixes: `AB`\r\n - 2-byte prefixes: `ABCD`\r\n - 3-byte prefixes: `ABCDEF`\r\n- Updated route normalization and matching so mixed-width paths can be resolved in the same network\r\n- Expanded route tests to cover mixed 1/2/3-byte path handling and exact-prefix matching\r\n\r\n### Why this release\r\n\r\nMeshCore is moving toward multibyte repeater prefixes. The previous official decoder was a blocker for that rollout. \r\nThis release switches the map to a patched decoder that can ingest and decode those path formats now.\r\n\r\n### Current support status\r\n\r\n- Multibyte path ingest is working in development\r\n- Live path strings with 1-byte, 2-byte, and 3-byte segments have been observed during testing\r\n- The app is intended to be ready for upcoming multibyte repeater rollouts\r\n- Not tested in a mixed-network environment. I am currently unable to test this in my mesh. Please open an [Issue](https://github.com/yellowcooln/meshcore-mqtt-live-map/issues) if you encounter any problems related to this feature.\r\n\r\n### Notes\r\n\r\n- **Show Hops** now documents and expects plain prefix display such as `AB`, `ABCD`, and `ABCDEF`\r\n- This release focuses on decoder and routing compatibility and does not introduce UI features", "notesHtml": "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.
\n@michaelhart/meshcore-decoder package with meshcore-decoder-multibyte-patchABABCDABCDEFMeshCore 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.
AB, ABCD, and ABCDEF