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

Cannot send DM's between two T-Decks #31

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

Describe the bug
I try to send a DM from one T-Deck to another T-Deck. Both are running v8.
I tried from the T-Deck itself and from the companion app on Android (connected over Bluetooth).
Group messages work fine.
Setting a fixed path via my own repeater does not resolve it.
The devices

Which device are you using*
LilyGO T-Deck Plus

To Reproduce
Steps to reproduce the behavior:

  1. Go to Contacts
  2. Click on the contact you want to send a DM (direct message) to
  3. Send either a predetermined "custom message" with Custom or send your own message with Send
  4. The message is not received on the other device
  5. When trying the above steps on the companion app (Android, connected over bluetooth) you can see that the message fails after 5 retries.

Additional context
I was able to check more elaborate debug logs via the Android companion app. I've marked the lines I think are relevant in italics:

[...]
[21:42:47] [Connection] onFrameReceived: responseCode=136, length=60
[21:42:49] [Connection] onFrameReceived: responseCode=13, length=80
[21:42:49] [Connection] onFrameReceived: responseCode=6, length=10
[21:42:50] [AckCodeManager] rememberContactMessageAckCode: contactMessageId=20, expectedAckCode=4157027172
[21:42:51] [Connection] onFrameReceived: responseCode=136, length=26
[21:42:56] [Connection] onFrameReceived: responseCode=136, length=48
[21:42:57] [Connection] onFrameReceived: responseCode=6, length=10
[21:42:57] [AckCodeManager] rememberContactMessageAckCode: contactMessageId=20, expectedAckCode=3127344891
[21:42:58] [Connection] onFrameReceived: responseCode=136, length=26
[21:43:00] [Connection] onFrameReceived: responseCode=5, length=72
[21:43:00] [ConnectionManager] setCurrentSelfInfo: DiscoSnail🐌
[21:43:00] [Connection] onFrameReceived: responseCode=13, length=80
[21:43:00] [Connection] onFrameReceived: responseCode=12, length=11
[21:43:03] [Connection] onFrameReceived: responseCode=136, length=54
[21:43:04] [Connection] onFrameReceived: responseCode=0, length=1
[21:43:04] [Connection] onFrameReceived: responseCode=3, length=148
[21:43:04] [Connection] onFrameReceived: responseCode=6, length=10
[21:43:04] [AckCodeManager] rememberContactMessageAckCode: contactMessageId=20, expectedAckCode=109276560
[21:43:05] [Connection] onFrameReceived: responseCode=136, length=26
[21:43:11] [Connection] onFrameReceived: responseCode=136, length=55
[21:43:11] [Database] setMessageFailedById: id=20
[21:43:19] [Connection] onFrameReceived: responseCode=12, length=11
[21:43:26] [Connection] onFrameReceived: responseCode=136, length=144
[21:43:30] [Connection] onFrameReceived: responseCode=136, length=60
[21:43:31] [Connection] onFrameReceived: responseCode=131, length=1
[21:43:31] [Connection] onFrameReceived: responseCode=17, length=45
[21:43:31] [Connection] onFrameReceived: responseCode=10, length=1
[21:43:32] [Connection] onFrameReceived: responseCode=136, length=65
[...]

**Describe the bug** I try to send a DM from one T-Deck to another T-Deck. Both are running v8. I tried from the T-Deck itself and from the companion app on Android (connected over Bluetooth). Group messages work fine. Setting a fixed path via my own repeater does not resolve it. The devices **Which device are you using*** LilyGO T-Deck Plus **To Reproduce** Steps to reproduce the behavior: 1. Go to `Contacts` 2. Click on the contact you want to send a DM (direct message) to 3. Send either a predetermined "custom message" with `Custom` or send your own message with `Send` 4. The message is not received on the other device 5. When trying the above steps on the companion app (Android, connected over bluetooth) you can see that the message fails after 5 retries. **Additional context** I was able to check more elaborate debug logs via the Android companion app. I've marked the lines I think are relevant in _italics_: [...] [21:42:47] [Connection] onFrameReceived: responseCode=136, length=60 [21:42:49] [Connection] onFrameReceived: responseCode=13, length=80 [21:42:49] [Connection] onFrameReceived: responseCode=6, length=10 _[21:42:50] [AckCodeManager] rememberContactMessageAckCode: contactMessageId=20, expectedAckCode=4157027172_ [21:42:51] [Connection] onFrameReceived: responseCode=136, length=26 [21:42:56] [Connection] onFrameReceived: responseCode=136, length=48 [21:42:57] [Connection] onFrameReceived: responseCode=6, length=10 _[21:42:57] [AckCodeManager] rememberContactMessageAckCode: contactMessageId=20, expectedAckCode=3127344891_ [21:42:58] [Connection] onFrameReceived: responseCode=136, length=26 [21:43:00] [Connection] onFrameReceived: responseCode=5, length=72 _[21:43:00] [ConnectionManager] setCurrentSelfInfo: DiscoSnail🐌_ [21:43:00] [Connection] onFrameReceived: responseCode=13, length=80 [21:43:00] [Connection] onFrameReceived: responseCode=12, length=11 [21:43:03] [Connection] onFrameReceived: responseCode=136, length=54 [21:43:04] [Connection] onFrameReceived: responseCode=0, length=1 [21:43:04] [Connection] onFrameReceived: responseCode=3, length=148 [21:43:04] [Connection] onFrameReceived: responseCode=6, length=10 _[21:43:04] [AckCodeManager] rememberContactMessageAckCode: contactMessageId=20, expectedAckCode=109276560_ [21:43:05] [Connection] onFrameReceived: responseCode=136, length=26 [21:43:11] [Connection] onFrameReceived: responseCode=136, length=55 _[21:43:11] [Database] setMessageFailedById: id=20_ [21:43:19] [Connection] onFrameReceived: responseCode=12, length=11 [21:43:26] [Connection] onFrameReceived: responseCode=136, length=144 [21:43:30] [Connection] onFrameReceived: responseCode=136, length=60 [21:43:31] [Connection] onFrameReceived: responseCode=131, length=1 [21:43:31] [Connection] onFrameReceived: responseCode=17, length=45 [21:43:31] [Connection] onFrameReceived: responseCode=10, length=1 [21:43:32] [Connection] onFrameReceived: responseCode=136, length=65 [...] <!-- github-sync-id:3839904865 -->
adam closed this issue 2026-10-27 15:35:06 +01:00
adam commented 2026-10-27 15:35:07 +01:00
Author
Owner
Copy link
Copy source

i released now v0.9.4 which should solve this bug - keep me updated!

i released now v0.9.4 which should solve this bug - keep me updated! <!-- github-comment-id:3781510534 -->
adam commented 2026-10-27 15:35:08 +01:00
Author
Owner
Copy link
Copy source

Not yet working on 0.9.4 after purging contacts and re-adding with 0-hop advert, but I will test some more.

Edit: found the issue: there was a duplicate entry with an old public key in one of the devices. After purging all contacts on both devices and doing a 0-hop advert I can message between the devices again :)

Not yet working on 0.9.4 after purging contacts and re-adding with 0-hop advert, but I will test some more. Edit: found the issue: there was a duplicate entry with an old public key in one of the devices. After purging all contacts on both devices and doing a 0-hop advert I can message between the devices again :) <!-- github-comment-id:3781664778 -->
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#31