Software

MeshCore on the AIO v2: YAMPA, tui-meshcore and meshcore-uconsole

MeshCore has no Linux-native node firmware, so the community built on pyMC_core: guax's YAMPA packet analyser and TUI chat client, and cwill747's GTK app.

Compatibility
CM4CM5
Difficulty
Easy
Status
Available
Author
guax
Added
Source
ClockworkPi forum

What it takes

  • Software only
  • Config change
  • Purchase required

Difficulty 1 of 3 — easy.

Details

vileer's answer in October 2025 was that MeshCore did not support Linux-native devices; by February 2026 guax had a working stack on the AIO v2's SX1262 through pyMC_core and the pyMC_Repeater project. The board needs two extra lines in the sx1262 section — use_dio3_tcxo: true and use_dio2_rf: true — which interlock has since upstreamed as an AIO v2 preset (pyMC_Repeater PR #99). On top of that: YAMPA (GPLv3), a React front end over a Python WebSocket server started with server.py --radio-type uconsole; tui-meshcore (GPLv3, Textual), pip install -e . then tui-meshcore, for channels and direct messages; and cwill747's meshcore-uconsole, a GTK network analyser with hardware presets that installs from his APT repository as meshcore-uconsole.

All three share the radio, so stop meshtasticd first — LOCOSP's python-periphery errors on a CM5 were exactly that. cwill747 confirms the AIO v1 needs the same two settings.

Open at Forum thread
  • MeshCore
  • LoRa
  • AIO
  • mesh
  • TUI

← Back to Software