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

[T-Deck] Sent messages do not synchronise between Companion app and T-Deck. #98

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

Using MC-Term version 0.9.9 on LilyGO T-Deck plus, together with the companion app connected via WiFi, sent messages in a channel do not synchronise between the MC-Term UI on the T-Deck and the companion app.
(Does not work in both ways: Messages sent from the app do not show on the T-Deck and vice versa.)

Regards!

Using MC-Term version 0.9.9 on LilyGO T-Deck plus, together with the companion app connected via WiFi, sent messages in a channel do not synchronise between the MC-Term UI on the T-Deck and the companion app. (Does not work in both ways: Messages sent from the app do not show on the T-Deck and vice versa.) Regards! <!-- github-sync-id:3960436716 -->
adam closed this issue 2026-10-27 15:38:23 +01:00
adam commented 2026-10-27 15:38:23 +01:00
Author
Owner
Copy link
Copy source

added in v0.9.10!

added in v0.9.10! <!-- github-comment-id:3936609405 -->
adam commented 2026-10-27 15:38:24 +01:00
Author
Owner
Copy link
Copy source

I see with v0.9.10 (connected via BLE to app meshcore-open on GNU/Linux) that message sent from app appears in history on device but not the other way round: Message sent from device does not syncronise with app, even if the app is conected while sending.

I see with v0.9.10 (connected via BLE to app [`meshcore-open`](vhttps://github.com/zjs81/meshcore-open) on GNU/Linux) that message sent from app appears in history on device but not the other way round: Message sent from device does not syncronise with app, even if the app is conected while sending. <!-- github-comment-id:3938957262 -->
adam commented 2026-10-27 15:38:25 +01:00
Author
Owner
Copy link
Copy source

fixed in v0.9.11!
and, fixed GUI-origin channel messages now populate message-detail metadata consistently (route/path hint + timestamp/RSSI baseline), so detail fields are no longer empty compared to companion-origin sends.

fixed in v0.9.11! and, fixed GUI-origin channel messages now populate message-detail metadata consistently (route/path hint + timestamp/RSSI baseline), so detail fields are no longer empty compared to companion-origin sends. <!-- github-comment-id:3939470065 -->
adam commented 2026-10-27 15:38:25 +01:00
Author
Owner
Copy link
Copy source

I see with v0.9.10 (connected via BLE to app meshcore-open on GNU/Linux) that message sent from app appears in history on device

I now used the official MeshCore app on Android, connected via IP ("WiFi"), and when I send a message I immediately see in the app not only the message rendered as a message sent by me, but the message doubled as a received with 63 hops.

Screenshot:

Image

Is this happening due to your change?

Regards!

> *I see with v0.9.10 (connected via BLE to app `meshcore-open` on GNU/Linux) that message sent from app appears in history on device* I now used the official MeshCore app on Android, connected via IP ("WiFi"), and when I send a message I immediately see in the app not only the message rendered as a message sent by me, but the message doubled as a _received_ with 63 hops. Screenshot: --- <img width="1045" height="1819" alt="Image" src="https://github.com/user-attachments/assets/6ef30161-4d75-4b86-a719-c30ba3424d8f" /> --- Is this happening due to your change? Regards! <!-- github-comment-id:4016387912 -->
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#98