Auto resend "No echoes heard" messages #108

New Issue

2026-10-05T01:57:32+02:00

adam commented

2026-10-05 01:57:32 +02:00

We have manual button to resend message with 2 options.
"Resend only for new repeaters" and "Resend as new". My suggestion is to add in options-messaging check mark to autoresend ( 2 or 3 times) only for new repeaters.Not resend new, no resend heard already, not abuse mesh net. For example add 2-3 sec delay for waiting echo, and if it not heard, "soft" resend message in 30 sec time window.
In my area i have one strong own 1W Repeater with yagi antenna pointing to others. And a wifi companion sitting near router about 10 meters away from Rep. And 3 of 10 messages not hearing at first type even from my Rep because he is transmitting flood at that exact( half duplex ) time when i send msg from web. My msg shows question mark. Other reps cant hear me.
Idk how to fix this. 2th local repeater with custom tx.time.delay?) good, but it can be fix with web client, i think.
Is it okay for you to implement this feature? Thanks

We have manual button to resend message with 2 options. "Resend only for new repeaters" and "Resend as new". My suggestion is to add in options-messaging check mark to autoresend ( 2 or 3 times) only for new repeaters.Not resend new, no resend heard already, not abuse mesh net. For example add 2-3 sec delay for waiting echo, and if it not heard, "soft" resend message in 30 sec time window. In my area i have one strong own 1W Repeater with yagi antenna pointing to others. And a wifi companion sitting near router about 10 meters away from Rep. And 3 of 10 messages not hearing at first type even from my Rep because he is transmitting flood at that exact( half duplex ) time when i send msg from web. My msg shows question mark. Other reps cant hear me. Idk how to fix this. 2th local repeater with custom tx.time.delay?) good, but it can be fix with web client, i think. Is it okay for you to implement this feature? Thanks

adam closed this issue

2026-10-05 01:57:32 +02:00

adam commented

2026-10-05 01:57:33 +02:00

Yeah that's reasonable; I have played with the idea of adding an auto-resend opt-in. It's a little tricky from an async-perspective without threading a bunch of stuff all over the place. I'll have a think on how this could be done reasonable.

Yeah that's reasonable; I have played with the idea of adding an auto-resend opt-in. It's a little tricky from an async-perspective without threading a bunch of stuff all over the place. I'll have a think on how this could be done reasonable.

adam commented

2026-10-05 01:57:34 +02:00

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#108