Skip to content

feat(cli): try confirm-or-revert prefs - #3358

Draft
benallfree wants to merge 1 commit into
meshcore-dev:devfrom
MeshEnvy:feature/cli-try
Draft

feat(cli): try confirm-or-revert prefs#3358
benallfree wants to merge 1 commit into
meshcore-dev:devfrom
MeshEnvy:feature/cli-try

Conversation

@benallfree

@benallfree benallfree commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Hey guys this is a draft PR for visibility only, curious to hear what everyone thinks.

I've been experimenting with some meshcore settings having to do with radio RX and got to wondering how I would get the node back if the RX setting caused it to go deaf.

My generalized solution/proposal is a try command that will flip a setting back after a timeout unless it is committed with set. And to avoid footguns, you can also use try reboot which will reboot the device after reverting the setting. Some settings auto-arm reboot to further avoid footguns.

Sample commands:

# Start a 1-hour rxgain trial (reverts unless you commit)
try 3600 radio.rxgain off

# Same, but reboot after timeout revert (optional keyword)
try reboot 3600 radio.rxgain off

# Radio 4-tuple trial (reboot armed on revert is inherited; apply still needs manual reboot)
try 3600 radio 915.0,250,11,5

# Powersaving is a bare verb, not set powersaving
try 1800 powersaving on

# List pending trials (key, trial value, seconds left, reboot suffix if armed)
get try

# Commit before timeout (cancels revert for that key)
set radio.rxgain off

# Snapshot current value (what try would revert to)
get radio.rxgain

# Short bench run
try 10 radio.rxgain off
get try
# wait ~10s, then:
get radio.rxgain
get try

Co-authored-by: Cursor <cursoragent@cursor.com>
@LitBomb

LitBomb commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

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.

2 participants