M5 acceptance: two devices, messages both ways #38

New Issue

2026-10-05T20:07:23Z

twisla commented

2026-10-05 20:07:23 +00:00

What

The test that closes M5, with the reference node (#22) running stock Meshtastic: this firmware and stock firmware talk to each other, both ways, and the result is written into docs/milestones/M5.md.

To do

A text on the default Channel from the Cardputer shows in the Meshtastic phone app, and the other way round.
A Direct Message each way, acknowledged.
Our node info, names and position (when shared) show correctly on the reference node.
A second Channel with a private key: the same, and nothing readable on the default one.
With a third Node if there is one: a message relayed by the Cardputer, and one relayed for it.
The Duty Cycle Budget holds under a burst of messages.
A range walk: how far the two still talk, each way. A figure for #20.
A Capture of all of it, kept as fixtures.

## What The test that closes M5, with the reference node (#22) running stock Meshtastic: this firmware and stock firmware talk to each other, both ways, and the result is written into `docs/milestones/M5.md`. ## To do 1. A text on the default Channel from the Cardputer shows in the Meshtastic phone app, and the other way round. 2. A Direct Message each way, acknowledged. 3. Our node info, names and position (when shared) show correctly on the reference node. 4. A second Channel with a private key: the same, and nothing readable on the default one. 5. With a third Node if there is one: a message relayed by the Cardputer, and one relayed for it. 6. The Duty Cycle Budget holds under a burst of messages. 7. A range walk: how far the two still talk, each way. A figure for #20. 8. A Capture of all of it, kept as fixtures. ## Related #22, #34, #35, #36, #33, #37, #32, #20.

twisla added this to the M5 Mesh transmit milestone 2026-10-05 20:07:23 +00:00

twisla added the

labels 2026-10-05 20:07:23 +00:00

twisla added a new dependency 2026-10-05 20:07:24 +00:00

#22 Hardware: a reference Meshtastic node