Feature request: per-channel region scopes #16

New Issue

2026-10-05T01:52:47+02:00

adam commented

2026-10-05 01:52:47 +02:00

Different channels may require different scopes - as it is the case in my region.... we have local channels with narrow scope and some more wider channels with more wider scope.

On official companion apps it is already possible to select a different scope for each channel.

Different channels may require different scopes - as it is the case in my region.... we have local channels with narrow scope and some more wider channels with more wider scope. On official companion apps it is already possible to select a different scope for each channel.

adam closed this issue

2026-10-05 01:52:47 +02:00

adam commented

2026-10-05 01:52:48 +02:00

I will work on that later this week -- currently spending most of my time on the multibyte pathing updates but I'll add that to the backlog :)

I will work on that later this week -- currently spending most of my time on the multibyte pathing updates but I'll add that to the backlog :)

adam commented

2026-10-05 01:52:49 +02:00

Hm, interesting, I dug in a bit more and the firmware doesn't support channel scoping as far as I can see; I'm wondering if they're just doing a trick to set the global flood scope, sending a message, and flipping it back. I'd need to see what the app is actually doing on the wire to confirm, which will be a bit more of an investigation project.

A flip-flop like that MIGHT work except for the bot logic we have in the app which can send responses in the background. I might be able to get creative with some locking and make scope-set/send/scope-set-back atomic.

Hm, interesting, I dug in a bit more and the firmware doesn't support channel scoping as far as I can see; I'm wondering if they're just doing a trick to set the global flood scope, sending a message, and flipping it back. I'd need to see what the app is actually doing on the wire to confirm, which will be a bit more of an investigation project. A flip-flop like that MIGHT work except for the bot logic we have in the app which can send responses in the background. I might be able to get creative with some locking and make scope-set/send/scope-set-back atomic.

adam commented

2026-10-05 01:52:49 +02:00

Good luck :-)

In app it is like this: there is a list of possible scopes where you can add / remove scopes. And then you can select the currently active scope for each channel seperately.

Good luck :-) In app it is like this: there is a list of possible scopes where you can add / remove scopes. And then you can select the currently active scope for each channel seperately.

adam commented

2026-10-05 01:52:50 +02:00

This is Mr. Cottle's app you're referring to, I assume?

This is Mr. Cottle's app you're referring to, I assume?

adam commented

2026-10-05 01:52:51 +02:00

Yes, exactly.

Yes, exactly.

adam commented

2026-10-05 01:52:52 +02:00

I'm about to push up a branch that supports this. Please consider it experimental, and let me know if you run into any issues. Clicking the globe icon in a channel header will let you set regional routing scope. Note that this will significantly increase message send time as sending gains two more operations during the radio access lock. If you run a significant number of bots, this may cause some backpressure.

I'm about to push up a branch that supports this. Please consider it experimental, and let me know if you run into any issues. Clicking the globe icon in a channel header will let you set regional routing scope. Note that this will significantly increase message send time as sending gains two more operations during the radio access lock. If you run a significant number of bots, this may cause some backpressure.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

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