π What's New in Version 1.3.0
πΊοΈ Transmission Route Visualization
The Message Card now displays full transmission metrics for received messages:
- RSSI, SNR, and hop count shown as a compact metrics bar below each message
- Expandable path section β click the metrics bar to reveal the complete transmission route (e.g.,
a1b2 β c3d4 β e5f6 β ...) - Smart path formatting β automatically splits hex paths into readable node hops, with special handling for FLOOD and FOLD route types
- SVG icons for signal strength, activity, and waypoints β visually clean and theme-friendly
π¬ Bubble-Style Message Layout
Messages now display in a modern chat-like bubble interface:
- Sent messages β right-aligned with green accent
- Received messages β left-aligned with blue accent
- Clear header with time and sender name
- Direction arrow icons integrated into the sender line
π‘ Real-Time rx_log Data
The card now subscribes to meshcore_message events and reads transmission data from a local NDJSON file:
- Automatic refresh when new messages arrive
- Local file caching with automatic pruning (24h max age, 500 entries limit)
- Seamless integration β metrics appear automatically for messages with available route data
π§ Configuration Required for Route Visualization
To enable the route visualization feature, you need to set up a file-based notification service that captures MeshCore events:
Step 1: Configure the File Notification Service
Please configure Set up a notification service and the file path set to /config/www/meshcore_rx.json
default_config:
whitelist_external_dirs:
- '/config/www'Note: If you are using default_config:, add allowlist_external_dirs under a separate homeassistant: key in your configuration.yaml. This allows the card to access /local/meshcore_rx.json.
Step 2: Create the Automation
Create a new automation that writes every meshcore_message event to the file:
alias: MeshCore - Log RX to file
description: ""
triggers:
- event_type: meshcore_message
trigger: event
actions:
- data:
entity_id: notify.file #<-- Insert the correct entity ID from the file integration
message: |
{{ trigger.event.data | tojson }}
action: notify.send_message
mode: queued- Note: The entity_id must match the notification entity created in Step 1. If you used a different name, adjust accordingly (e.g., notify.file).
Step 3: Verify
Restart Home Assistant
Send or receive a message via MeshCore
Check that /config/www/meshcore_rx.json exists and contains JSON lines
The Message Card will automatically load and display route metrics for matching messages
β Support Development
If you find this project useful and would like to support future development:
Your support helps fund development, testing, bug fixes, and new features.