adam/meshcore
1
0 Fork 0
mirror of https://github.com/dabeani/meshcoreterm.git synced 2026-11-02 11:00:32 +01:00
Code Issues 97 Packages Projects Releases Wiki Activity

Sending a private message or message to room: Missing "ACK" information. Message immediately looks like delivered, even if it is not. #128

New Issue
Closed
opened 2026-10-27 15:40:06 +01:00 by adam · 4 comments
adam commented 2026-10-27 15:40:06 +01:00
Owner
Copy link
Copy source

Describe the bug

When I send a private message to a contact or a message to a room, I immediately get returned to the chat view, seeing my message. Regardless weather actually it was successfully delivered or not.

I do not see any information weather an ACK was received or not.

Expected behaviour

Mark weather an ACK was received or not, give status about possible retries, and allow to manually re-send message -- even when in between other views on the device were active.

Which device are you using

LilyGO T-Deck Plus

Which Firmware are you using

v0.9.10

Regards!

**Describe the bug** When I send a private message to a contact or a message to a room, I immediately get returned to the chat view, seeing my message. Regardless weather actually it was successfully delivered or not. I do not see any information weather an ACK was received or not. **Expected behaviour** Mark weather an ACK was received or not, give status about possible retries, and allow to manually re-send message -- even when in between other views on the device were active. **Which device are you using** LilyGO T-Deck Plus **Which Firmware are you using** v0.9.10 Regards! <!-- github-sync-id:3997257143 -->
adam closed this issue 2026-10-27 15:40:06 +01:00
adam commented 2026-10-27 15:40:07 +01:00
Author
Owner
Copy link
Copy source

Same issue in #112

Same issue in #112 <!-- github-comment-id:4067477952 -->
adam commented 2026-10-27 15:40:08 +01:00
Author
Owner
Copy link
Copy source

In firmware version 0.9.11, I still miss the option to re-send a failed message.

Also, for flood routed messages I see "255 hops" in the (not-delivered) message details. But isn't the maximum in MeshCore 63 or 64 hops? Why 255 here?

Regards!

In firmware version 0.9.11, I still miss the option to re-send a failed message. Also, for flood routed messages I see "255 hops" in the (not-delivered) message details. But isn't the maximum in MeshCore 63 or 64 hops? Why 255 here? Regards! <!-- github-comment-id:4113105179 -->
adam commented 2026-10-27 15:40:08 +01:00
Author
Owner
Copy link
Copy source

See also #161.

See also #161. <!-- github-comment-id:4213720048 -->
adam commented 2026-10-27 15:40:09 +01:00
Author
Owner
Copy link
Copy source

Closing since delivery status now is displayed; the left over part of this is now separately opened at #299.

Closing since delivery status now is displayed; the left over part of this is now separately opened at #299. <!-- github-comment-id:4610896349 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#128