8e5b4c97d7
- MeshCore: fix PHY to live narrowband config (869.618/62.5/SF8/CR5),
read off the test node's SELF_INFO — old 869.525/250/SF11 heard nothing
- MeshCore: on-chip Ed25519 identity (rweather/Crypto, NVS-persisted) and
signed ADVERT TX (verified valid + received by a real node) — the bridge
now shows up as a MeshCore contact
- Meshtastic: send text messages (portnum 1) reusing the announce path
- serial TX console with per-network targeting ("T:hi" / bare = all)
- longer dwell (3000ms) to sit through flood-rebroadcast bursts
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
archy-messh
Research + firmware project exploring a single LoRa device that can speak, relay, and repeat between three independent mesh networking protocols:
- Meshtastic
- MeshCore
- Reticulum (via RNode-style modem firmware)
Goal: one ESP32-based device that acts as a tri-protocol repeater/bridge —
not a fork of any single project, and not affiliated with or dependent on
the archy (Archipelago) codebase. This repo is intentionally standalone.
Status
Architecture phase done — see docs/ARCHITECTURE.md for the protocol
research, hardware constraints (target: Heltec WiFi LoRa 32 V3), and
phased plan. Phase 0 (host-side bridge across 3 separate stock-firmware
boards) is written — see host-bridge/ — but not yet hardware-tested; no
LoRa boards have been attached to the dev machine this was written on.
Layout
docs/— protocol research notes and architecture/design docshost-bridge/— Phase 0: Python bridge relaying text between real Meshtastic/MeshCore/RNode-Reticulum boards over each project's official client protocolfirmware/— Phase 1+ embedded firmware (once Phase 0 is validated on hardware)hardware/— reference hardware notes / board selection
Non-goals (for now)
- Not reimplementing any of the three protocols from scratch in v1
- Not targeting non-ESP32 hardware initially
- Not touching/depending on the
archy(Archipelago) repo in any way