Try sending a DM again if it wasn't received #49

New Issue

2026-10-05T01:17:56+02:00

adam commented

2026-10-05 01:17:56 +02:00

On iOS I get an acknowledgment letting me know that the node actually got the message I sent. If that doesn't happen then could the bot try again

Here's an example of a successful send to read message #3 but I had to do it twice because it got lost in the network

On iOS I get an acknowledgment letting me know that the node actually got the message I sent. If that doesn't happen then could the bot try again Here's an example of a successful send to read message #3 but I had to do it twice because it got lost in the network ![Image](https://github.com/user-attachments/assets/59bd20d3-31a3-4511-829a-ca675320dbed)

adam closed this issue

2026-10-05 01:17:56 +02:00

adam commented

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

Yes this is a problem with meshtastic network. There isn't a good way to deliver with confirmations.

Ack is only as good as the free airtime. Which isn't ideal at all.

A feature like this can easily further degrade the network, it's a good idea but I fear it would be a serious problem overall due to network architecture outside the scope of the bot.

Additionally just because you asked don't mean it was actually received, further complicating this is if there are hops it would further degrade the network for all.

Yes this is a problem with meshtastic network. There isn't a good way to deliver with confirmations. Ack is only as good as the free airtime. Which isn't ideal at all. A feature like this can easily further degrade the network, it's a good idea but I fear it would be a serious problem overall due to network architecture outside the scope of the bot. Additionally just because you asked don't mean it was actually received, further complicating this is if there are hops it would further degrade the network for all.

adam commented

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

Would there be a way to log the ack back? This case was a zero hop; bot and node are in the same house. Maybe try again if hops are zero?

Would there be a way to log the ack back? This case was a zero hop; bot and node are in the same house. Maybe try again if hops are zero?

adam commented

2026-10-05 01:17:58 +02:00

you can turn on ACK in settings.ini it's not by default. but I am not processing any extra wait or hold today for a demanded response. could be interesting to record that value and consider it unsent for mail.. I need to look to see if there is good ways to handle it in the API.

you can turn on ACK in settings.ini it's not by default. but I am not processing any extra wait or hold today for a demanded response. could be interesting to record that value and consider it unsent for mail.. I need to look to see if there is good ways to handle it in the API.

adam commented

2026-10-05 01:17:59 +02:00

Checking to see, did enable

Request Acknowledgement of message OTA
wantAck = True

Solve the issue for you?

Checking to see, did enable Request Acknowledgement of message OTA wantAck = True Solve the issue for you?

adam commented

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

Request for ACK but I don't see it in the logs

![Image](https://github.com/user-attachments/assets/3b3ff172-fdba-450f-a1c8-34d3f6f838eb) Request for ACK but I don't see it in the logs

adam commented

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

Ahh sorry, I added confusion here yea I get ya, the wait time for the ack can be costly hangs the app. But for mail might be worth it

Ahh sorry, I added confusion here yea I get ya, the wait time for the ack can be costly hangs the app. But for mail might be worth it

adam commented

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

currently there is not an ideal way to manage this with API/firmware that I know of

currently there is not an ideal way to manage this with API/firmware that I know of

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/meshing-around#49