Skip to content

feat(meshcore): sync and apply region_scope (#391)#127

Merged
pskillen merged 3 commits into
mainfrom
api-391/pskillen/region-scope
Jun 3, 2026
Merged

feat(meshcore): sync and apply region_scope (#391)#127
pskillen merged 3 commits into
mainfrom
api-391/pskillen/region-scope

Conversation

@pskillen
Copy link
Copy Markdown
Owner

@pskillen pskillen commented Jun 3, 2026

Summary

  • Include region_scope in mc-channel-sync snapshot entries (null when companion CHANNEL_INFO omits scope).
  • On apply, call set_flood_scope per channel row (active flood scope on companion; last slot wins until operator changes channel in MeshCore app).
  • Follow-up: after apply, merge region_scope from the apply payload onto device read by mc_channel_idx before posting sync (scope_hints), so the API does not create duplicate unscoped rows. log_device_channels always logs scope (or (none)).

Depends on meshflow-api #393 (merge API + migrate first).

Related: meshflow-api #393, meshflow-ui #321

Testing performed

  • pytest test/meshcore/test_channels.py test/test_bot.py

Include region_scope in mc-channel-sync snapshots (null when companion omits
it). Best-effort set_flood_scope on apply when meshcore_py supports it.
Overlay apply payload scope onto device read before mc-channel-sync when
CHANNEL_INFO omits per-channel scope; pass scope_hints through sync paths.
schedule_channel_sync passes scope_hints to sync_channels_to_storage_apis_async;
update radio channel sync regression tests to match.
@pskillen pskillen merged commit d248f29 into main Jun 3, 2026
3 checks passed
@pskillen pskillen deleted the api-391/pskillen/region-scope branch June 3, 2026 15:34
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