Sent direct messages: Sometimes "Path: Direct" and "Zero Hop" is shown even if a 5-hop-path has been negotiated. #211

New Issue

2026-10-27T15:44:03+01:00

adam commented

2026-10-27 15:44:03 +01:00

Describe the bug

Something is still strange with direct message where a path is known.

I wrote a direct message to some contact in my contact list. At first, no path was known, but then one got known and it says "5H" (5 hops) in the contacts list.

Then I wrote a few test messages, after a path got known.

When I tap on the details of the test messages, some show "Zero Hop" and "Path: Direct"; others show "5 Hops" and "Path: 5 hops".

Photographs of all the test messages:

Overview of the messages -- details views in the next photographs:
Test message when there still was flood routing -- first message, which established the path:
Test message when a path was established, with "Mark Delivery Fast" switched on:
Test message when a path was established, with "Mark Delivery Fast" switched off:
Another Test message when a path was established, with "Mark Delivery Fast" switched off:

It seems that the messages that failed to receive an ACK have a wrong path length set.

Also, here it would be helpful if the actual pre-set and really used path could be seen in detail.

Regards!

**Describe the bug** Something is still strange with direct message where a path is known. I wrote a direct message to some contact in my contact list. At first, no path was known, but then one got known and it says "5H" (5 hops) in the contacts list. Then I wrote a few test messages, after a path got known. When I tap on the details of the test messages, some show "Zero Hop" and "Path: Direct"; others show "5 Hops" and "Path: 5 hops". Photographs of all the test messages: --- 0. Overview of the messages -- details views in the next photographs: <img width="1058" height="782" alt="Image" src="https://github.com/user-attachments/assets/0dd5d1f7-307e-47f6-ac51-102fef142716" /> 1. Test message when there still was flood routing -- first message, which established the path: <img width="936" height="725" alt="Image" src="https://github.com/user-attachments/assets/0ac2f45d-577e-4f99-831f-96936106ab42" /> 2. Test message when a path was established, with "Mark Delivery Fast" switched on: <img width="931" height="702" alt="Image" src="https://github.com/user-attachments/assets/a4d26bec-7804-42f6-a36d-cda5c983824b" /> 3. Test message when a path was established, with "Mark Delivery Fast" switched off: <img width="911" height="691" alt="Image" src="https://github.com/user-attachments/assets/a1cae386-aa1e-4401-91c7-2f30daaadc4b" /> 4. Another Test message when a path was established, with "Mark Delivery Fast" switched off: <img width="1029" height="789" alt="Image" src="https://github.com/user-attachments/assets/b8728327-b805-4953-b5b9-c0a856b31176" /> --- It seems that the messages that failed to receive an ACK have a wrong path length set. Also, here it would be [helpful if the actual pre-set and really used path could be seen in detail](https://github.com/dabeani/meshcoreterm/issues/116). Regards!

adam closed this issue

2026-10-27 15:44:03 +01:00

adam commented

2026-10-27 15:44:04 +01:00