Files
eric 6125130e6a fix(e2e): peer sendText moved to Interface; add RF failure diagnostics
Run 10538 booted the full simulator and ran pytest — both failures were
test-side: the installed meshtastic client moved sendText from Node to the
Interface, and the outbound chunked message never arrived at the peer (cause
still unknown). Fix the sendText call and add in-run diagnostics so the next
failure is self-explaining:

- e2e: outbound-timeout failure now reports what arrived at the peer and the
  simulator log tail; sim now boots with -v (meshtastic debug logging).
- run_e2e.sh: on pytest failure in docker mode, dump per-node meshtasticd
  logs (meshtasticator-nodes.log) before cleanup removes the container.
2026-09-07 21:46:25 -07:00
..
2026-09-07 21:01:21 -07:00

hermes-meshtastic

Meshtastic LoRa mesh gateway platform adapter plugin for Hermes Agent.

Allows bidirectional communication between Hermes AI agent profiles and off-grid Meshtastic nodes (e.g., Heltec V4, T-Beam, LilyGO) over 915 MHz LoRa mesh radio.

Features

  • Connects directly to local Meshtastic radio via TCP (e.g. meshtastic.local:4403).
  • Subscribes to LoRa text messages on designated channel index (e.g. Channel 1 # private with AES-256).
  • Direct Message (1-on-1) routing between Meshtastic Node IDs and Hermes agent sessions.
  • Automatic message chunking and markdown stripping to fit within LoRa RF packet budgets (<180 chars).
  • Automatic reconnection with exponential backoff.