v0.7.7

What's Changed

Features

• Add clickable edges to network connections graph (#126)
  • Click any edge in the force-directed graph to see connection details, SNR statistics, and recent traceroutes
  • Color legend showing node connection counts
• Add data retention settings UI (#124)

Bug Fixes

• Resolve gateway node for MeshMonitor sources in propagation view (#123)
• Add data type descriptions to retention settings (#125)
• Increase rate limiting delays for historical data collection (#127)
• Filter unregistered metrics from available metrics endpoint (#129)

Chores

• Bump version to 0.7.7 (#128)

Full Changelog: v0.7.6...v0.7.7

v0.7.6

What's Changed

Bug Fixes

• Exclude MeshMonitor metadata from Message Utilization packet counts (#121)

Chores

• Bump version to 0.7.6 (#122)

Full Changelog: v0.7.5...v0.7.6

v0.7.5

What's Changed

Features

• Integrate MeshMonitor position-history API — Fetches full position history via GET /api/v1/nodes/{nodeId}/position-history with offset pagination and dedup, closing the position undercount gap. Gracefully handles older MeshMonitor instances (404 early-exit). Integrated into regular polling, startup catchup, and historical background collection. #119

Bug Fixes

• Truncate telemetry timestamps for Message Utilization dedup — Fixes duplicate telemetry records caused by sub-second timestamp differences. #118

Chores

• Bump version to 0.7.5 #120

Full Changelog: v0.7.4...v0.7.5

v0.7.4

What's Changed

Features

• Add 429 rate limit handling with exponential backoff to MeshMonitor collector (#114)

Bug Fixes

• Use lowercase enum values for PacketRecordType in PostgreSQL (#115)
• Handle fresh database bootstrap in entrypoint — new installs with an empty database no longer fail on startup (#116)

Full Changelog: v0.7.3...v0.7.4

v0.7.3

What's Changed

Features

• Expanded Meshtastic portnum decoding and PaxCounter support — the MQTT collector now decodes 15+ portnums (up from 4), including Waypoint, Routing, NeighborInfo, MapReport, StoreForward, PaxCounter, Admin, RemoteHardware, KeyVerification, and ATAK. Text-based portnums (DetectionSensor, Alert, RangeTest, Reply, NodeStatus) are decoded as UTF-8 strings. PaxCounter packets extract wifi, ble, and uptime metrics into the telemetry table (#112)
• Traceroute, encrypted, unknown & nodeinfo in utilization analysis — the utilization analysis now includes traceroute, encrypted, unknown, and nodeinfo packet types (#110)

Bug Fixes

• Fix solar forecast per-node charging/discharge hours — solar forecast simulation now uses per-node charging and discharge hours instead of global defaults (#111)

Chores

• Bump version to 0.7.3 (#113)

Full Changelog: v0.7.2...v0.7.3

v0.7.2

What's Changed

Features

• Clickable route segment popups on map — clicking a route segment line now shows a popup with both endpoint node names, traceroute usage count, and contributing data sources (#105)
• Clock skew indicator in message detail modal — a ⌚ icon appears next to source timestamps when the gateway radio's clock differs from server time by >30 seconds, with hover tooltip showing skew details (#106)

Bug Fixes

• Fix MQTT NodeInfo parsing for protobuf packets — short_name, long_name, and hw_model were silently dropped for protobuf-decoded NodeInfo packets due to case-mismatched payload keys. MQTT nodes now properly populate display names as NodeInfo packets arrive (#108)

Chores

• Bump version to 0.7.2 (#109)

Full Changelog: v0.7.1...v0.7.2

v0.7.1

What's Changed

Bug Fixes

• Consolidate duplicate channels across sources — The same physical Meshtastic channel no longer appears multiple times in the Communication page when collected from different sources (e.g. "Channel 0" from MeshMonitor and "MediumFast" from MQTT). Channel names are now inferred for MeshMonitor sources by cross-referencing messages with MQTT, and channels with the same name merge naturally across sources. (#103)

Maintenance

• Bump version to 0.7.1 (#104)

Full Changelog: v0.7.0...v0.7.1

v0.7.0

What's New

Propagation Map & Timing

• Propagation Time Metric: The Message Detail Modal now shows how long a message took to propagate across the mesh (e.g. "850ms", "2.3s", "1m 12s") — #100
• Animated Propagation Map: New "Visualize Propagation" button opens a dark-themed map showing animated message propagation across gateways with play/pause controls, color-coded markers, and a clickable timeline — #100
• Temporal Source Sorting: Message reception sources are now sorted chronologically (earliest first) — #101

Bug Fixes

• Fix gateway and channel extraction from MQTT topic for JSON messages — #99
• Drop stale ix_messages_source_packet index and broaden duplicate handler — #97
• Match ON CONFLICT to 3-column gateway unique index for messages — #96
• Use ON CONFLICT DO NOTHING for MQTT traceroute inserts — #95

Maintenance

• Bump version to 0.7.0 — #102

Full Changelog: v0.6.7...v0.7.0

v0.6.7 - Historical Traceroute Positions

What's New

Historical Traceroute Positions

Traceroutes now store node positions at the time they were completed. The map renders routes to where nodes actually were, not where they've moved to since. MeshMonitor sources use the new routePositions API field; MQTT sources snapshot last-known positions from the database at ingestion time. When historical positions aren't available, the frontend falls back to current node positions.

Bug Fixes

• Fixed anonymous user migration failing due to missing totp_enabled column in INSERT
• Added server_default declarations for all NOT NULL columns with Python defaults, preventing raw SQL INSERT failures on older installs

Pull Requests

• #93 - feat: Support route_positions in traceroutes
• #92 - fix: Add server_default declarations and migration for NOT NULL columns
• #91 - fix: Include totp_enabled in anonymous user migration INSERT
• #94 - chore: Bump version to 0.6.7

Full Changelog: v0.6.6...v0.6.7

v0.6.6

What's Changed

Features

• Anonymous user permissions — Built-in anonymous user controls what unauthenticated visitors can see. Per-tab read/write permissions allow making parts of the dashboard public without requiring login. (#88)

Bug Fixes

• Position telemetry for MeshMonitor sources — MeshMonitor sources now correctly create position telemetry rows. (#87)
• Relay node resolution and message detail UX — Improved relay node lookup and message detail display. (#86)
• Duplicate message detection — Fixed constraint name mismatch that could cause duplicate message errors. (#85)

Documentation

• User management docs — New comprehensive documentation covering user roles, tab-based permissions, anonymous access, and default permission tables. Updated cross-links across existing docs. (#89)

PRs Included

• #85 — fix: Match correct constraint name for duplicate message detection
• #86 — fix: Improve relay node resolution and message detail UX
• #87 — fix: Add position telemetry rows for MeshMonitor sources
• #88 — feat: Add anonymous user permissions
• #89 — chore: Bump version to 0.6.6 and add user management docs

Issues Resolved

• #80 — [BUG] Coverage map reports "No position data found"

Full Changelog: v0.6.5...v0.6.6