Skip to content

Add bulk region hierarchy command to CLI#2540

Draft
agessaman wants to merge 1 commit into
meshcore-dev:devfrom
agessaman:feat/regions-quick-loasd
Draft

Add bulk region hierarchy command to CLI#2540
agessaman wants to merge 1 commit into
meshcore-dev:devfrom
agessaman:feat/regions-quick-loasd

Conversation

@agessaman
Copy link
Copy Markdown
Contributor

Add a new command region bulk for defining region hierarchies in a single line. This command allows users to create multiple regions in a single message. Updated the documentation to include usage examples and detailed parameter descriptions.

The primary use-case here is improving the regions configuration process by requiring fewer command messages to load a full set of regions on a repeater. This has the additional benefit that regions can be configured or reconfigured at multiple hops with more reliability—with region load or region put a dropped message can frustrate or break the configuration process.

Add a new command `region bulk` for defining region hierarchies in a single line. This command allows users to create multiple regions in a single message. Updated the documentation to include usage examples and detailed parameter descriptions.
@AI7NC
Copy link
Copy Markdown
Contributor

AI7NC commented May 12, 2026

This idea has my full support. This will allow much simpler regional loads for repeater operators by condensing in my region 8 load commands into a single command.

@towerviewcams
Copy link
Copy Markdown

8 load commands with many repeaters that I host will create allot of traffic and retry attempts. Anything that can be done to reduce and make this process more efficient should be considered.

@ripplebiz
Copy link
Copy Markdown
Member

I quite like this. A nifty shorthand.
I think 'region def ...' would prob read better than 'bulk'. Plus you get an extra byte! :-)

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.

4 participants