🚀 Version 1.10.0: TCP Streaming Architecture

This is a major architectural upgrade that replaces HTTP polling with native TCP streaming for significantly improved performance and reliability.

⚡ Major Changes

TCP Streaming Protocol

MeshMonitor now connects directly to Meshtastic devices using their native TCP streaming protocol (port 4403), replacing the previous HTTP polling implementation.

Benefits:

• 🎯 ~90% bandwidth reduction - No HTTP overhead
• ⚡ Instant message delivery - Event-driven, not polling-based
• 📉 Lower latency - TCP push model vs 2-second poll interval
• 🔄 More reliable - Automatic reconnection with exponential backoff
• 💻 Lower CPU usage - Event-driven vs continuous polling

Implementation Details

• Event-driven architecture using Node.js EventEmitter
• 4-byte frame protocol: [0x94][0xc3][LENGTH_MSB][LENGTH_LSB][PROTOBUF_PAYLOAD]
• Automatic reconnection: 1s → 2s → 4s → 8s → 16s → 30s (max 10 attempts)
• Robust frame parsing with corruption recovery
• All 147 tests passing

Integration Options

The TCP implementation enables multiple connection scenarios:

1. Direct TCP (WiFi/Ethernet nodes) ✅

MeshMonitor → TCP:4403 → Meshtastic Node

2. meshtasticd Proxy (BLE/Serial nodes) ✅

MeshMonitor → TCP:4403 → meshtasticd → BLE/Serial → Meshtastic Device

3. HomeAssistant Integration ✅

MeshMonitor → TCP:4403 → HomeAssistant → Meshtastic

4. Custom Proxies ✅
Any proxy implementing the Meshtastic TCP protocol is compatible.

📚 Documentation Updates

Comprehensive documentation overhaul for the TCP refactor:

• ✅ New "Getting Started" section with copy-paste deployment commands
• ✅ meshtasticd integration instructions for BLE/Serial devices
• ✅ TCP protocol technical details and frame format documentation
• ✅ Updated architecture diagrams and explanations
• ✅ Integration scenarios documented
• ✅ Historical context preserved in MESHTASTICD_ANALYSIS.md

🔧 Configuration Changes

Updated Environment Variables

# Old (HTTP - removed)
MESHTASTIC_USE_TLS=false

# New (TCP)
MESHTASTIC_TCP_PORT=4403  # Default port for Meshtastic TCP

Backward Compatible

Existing MESHTASTIC_NODE_IP configuration works unchanged. Simply update your environment to use the new TCP port variable.

📦 Docker Deployment

Pre-built images available on GitHub Container Registry:

docker pull ghcr.io/yeraze/meshmonitor:1.10.0

# Or use latest
docker pull ghcr.io/yeraze/meshmonitor:latest

Quick start:

export MESHTASTIC_NODE_IP=192.168.1.100
export MESHTASTIC_TCP_PORT=4403
docker compose up -d

🔌 meshtasticd Integration

Connect to BLE or Serial devices via meshtasticd:

# For BLE devices
meshtasticd --ble-device "Meshtastic_1234"

# For Serial devices  
meshtasticd --serial-port /dev/ttyUSB0

# Point MeshMonitor to meshtasticd
export MESHTASTIC_NODE_IP=localhost
docker compose up -d

🧪 Testing

• ✅ All 147 automated tests passing
• ✅ Production validated with 140+ node mesh network
• ✅ 24+ hours stable operation
• ✅ No regressions in existing features

📝 Pull Requests

• #67 - TCP streaming implementation
• #68 - Documentation updates

🙏 Acknowledgments

This refactor was analyzed, implemented, and documented with Claude Code.

Full Changelog: v1.9.3...v1.10.0

🚀 MeshMonitor v1.10.0

📦 Installation

Docker (recommended):

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

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