[Bug]: App resends messages although they were received.

[fw190d13]

Contact Details

No response

Checklist

• I am able to reproduce the bug with the latest version.

• I have updated to the latest Alpha firmware, and am able to reproduce the bug. Many issues are fixed quickly in alpha before the general beta release.

• I made sure that there are no existing OPEN or CLOSED issues which I could contribute my information to.

• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.

• This issue contains only one bug.

• I have read and understood the Contribution Guidelines.

• I agree to follow this project's Code of Conduct

• I actually read this list, and should be taken seriously.

Affected app version

2.7.13 and 2.7.14

Affected Android version

Android 13

Affected phone model

Motorola G82 5G

Affected node model

Seed Solar Node

Affected node firmware version

2.7.19

Steps to reproduce the bug

1. Send message
2. Cloud indicating the message was not send appears.
3. The message is being resend automatically 3 times
4. This situation has happened several times as I got screenshots form other users with my messages visible as send 3 times.

Actual behavior

1. The message was delivered in the first, second and third try although the app and note think that it didn't get through.

Expected behavior

If the message was not sent correctly there is an automatic resend. It is difficult to imagine that there were 3 successful sends and the App and node didn't record that. I had this a few times reported to me by other people and had to revert to the 2.7.10 fro f-droid.

Screenshots/Screen recordings

No response

Relevant log output

Additional information

No response

[github-actions]

Please provide the app logs to help diagnose the issue. You can obtain them by going to Settings > Debug > Save Logs in the Meshtastic app, reproducing the problem, and sharing the exported log file. If app logs are insufficient, you can also provide Android logcat output. To do this, connect your phone via USB with USB debugging enabled and run: adb logcat -s Meshtastic:* *:E. Reproduce the problem, then copy and paste the relevant output.

[shortwavesurfer2009]

I was just thinking about this, and I have a question. Are clients or router* able to hear your message? Because if every node that can hear your message is in client mute, then your message will show as not delivered even though it was since client mute does not retransmit.

Edit: Also, a client mute node will show your message as many times as it was transmitted before a client or router hears it. So if it took three tries for a router or client to hear the message, but there's a client mute node that was able to hear it, then your message will be delivered to client that mute node three different times.

[fw190d13]

At the point of sending my node could directly see 1 router ,1 client and, 1 client_base node if memory serves well so all of those should be sufficient to tell me that the message was pushed out.

[shortwavesurfer2009]

At the point of sending my node could directly see 1 router ,1 client and, 1 client_base node if memory serves well so all of those should be sufficient to tell me that the message was pushed out.

Yeah, for sure. Just had to check

[shalberd]

@fw190d13 how many nodes do you have in your mesh and which preset and frequency do you use?

Cloud indicating the message was not send appears.

That does not mean the message did not make it to the first node. The strike-through cloud symbol only means the acknowledgement of the message being received by the first hop node did not make it back to your node.
That is an important difference. Especially in busy meshes or when the RF conditions are not optimal, a message ACK might not make it back to your node.

cloud symbol: message ACK from the first node that got the message and sent acknowledgement back to you

RELAYED = 4 // got an ACK from relay, not destination

https://github.com/meshtastic/firmware/blob/v2.7.22.96dd647/src/MessageStore.h#L52C4-L52C59

strikethrough cloud symbol: no ACK received back from any node that got the message of your node sending it.

https://github.com/meshtastic/firmware/blob/v2.7.22.96dd647/src/MessageStore.h#L51

It is difficult to imagine that there were 3 successful sends and the App and node didn't record that

it has nothing to do with the app. The status comes from the node, I think. It is handled by firmware, the ACKs coming in, or not, as in your situation.

there was a similar issue a while ago that was indeed caused by the app itself resending.

#4354

but the changes were then reverted, so that cannot be it

#4513

I am sure this is not app-related. Instead, it seems to be the default behavior of the firmware:

#4124 (comment)

https://github.com/meshtastic/firmware/blob/v2.7.22.96dd647/src/mesh/ReliableRouter.cpp#L17

maybe @GUVWAF can point here to the code in firmware (MeshService or ReliableRouter or Router) that does the following:

number of retransmissions in the firmware, where we already have 3 retransmissions to begin with. It then also calculates the appropriate delays based on packet length and LoRa settings

[fw190d13]

It depends - around 100-150 online. Currently the region went from MF to SS presets.

The node is on 2.7.19 firmware.

Additionally when clicking the striked cloud I get Error - unrecognized info pop-up on private messages, although the node has a green padlock in my list. Removing the node and waiting to rediscover doesn't help.

[jamesarich]

The node is on 2.7.19 firmware.

have you tested any of the latest alpha builds? app or firmware?