github dida886/meshcore-card 1.3.0
See Your Signal: Routes, Bubbles & Real-Time Metrics

latest releases: 1.8.0, 1.7.4, 1.7.3...
5 months ago

πŸš€ What's New in Version 1.3.0

πŸ—ΊοΈ Transmission Route Visualization

message-card-screenshot

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

Add Repository

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:

Buy Me A Coffee

Your support helps fund development, testing, bug fixes, and new features.

Don't miss a new meshcore-card release

NewReleases is sending notifications on new releases.