Real nodes: drop Meshtastic firmware boards as radios - #8
Merged
Merged
Conversation
A board running stock Meshtastic firmware no longer stands in for a radio (radio.driver meshtastic, the setup and GUI choices, the board radio docs and screenshots). Boards may come back later as an outlet the hosted nodes' bridge pushes through. Kept for hosted nodes: remote identities in the mesh host, the client API client and its fake node, admin forwarding from app clients, and writing name and channel edits to the node. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SJZ75CWob1eMXeTa8Q2nLc
13 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #5. Merges into
epic/real-nodes.What
Removes boards running stock Meshtastic firmware as radios, added in #7:
radio.driver: meshtasticand its validation;A board may come back later as an outlet for the hosted nodes' bridge: the bridge will push frames through an interface, with our KISS/HAT radio as the first outlet and a board (over its MQTT client proxy or UDP multicast) as a possible later one, carrying hosted nodes one hop behind it.
Kept
These are what hosted nodes (the next child PRs) build on:
mesh;internal/mtclientandmtclient/mtclienttest;real_nodeflag, now labelled meshtasticd.Testing
go vet ./...andgo test ./...pass; the GUI type-checks and builds.🤖 Generated with Claude Code
https://claude.ai/code/session_01SJZ75CWob1eMXeTa8Q2nLc