Yeraze/meshmonitor v1.18.2 on GitHub

🐛 Bug Fix

Auto-Ack Message Saving

Fixed critical issue where auto-acknowledge responses were being sent to the mesh network but not saved to the database, making them invisible in the MeshMonitor UI.

Problem:
In v1.18.1, we fixed the DM channel assignment bug by removing message saving from meshtasticManager.sendTextMessage(). However, this inadvertently broke auto-ack functionality since auto-ack calls sendTextMessage() directly and relied on it to save messages to the database.

Symptoms:

Auto-ack responses were successfully transmitted to the mesh network
Logs showed "Message sent successfully"
But responses were not visible in the MeshMonitor UI
Other mesh users could see the responses, but they didn't appear in the local database

Solution:

Restored message saving in meshtasticManager.sendTextMessage() with correct channel logic
Uses channel: destination ? -1 : channel to properly handle both DMs and channel messages
Removed duplicate saving from server.ts API endpoint
Now all messages (user-sent, auto-ack, auto-announce) are saved consistently

Changes:

✅ Auto-ack responses now visible in UI
✅ Direct messages correctly use channel -1
✅ Channel messages correctly use actual channel number
✅ No duplicate message saves

📦 Full Changelog

v1.18.1...v1.18.2

🚀 MeshMonitor v1.18.2

📦 Installation

Docker (recommended):

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

🧪 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.