When using my t deck i rely on my repeater being awake when i send a message due to its power management and finding im now sending messages that arnt being pushed forward by the repeater and wondered if you could add a physical button to resend the last message? Im finding that the resend isnt working as it should even when enabled in the messages tab on the management section. A physical button that can be repressed until a user sees the message go on the first hop!
im having to check every message by pressing the sent message to see if my repeater shows at bottom of message maybe a resend button on that page would be amazing
For your consideration
When using my t deck i rely on my repeater being awake when i send a message due to its power management and finding im now sending messages that arnt being pushed forward by the repeater and wondered if you could add a physical button to resend the last message? Im finding that the resend isnt working as it should even when enabled in the messages tab on the management section. A physical button that can be repressed until a user sees the message go on the first hop!
im having to check every message by pressing the sent message to see if my repeater shows at bottom of message maybe a resend button on that page would be amazing
<!-- github-sync-id:4231615902 -->
Maybe even a blue button in the messages tab of the management section to switch the resend button on and off?
ability to switch resend button on and off when needed description and button enabled disabled
and a visible button on the message sent page if a repeater doesnt show up after sending r/s =resend
Maybe even a blue button in the messages tab of the management section to switch the resend button on and off?
ability to switch resend button on and off when needed description and button enabled disabled

and a visible button on the message sent page if a repeater doesnt show up after sending r/s =resend

<!-- github-comment-id:4213702602 -->
> *and a visible button on the message sent page if a repeater doesnt show up after sending*
I would even say have the buton always beeing there. ("Ripple" firmwware has it.) Messages can be repeated but still not reach the destination.
#128 is partly duplicate.
<!-- github-comment-id:4213718370 -->
Because there are similar issues does that mean this request needs to be removed? and agree just because there is a button to be pressed doesnt mean its been sent i totally agree! so is a physical button a good idea instead of relying on auto resend on failure. I also agree the button could be there permanent if the end user can see the message hasnt gone a single push will feed it back through the transmission of that message
Because there are similar issues does that mean this request needs to be removed? and agree just because there is a button to be pressed doesnt mean its been sent i totally agree! so is a physical button a good idea instead of relying on auto resend on failure. I also agree the button could be there permanent if the end user can see the message hasnt gone a single push will feed it back through the transmission of that message
<!-- github-comment-id:4213752345 -->
On Thu, 09 Apr 2026 04:23:26 -0700, BUDDHADECK2 @.***> wrote:
Because there are similar issues does that mean this request needs to
be removed?
I am not really sure how similar the issues are. Let's @dabeani decide.
On Thu, 09 Apr 2026 04:23:26 -0700, BUDDHADECK2
***@***.***> wrote:
> Because there are similar issues does that mean this request needs to
> be removed?
I am not really sure how similar the issues are. Let's @dabeani decide.
<!-- github-comment-id:4215418547 -->
ive highlighted the enhancement the best way i can like you say its up to the dev if he sees the enhancement nessacary going forward
ive highlighted the enhancement the best way i can like you say its up to the dev if he sees the enhancement nessacary going forward
<!-- github-comment-id:4215517193 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For your consideration
When using my t deck i rely on my repeater being awake when i send a message due to its power management and finding im now sending messages that arnt being pushed forward by the repeater and wondered if you could add a physical button to resend the last message? Im finding that the resend isnt working as it should even when enabled in the messages tab on the management section. A physical button that can be repressed until a user sees the message go on the first hop!
im having to check every message by pressing the sent message to see if my repeater shows at bottom of message maybe a resend button on that page would be amazing
Maybe even a blue button in the messages tab of the management section to switch the resend button on and off?
ability to switch resend button on and off when needed description and button enabled disabled
and a visible button on the message sent page if a repeater doesnt show up after sending r/s =resend
I would even say have the buton always beeing there. ("Ripple" firmwware has it.) Messages can be repeated but still not reach the destination.
#128 is partly duplicate.
Because there are similar issues does that mean this request needs to be removed? and agree just because there is a button to be pressed doesnt mean its been sent i totally agree! so is a physical button a good idea instead of relying on auto resend on failure. I also agree the button could be there permanent if the end user can see the message hasnt gone a single push will feed it back through the transmission of that message
On Thu, 09 Apr 2026 04:23:26 -0700, BUDDHADECK2
@.***> wrote:
I am not really sure how similar the issues are. Let's @dabeani decide.
ive highlighted the enhancement the best way i can like you say its up to the dev if he sees the enhancement nessacary going forward