Skip to content

companion.cli: run a command on another node over the air - #784

Open
A13xB0 wants to merge 1 commit into
mainfrom
feat-253-companion-cli
Open

A13xB0 wants to merge 1 commit into
mainfrom
feat-253-companion-cli

Conversation

@A13xB0

@A13xB0 A13xB0 commented Oct 24, 2026

Copy link
Copy Markdown
Collaborator

Closes #253.

The MeshCore type is TXT_TYPE_CLI_DATA; there is no TXT_TYPE_CLI_COMMAND. Every firmware already handles it: a repeater runs it for a logged-in admin and replies the same way. This PR only originates it.

  • proto.SendCommandData: CMD_SEND_TXT_MSG with txt_type 1. Inbound messages now record whether they are CLI replies.
  • New verb companion.cli {node, to, command}. It takes at_ms like the other input verbs.
  • companion.state lists the replies as cli_replies.
  • The companion command line gains meshcore-cli's cmd <contact> <command>, and the transcript prints each reply.

Live test (MESHBENCH_LIVE=1), native firmware: a companion hears a repeater's advert, logs in with the default password, sends get name over the air, and reads back > repeater.

companion.cli sends TXT_TYPE_CLI_DATA from a connected companion to a
node it is logged in to; the node runs it and answers in kind. Replies
are kept as CLI messages and listed by companion.state as cli_replies.
The command line gains meshcore-cli's cmd.

Closes #253.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TXT_TYPE_CLI_COMMAND

1 participant