Version 1.10.1

Bug fix and UI improvement release.

🐛 Bug Fixes

Fixed Foreign Key Constraint Issues (#72)

Resolves critical database errors that prevented normal operation:

• Issue #69: Fixed "Purge Nodes" failing with FK constraint error

  • Now properly deletes child records (messages, telemetry, traceroutes, route_segments) before deleting nodes
  • Respects database foreign key constraints

• Issue #70: Fixed message sending failing with FK constraint error on fresh databases

  • Ensures local node exists before inserting sent messages
  • Creates minimal node entries for destination nodes if missing
  • Prevents FK violations when sending messages before nodes are fully populated

Additional Improvements

• Added hwModel to local node info type for future use
• Properly populate hwModel when processing MyNodeInfo

🎨 UI Improvements

Route Popup Distance Formatting (#73)

Improved visual consistency and readability of distance information in map popups:

• Distance values now centered and highlighted in accent color
• Consistent styling with "Used in N traceroutes" format
• Applied to all popup types:
  • Purple route segments (intermediate hops)
  • Red forward traceroute paths
  • Red return traceroute paths

📦 Installation

Docker (Recommended):

docker pull ghcr.io/yeraze/meshmonitor:1.10.1

Docker Compose:

services:
  meshmonitor:
    image: ghcr.io/yeraze/meshmonitor:1.10.1
    ports:
      - "8080:8080"
    volumes:
      - ./data:/data
    environment:
      - MESHTASTIC_NODE_IP=192.168.1.100

From Source:

git clone https://github.com/Yeraze/meshmonitor.git
cd meshmonitor
git checkout v1.10.1
npm install
npm run build
npm run start

🔗 Related Issues

• Fixes #69
• Fixes #70

📋 Full Changelog

Commits in this release:

• fix: Foreign key constraint issues (#69, #70) (#72)
• ui: improve route popup distance formatting for better visibility (#73)

For full details, see the v1.10.0 → v1.10.1 comparison.