[BUG] 4.15.1 MeshCore setting regions to channels?

[kokoshell]

Hi Yeraze,

Is there any way to set/unset region scope to #hashtag channels like on the phone app ?
And region to be displayed next to channel name ?
I noticed that if region scopes are set to #hashtag channels on the phone app,
cant see/send messages any longer on those channels from Meshmonitor app ! (TCP connection).

Best regards,
Kokoshell

[Yeraze]

Hi @kokoshell — thanks for the report. This isn't a duplicate of an existing open/closed issue, so let's dig in.

1. Setting region/scope on a channel — this already exists

MeshMonitor does support setting a region/scope per channel, including for #hashtag public channels:

Configuration → Channels → (edit the channel) → "Region / Scope (optional)"

That field accepts a plain region name (no leading #) and offers a datalist of previously-used region names. There's also a source-wide default scope (used when a channel has no scope of its own) under the MeshCore source settings, and a per-message one-off scope override right in the message compose box in the Channels view (the "Scope: …" toggle above the send box), which is handy for a single message without changing the channel's normal scope.

2. Why setting the region on the phone app alone breaks sending/receiving from MeshMonitor

This is the important part, and it's a MeshCore protocol characteristic rather than a MeshMonitor bug: region/scope is not stored on the device as part of the channel definition. There's no "scope" field in the MeshCore Companion channel struct — GetChannel/SetChannel only carry name + secret. Instead, scope is a single global "flood scope" setting on the device that each client app re-asserts right before it sends (MeshMonitor does this via a set_flood_scope bridge command keyed off the channel you're sending on).

The consequence: MeshMonitor and the official phone app each track their own, independent idea of "what scope does channel X use." Nothing syncs that between apps or persists it on the node itself. So if you set a region on #hashtag channels in the phone app, but MeshMonitor's own channel row still has an empty scope, MeshMonitor will assert unscoped on the device right before every send on that channel — and if any nearby repeaters are configured region denyf * (deny-by-default, only forward listed regions), that unscoped traffic gets silently dropped. The same mismatch explains the receive side too, since it's the same repeaters not relaying either direction.

Fix (no code change needed): In MeshMonitor, edit that same channel under Configuration → Channels and set "Region / Scope" to the exact same region name you configured in the phone app (case-sensitive, no #). Once both apps assert the same scope before sending, the repeaters should forward normally again.

Could you confirm:

• The exact region name you set in the phone app for these channels?
• Whether you've set that same name in MeshMonitor's Channels config for the affected channel(s)?

If you try that and it's still broken, please let me know and I'll take another look — that would point to an actual bug rather than a config mismatch.

3. "Region displayed next to channel name"

Today, scope is shown per-message in the chat stream (a small badge next to each message that carried one) and in the compose box's "Scope: …" indicator, but not next to the channel name in the channel list itself. That's a reasonable small enhancement — let me know if you'd like me to open that as a separate feature request, or if the per-message/compose-box display already covers what you need.

-- Authored by Roger 🤓

---

Generated by Claude Code

[Yeraze]

@kokoshell any updates here?

[Yeraze]

Closing due to no response