Channel message region override can't seem be set to none #217

Closed
opened 2026-10-05 02:04:06 +02:00 by adam · 3 comments
Owner

When setting the region scope globally on the companion I have found a need for some testing to set the region to none and not use a region at all.

It does not seem possible to set the overwrite to disabling regions/none and can only be set to something else.
Testing with setting a region while the companion is set to no region and setting a custom in a channel works but it would be useful to be able to have the opposite and set the companions region and then specific channels set to none.

When setting the region scope globally on the companion I have found a need for some testing to set the region to none and not use a region at all. It does not seem possible to set the overwrite to disabling regions/none and can only be set to something else. Testing with setting a region while the companion is set to no region and setting a custom in a channel works but it would be useful to be able to have the opposite and set the companions region and then specific channels set to none. <!-- github-sync-id:4730333068 -->
adam closed this issue 2026-10-05 02:04:06 +02:00
Author
Owner

That's a fair complaint; I haven't addressed the inverse of regions. I'll make a special region code for that like [[none]]. Will probably get to that next week or so.

That's a fair complaint; I haven't addressed the inverse of regions. I'll make a special region code for that like `[[none]]`. Will probably get to that next week or so. <!-- github-comment-id:4815270884 -->
Author
Owner

Alrighty this has been handled; rather than the [[none]] goofiness it's a "Always send unscoped" setting in the region override pane. Let me know if you run into any issues.

Alrighty this has been handled; rather than the `[[none]]` goofiness it's a "Always send unscoped" setting in the region override pane. Let me know if you run into any issues. <!-- github-comment-id:4919901529 -->
Author
Owner

Tested and appears to work as advertised. Messages that could not reach a bot when scoped now get though when sent sending to the channel unscoped.

Tested and appears to work as advertised. Messages that could not reach a bot when scoped now get though when sent sending to the channel unscoped. <!-- github-comment-id:4920028134 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#217