MeshCore Ninja Alpha
← MeshCore for Home Assistant

MeshCore for Home Assistant · Releases

from GitHub · updated 2026-06-23

20 releases

  1. v2.8.0 # 6 days ago · 2026-06-18 01:55 UTC
    View release ↗

    Features

    • Unified Contact Discovery Mode (#261) — the two overlapping contact-discovery flags (disable_contact_discovery and the never-shipped large_mesh_mode) are collapsed into a single Contact Discovery Mode select with three choices:

      • Entity per contact (default) — one diagnostic binary_sensor per discovered contact, same as before.
      • Data only — discovered (un-added) contacts are tracked as data with no per-contact entity, while added/curated contacts keep theirs. On dense meshes this avoids hundreds of low-utility entities and the entity-registry churn they drive. The dropdown, services, chat panel, an aggregate summary sensor, and meshcore.get_discovered_contact all keep working.
      • Disabled — no discovered-contact processing at all.

      Set it at install time or in Configure → Global Settings.

    Fixes

    • Telemetry/GPS AttributeError from untracked nodes (#266) — _get_node_info assumed a dict-shaped public_key; a TELEMETRY/GPS event from a node that wasn't a tracked repeater/client/root raised AttributeError on the string-shaped key and killed the handler.
    • node_status sensor stuck "Disconnected" (#267) — the status callback set its value but never pushed state, so the header indicator could show disconnected (while actually connected) until the next device event. Now pushes on event and seeds an initial value at setup.
    • UTC-aware MQTT timestamps (#259) — status, raw event, and normalized packet payloads now emit offset-aware ISO 8601 timestamps so consumers don't misread local time as UTC. Fixes #258.
    • Quiet benign reconnect-race log noise (#268) — the no_event_received result from the get_msg loops during config re-add / reconnect is downgraded to debug; real errors still log at ERROR.
    • Flood-scope * wildcard (#263) — a raw * entry in the flood-scope allowlist is now recognized as the global wildcard and skipped, instead of deriving a junk transport key for a non-existent #* region.

    Notes

    • Migration on first start: existing installs migrate config entry v2 → v3 automatically. disable_contact_discovery=true maps to Disabled; otherwise the mode defaults to Entity per contact, so behavior is unchanged unless you opt into Data only. No reload, no entity-registry churn.
    • MQTT timestamp format change (#259): the time/date display fields in MQTT packet payloads now reflect UTC wall-clock rather than local time. If you parse those downstream, note the shift.
    • Minimum Home Assistant version remains 2023.8.0. No meshcore-py floor change (still >=2.3.7).
  2. v2.7.0 # 23 days ago · 2026-06-01 02:44 UTC
    View release ↗

    Features

    • Self-diagnostic sensors for the companion node (#251) — opt-in polling of the locally-attached companion's get_stats_core / get_stats_radio / get_stats_packets, exposed as 13+ new sensors on the main device. Local-transport queries only — no mesh traffic.
    • Region-scoped channel broadcasts (#250) — new scope parameter on meshcore.send_channel_message for TC_FLOOD region-scoped sends. Optional flood_scopes allowlist in global settings labels incoming scoped messages with their region name.
    • Remove orphan devices from the UI (#247) — repeater, client, and contact devices that are no longer tracked can now be deleted via the HA device page. Hub and live devices are refused. Closes #229.
    • Repeater neighbor count sensor (#228) — per-repeater count of active neighbors derived from the existing neighbor list.
    • hop_count + snr on incoming channel messages (#245) — logbook event now carries SNR and hop count for channel traffic, matching the existing DM behavior.
    • Conditional recipient type selection (#218) — adapts the message-input UI based on the chosen recipient.

    Fixes

    • Region-scope (TC_FLOOD) RX_LOG correlation (#246) — fixes a 4-byte transport-code offset that broke RX_LOG correlation for all region-scoped messages and corrects the AES plaintext offset. Closes #237, #242, #198.
    • path_hash_size on rx_log correlation entry (#249) — completes #226 by propagating the per-hop hash width to every consumer of meshcore_message.
    • execute_command response normalization (#248) — req_*_sync helpers that return plain dicts, lists, scalars, or None are now surfaced correctly instead of being silently dropped or raising a confusing error.
    • Discovered-contact cleanup post-#236 (#252) — repairs four cleanup paths that the #236 unique_id migration left looking up entities by the old format.
    • Recorder cap on discovered-contact select (#254) — options is now excluded from recorder state, dodging the 16 KiB per-state attribute cap that fired warnings on dense meshes. Closes #243.
    • Removed hass.helpers.entity_registry.async_get() accessor (#253) — switched to er.async_get(hass) in three contact services. Fixes AttributeError on recent HA core.
    • MQTT startup wait (#244) — fixes a task that blocked HA boot.
    • recv errors as count + measurement (#239) — corrects sensor types.
    • multi-entry message_sent fan-out (#235) — filters by entry_id.
    • Contact-diagnostic unique_id scoping (#236) — scoped by entry_id with one-time migration.
    • TZ-aware UTC timestamp on meshcore_message (#234).
    • RX_LOG multi-byte path size parsing (#226).

    Docs

    • Companion Integration API page (#217)
    • ESPHome BLE bridge workaround (#223)
    • Discord community channel linked in README + docs site

    Notes

    • Minimum Home Assistant version remains 2023.8.0.
    • The meshcore-py floor is >=2.3.7 (was bumped in #222).
    • #236's unique_id migration runs once per install on first start of this release. Entities migrate automatically. Users on the broken cleanup state from earlier #236-only installs will see the Phase 4 orphan sweep clean up stale registry entries (covered by #252).
    • #251 self-diagnostics defaults off. Enable in Global Settings if you want the new sensors.
  3. v2.6.0 # 2 months ago · 2026-04-28 05:19 UTC
    View release ↗

    Features

    • Structured query services for companion integrations (#216) — new meshcore.get_contacts, meshcore.get_channels, and meshcore.trace services return typed responses so companions don't have to scrape execute_command output.
    • SNR + hop count on incoming DM events (#215) — meshcore_message events now include hop_count (always) and snr (V3 firmware) for direct messages, matching what was already available for channel messages via rx_log_data.
    • Repeater neighbor sensors (#211) — per-repeater SNR and activity sensors with auto-cleanup of stale neighbors, plus an opt-in toggle and configurable airtime cost in the global settings.
    • Per-device online binary sensor (#209) — replaces the imprecise global device.connected flag with per-device binary_sensor.*_online entities derived from _last_successful_request timing.
    • Stale discovered-contact cleanup (#183) — new days_threshold parameter on clear_discovered_contacts, plus an opt-in daily auto-cleanup with a configurable threshold.
    • Adaptive RX_LOG poll-wait (#182) — replaces the blocking 500ms sleep on incoming channel messages with a 50ms-step poll that fires as soon as data arrives, with a background pass for late-arriving repeater RX_LOGs delivered as meshcore_delivery_update events.

    Fixes

    • Entity-identity stabilization (#201) — removes device name from unique_id (one-time startup migration), refreshes SELF_INFO after config-modifying commands, and adds missing async_write_ha_state() so frontend updates without a reload.
    • Map uploader (#200) — corrects ADV_TYPE_CHAT and points the uploader at meshcore.io.
    • Telemetry sensors (#191) — restores missing device_class and units on telemetry sensors.
    • execute_command AttributeError (#190) — removes a stale set_command_result call.

    Docs

    • README now links to the meshcore-card Lovelace card (#220).
    • Installation docs USB firmware note (#133).

    Notes

    • Migration on first start: #201 strips device names from unique_id once per upgrade; entities migrate automatically. Some users may see a brief reload as the registry updates.
    • The minimum Home Assistant version remains 2023.8.0.
  4. v2.5.0 # 3 months ago · 2026-04-01 16:21 UTC
    View release ↗

    What's New

    Map Auto Uploader

    Automatically uploads repeater and room server adverts to map.meshcore.dev when your companion hears them. No separate bot needed. Enable in Global Settings. Requires ENABLE_PRIVATE_KEY_EXPORT=1 on firmware. (#163)

    Message Delivery Feedback

    New Last Message Delivery sensor shows real-time delivery status for sent messages. Channel messages show repeater count (progressive updates as relays arrive). Direct messages show ACK confirmation. (#168)

    Instant Message Delivery

    Subscribes to the firmware's MESSAGES_WAITING push notification for near-instant message fetching instead of waiting for the poll interval. (#177)

    Reconfigure Connection

    Change your connection type (USB/BLE/TCP) or parameters without deleting and re-adding the integration. All settings are preserved. Look for the "Reconfigure" button on the integration page. (#187)

    Public Key Change Detection

    Detects when a companion device's public key changes (e.g., after firmware reflash) and automatically migrates all entity IDs. Creates a repair notification for any manual references that need updating. (#169)

    Companion Prefix Sensor

    New sensor showing the device's routing prefix based on path_hash_mode, with live updates from SELF_INFO events. (#169)

    Fixes

    • Repeater status/telemetry timeouts — Fixed login check (was comparing against wrong event type), switched to SDK sync methods with firmware-calculated timeouts. Multi-hop repeaters now respond reliably. (#185)
    • coordinator.data set to None — _async_update_data now returns result_data so HA's coordinator framework has valid data. Fixes NoneType has no attribute 'get' crashes. (#171)
    • Repeater firmware version not updating — Re-queries firmware version when editing a repeater in Manage Devices. (#179)
    • Edit repeater clears password — Password field no longer gets overwritten with empty string when saving other settings. (#179)
    • set_flood_scope type — Fixed parameter type from int to str. (#181)
    • Conditional message polling — Replaced unconditional get_msg() every 5s with a 60-second safety-net poll, reducing ~17,280 unnecessary commands/day on quiet meshes. (#186)
    • mesh_core returns None when disconnected — Prevents startup crashes when device isn't available. (#163)
    • ConfigEntryNotReady on connection failure — HA retries connection automatically instead of leaving the integration in a broken state. (#173)

    Other

    • Dutch and Slovak translations for new features
    • Last command result sensor for dashboard CLI feedback (#163)
    • Channel select now filters unused/empty channels (#163)
    • execute_command supports return_response for automation use (#169)
    • OptionsFlow updated to HA 2024+ pattern (#163)
    • Deprecated logger.warn() calls replaced with logger.warning()
  5. V2.4.1 # 4 months ago · 2026-03-07 16:20 UTC
    View release ↗
  6. v2.4.0 # 4 months ago · 2026-03-03 03:07 UTC
    View release ↗

    MQTT Upload Support

    • Multi-broker MQTT upload with full UI configuration
    • LetsMesh integration with EdDSA auth-token support (Python fallback when CLI unavailable)
    • Per-broker owner/email JWT claim settings
    • Periodic MQTT status metrics for LetsMesh observer support
    • Packet-only publishing aligned with meshcoretomqtt format
    • Broker connection status binary sensors
    • Auto-fetch device private key for auth tokens
    • Packet hash stabilization to reduce LetsMesh duplicates

    Execute Command Improvements

    • Bump meshcore to >=2.2.15 with synced command parameter mappings
    • Functional syntax support: set_coords(37.7749, -122.4194) (fixes #111)
    • Supports positional args, keyword args, strings, numbers, booleans, and bytes literals
    • Add set_flood_scope command

    Discovered Contacts Management

    • New opt-in FIFO limit for discovered contacts (configurable max, default 100 when enabled)
    • Oldest contacts evicted first; re-advertisements refresh queue position
    • Evicted contacts have binary sensor entities automatically removed
    • New meshcore.clear_discovered_contacts service to remove all at once

    Bug Fixes

    • Fix duplicate entry setup and guard static path registration
    • Fix options menu contact detection for repeaters and clients
    • Fix missing log argument
    • Only cleanup devices associated with the current entry

    Telemetry

    • Support negative current readings (charging vs discharging)
    • Add power sensor, display current in mA
    • 2-character pubkey prefix for display

    Documentation

    • Add MQTT upload documentation page
    • Document functional command syntax in services docs
    • Add contact FIFO limit section to contacts docs
    • Replace manual storage file deletion with clear_discovered_contacts service

    Housekeeping

    • Add __pycache__/, *.pyc, .pytest_cache to .gitignore
    • Add test infrastructure and unit tests for command parsing and contact eviction
  7. V2.3.0 # 5 months ago · 2026-02-05 20:47 UTC
    View release ↗
    • Fixes issues with non-normalized repeater names and the latest versions of home assistant
  8. v2.2.5 # 5 months ago · 2026-01-26 21:21 UTC
    View release ↗

    Fix documentation link

  9. v2.2.4 # 6 months ago · 2025-12-27 22:18 UTC
    View release ↗

    Fix issue with broken contact select options

  10. v2.2.3 # 7 months ago · 2025-11-28 06:03 UTC
    View release ↗

    Fixes minor issue with sensors reverting to discovered after being added to the connected client.

  11. v2.2.2 # 7 months ago · 2025-11-27 06:39 UTC
    View release ↗
    • Fixes some bugs preventing proper contact sensor synchronization when adding/removing contacts.
    • Changes RX and TX Airtime sensors to be TOTAL_INCREASING
  12. v2.2.1 # 7 months ago · 2025-11-23 17:58 UTC
    View release ↗

    New Features

    RX_LOG Correlation

    • Automatic RX_LOG parsing and decryption - RX_LOG_DATA events are now automatically parsed and decrypted when GroupText payloads are detected
    • Multi-reception correlation - meshcore_message events now include rx_log_data with radio metrics (SNR, RSSI) and path information from all mesh receptions
    • Path visualization - See which routes your messages took through the mesh network

    Example rx_log_data includes:

    • Signal quality (SNR/RSSI)
    • Mesh path (hop nodes)
    • Channel hash
    • Multiple receptions from different routes

    Contact Management

    • Remove discovered contact service - New service to clean up discovered contacts from Home Assistant without removing from node
    • Disable contact discovery toggle - New global setting to disable automatic contact sensor creation for large networks (500+ contacts)

    Improvements

    Performance & Reliability

    • Rate limiting - Token bucket refill rate reduced from 180s to 120s (2 minutes instead of 3)
    • Auto-disable inactive devices - Tracked repeaters/clients automatically disable after 5 days without successful requests (120 hours)
    • Increased sensor timeout tolerance - Sensors now wait 3x the update interval before marking unavailable (previously 1.5x)
    • Event-driven contact updates - Removed contact refresh interval setting in favor of real-time NEW_CONTACT event handling

    Bug Fixes

    • Fixed service parameter types for change_contact_path and change_contact_flags methods
  13. v2.2.0 # 8 months ago · 2025-10-29 05:04 UTC
    View release ↗

    MeshCore Home Assistant Integration - Version 2.2.0

    🚀 Major Features

    Token Bucket Rate Limiting

    • New: Intelligent rate limiting to protect mesh network from excessive traffic
    • Configuration: 20 token burst capacity, 1 token refills every 3 minutes
    • Impact: Sustains ~20 requests per hour across all tracked devices
    • Sensor: Exposes a sensor to track the rate limiting bucket capacity overtime
    • Behavior: Requests are skipped (not queued) when tokens depleted, logged as debug messages
    • Documentation: Comprehensive rate limiting guide in remote device tracking docs

    Device Disabling

    • New: Temporarily disable repeaters or clients without removing them
    • Access: Available in config flow → Manage Monitored Devices → Edit
    • Use Cases:
      • Maintenance windows
      • Reducing network traffic
      • Testing network performance
      • Isolating problematic devices
    • Result: All status, telemetry, and login requests stopped while entities remain

    Manual Contact Management Mode

    • New: Automatic manual contact mode on startup
    • Discovered Contacts: New select entity for contacts not yet added to node
    • Added Contacts: Separate select entity for contacts already on your node
    • Persistence: Discovered contacts saved to .storage/meshcore.<entry_id>.discovered_contacts
    • Services:
      • meshcore.add_selected_contact - Add discovered contacts via UI
      • meshcore.remove_selected_contact - Remove contacts via UI
      • meshcore.cleanup_unavailable_contacts - Remove all unavailable contact sensors
    • Immediate Updates: Contact list refreshes immediately on add/remove operations

    ✨ Enhancements

    Channel Improvements

    • Channel Select Entity: Now displays actual channel names instead of "Channel 0"
    • Format: "Name (idx)" e.g., "#pdx (1)", "work (2)"
    • Unused Channels: Display as "(unused) (idx)" when not configured
    • Auto-Update: Channel info refreshes immediately after set_channel commands
    • Documentation: Complete guide on hash-based channel encryption and configuration UI

    Channel Message Service

    • Fix: Now correctly reads channel_idx from channel select entity attributes
    • Previous Issue: Tried to parse channel index from display string
    • Result: Works with new channel name format

    🐛 Bug Fixes

    Reduced Login Packets

    • Fix: Reduced excessive login attempts to repeaters
    • Reason: Login is rarely the failure case in established sessions
    • Impact: Reduces unnecessary mesh network traffic

    Special Characters in Contact Names

    • Fix: Handles names with parentheses correctly (e.g., "Queen Anne (Soon)")
    • Method: Regex-based parsing extracts rightmost parentheses content
    • Centralized: New extract_pubkey_from_selection() utility function

    🔄 Migration Notes

    No breaking changes - all new features are additive. Existing configurations will continue to work without modification.

  14. v2.1.12 # 8 months ago · 2025-10-22 20:05 UTC
    View release ↗

    Add more decimal places to battery sensors Add delay on server startup to avoid corrupting connections Fix bug with repeater settings not persisting

  15. v2.1.11 # 8 months ago · 2025-10-19 03:13 UTC
    View release ↗

    What's Changed

  16. v2.1.10 # 8 months ago · 2025-10-15 15:12 UTC
    View release ↗
    • Adds channel name support. Channel name will now be used in logs and sensors instead of the index
    • Fixes a bug with sensors going stale after an hour if the configured interval was longer than an hour
    • Updates the default refresh interval to be 2 hours
  17. v2.1.9 # 8 months ago · 2025-10-13 19:08 UTC
    View release ↗

    What's Changed

    New Contributors

    Full Changelog: https://github.com/meshcore-dev/meshcore-ha/compare/v2.1.8...v2.1.9

  18. v2.1.8 # 9 months ago · 2025-10-05 18:15 UTC
    View release ↗
    • Improved call spacing to reduce collisions
    • Added more translation keys
    • Added flag to disable path resetting
  19. v2.1.7 # 9 months ago · 2025-10-03 22:48 UTC
    View release ↗

    Reliability Tracking Sensors

    • Request Success/Failure Counters: New sensors track all over-the-wire communication attempts for each monitored node
    • Complete Coverage: Tracks login, status, and telemetry requests for comprehensive network health monitoring
    • Troubleshooting: Identify problematic nodes and routing issues with detailed success/failure metrics

    Flexible Update Intervals

    • Removed Maximum Limits: Update intervals now support unlimited maximums
    • Unified Minimums: Both repeaters and clients use consistent 300-second minimum intervals
    • Better Configuration: Support for very long intervals (hours or days) for low-power scenarios

    Enhanced Failure Handling

    • Smarter Backoff: Dynamic base interval calculation ensures exactly 5 retries fit within configured update windows
    • Faster Path Recovery: Path reset now triggers after 3 failures (was 5) for quicker routing recovery
    • Improved Login Logic: Fixed bug where timeouts/unexpected responses were incorrectly counted as successes

    🐛 Bug Fixes

    • Login Success Detection: Now properly validates login responses instead of treating non-errors as success
    • path reset - fixed an issue where path was not being set my the pubkey prefix arg
  20. v2.1.6 # 9 months ago · 2025-09-28 15:35 UTC
    View release ↗

    What's Changed

    Full Changelog: https://github.com/meshcore-dev/meshcore-ha/compare/v2.1.5...v2.1.6