github Yeraze/meshmonitor v2.19.1
v2.19.1 - Auto-Upgrade Enhancements & Bug Fixes

3 hours ago

⚠️ IMPORTANT: Auto-Upgrade Configuration Change

If you are using the Auto-Upgrade feature, you MUST add a new environment variable to your Docker Compose configuration:

environment:
  - COMPOSE_PROJECT_NAME=meshmonitor

Why this is required:

  • The upgrade watchdog needs to know which Docker Compose project to target when performing upgrades
  • Without this variable, the upgrader may target the wrong containers or fail to upgrade
  • This ensures the upgrader correctly identifies and upgrades your MeshMonitor instance

Where to add it:
Add this to your docker-compose.yml or docker-compose.override.yml file in the environment section of the meshmonitor-upgrader service.

See the Auto-Upgrade Documentation for complete configuration examples.


What's New in v2.19.1

✨ Features & Enhancements

  • Auto-Acknowledge SNR/RSSI Tokens (#695)

    • Added {SNR} and {RSSI} tokens to auto-acknowledge feature
    • Enables dynamic acknowledgment messages with signal quality metrics
  • Docker Socket Permissions Check (#707)

    • Added automated test to verify Docker socket permissions during auto-upgrade configuration
    • Improves reliability of auto-upgrade feature setup

🐛 Bug Fixes

  • Virtual Node Traceroute History (#708)

    • Fixed issue where traceroutes initiated by 3rd party Virtual Node clients didn't appear in Traceroute History modal
    • Traceroute queries now search bidirectionally to capture all traceroutes regardless of initiator
  • Date Format in Auto-Acknowledge (#705, closes #704)

    • Fixed {DATE} token to respect user's configured date format preference
    • Ensures consistency between UI date display and automation tokens
  • Time Format in Auto-Acknowledge (#702, closes #698)

    • Fixed {TIME} token to respect user's configured time format preference (12h/24h)
    • Automation messages now match user's time format settings
  • Map Feature Toggle Persistence (#703, closes #697)

    • Fixed map feature toggles (Nodes, Messages, Telemetry, Traceroutes, Waypoints) not persisting to localStorage
    • User preferences now properly saved and restored across sessions

📝 Documentation

  • Updated auto-upgrade documentation with COMPOSE_PROJECT_NAME configuration
  • Clarified Docker Compose overlay file preservation during upgrades

Pull Requests Merged

  • #708: fix: Show Virtual Node traceroutes in Traceroute History modal
  • #707: feat: Add Docker socket permissions check to auto-upgrade configuration test
  • #706: chore: Bump version to 2.19.1
  • #705: fix: Respect user date format preference in auto-acknowledge {DATE} token
  • #703: fix: Persist all map feature toggle selections to localStorage
  • #702: fix: Respect user time format preference in auto-acknowledge {TIME} token
  • #695: feat: Add SNR and RSSI tokens to auto-acknowledge feature

Issues Resolved

  • #704: [BUG] {DATE} token in automations not match user date format
  • #698: [BUG] {TIME} token in automation not match the time format
  • #697: [BUG] Feature selection not saved
  • #696: Traceroute - How does it work?
  • #694: [FEAT]

Full Changelog: v2.19.0...v2.19.1

🚀 MeshMonitor v2.19.1

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/data \
  ghcr.io/Yeraze/meshmonitor:2.19.1

🧪 Testing

✅ All tests passed
✅ TypeScript checks passed
✅ Docker images built for linux/amd64, linux/arm64, linux/arm/v7

📋 Changes

See commit history for detailed changes.

🚀 MeshMonitor v2.19.1

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/data \
  ghcr.io/Yeraze/meshmonitor:2.19.1

🧪 Testing

✅ All tests passed
✅ TypeScript checks passed
✅ Docker images built for linux/amd64, linux/arm64, linux/arm/v7

📋 Changes

See commit history for detailed changes.

Don't miss a new meshmonitor release

NewReleases is sending notifications on new releases.