d731bfd7fa
The device now transmits a NodeInfo (User protobuf: id/long_name/short_name) on the LongFast primary channel every 60s, so it appears in other Meshtastic clients as 'Reticutasticore' / 'RTC'. NodeNum derived from the MAC (!4359d2d0). No public key advertised, so DMs to us fall back to channel encryption — which the existing RX path already decodes and displays. Confirmed on hardware: announce tx=0 (success) on the first T-window. Also spec the planned message-received animation (upside-down spinning smiley + lightning bolts -> Meshtastic-style modal) in the README. 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