adam/Remote-Terminal-for-MeshCore
1
0 Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-10-30 22:41:57 +01:00
Code Issues 26 Packages Projects Releases Wiki Activity

[BUG] Sent messages remain stuck on ? status (no ACK UI update) when using MeshCoreMod firmware #247

New Issue
Closed
opened 2026-10-05 02:05:50 +02:00 by adam · 2 comments
adam commented 2026-10-05 02:05:50 +02:00
Owner
Copy link
Copy source

📝 Problem Description

When sending messages through RemoteTerm chat using MeshCoreMod firmware, sent messages almost never get marked as acknowledged/delivered (remaining stuck with a ? status indicator next to the timestamp). However, the messages are actually being transmitted and received by the mesh network, as recipients receive them and can reply normally.

🚦 Current Behavior

Sent messages remain stuck on the ? status indicator in RemoteTerm instead of updating to a confirmed status (ticks/ACK), even though the recipient successfully receives the message and replies.

🎯 Expected Behavior

Sent messages should update their status indicator once an ACK/confirmation is received from the mesh network, accurately reflecting delivery.

📋 Steps to Reproduce

  1. Connect RemoteTerm to a node running MeshCoreMod.
  2. Send a message in a channel or direct chat.
  3. Observe that the recipient receives the message and replies.
  4. Notice that in RemoteTerm, the sent message status indicator remains on ?.

📡 Radio Node

  • Firmware version: MeshCoreMod 1.16.04 (https://meshcomod.com/)
  • Hardware / board type: Seeed Studio XIAO ESP32S3 (Wio)

🔌 Connection to the Radio

  • Connected directly to the radio, or through an intermediary? Direct connection
  • Transport: Reproducible on both Serial and TCP

💻 Environment Information

  • OS: Chrome OS / Desktop (Chrome Browser)
  • Browser / Version: Google Chrome
  • RemoteTerm Version: v3.17.0·889bb19

📸 Screenshots / Debug Logs

(Attach screenshot showing the ? status next to sent messages despite receiving replies)

Additional context

  • This issue seems isolated to RemoteTerm. Using official/modded Android apps over Bluetooth, Serial, or TCP works as expected and ACKs are displayed correctly.
  • The underlying radio transmission and reception work fine; only the RemoteTerm web UI state update/ACK handling seems affected when paired with MeshCoreMod.
## 📝 Problem Description When sending messages through RemoteTerm chat using MeshCoreMod firmware, sent messages almost never get marked as acknowledged/delivered (remaining stuck with a `?` status indicator next to the timestamp). However, the messages are actually being transmitted and received by the mesh network, as recipients receive them and can reply normally. ## 🚦 Current Behavior Sent messages remain stuck on the `?` status indicator in RemoteTerm instead of updating to a confirmed status (ticks/ACK), even though the recipient successfully receives the message and replies. ## 🎯 Expected Behavior Sent messages should update their status indicator once an ACK/confirmation is received from the mesh network, accurately reflecting delivery. ## 📋 Steps to Reproduce 1. Connect RemoteTerm to a node running MeshCoreMod. 2. Send a message in a channel or direct chat. 3. Observe that the recipient receives the message and replies. 4. Notice that in RemoteTerm, the sent message status indicator remains on `?`. ## 📡 Radio Node - **Firmware version:** MeshCoreMod 1.16.04 (https://meshcomod.com/) - **Hardware / board type:** Seeed Studio XIAO ESP32S3 (Wio) ## 🔌 Connection to the Radio - **Connected directly to the radio, or through an intermediary?** Direct connection - **Transport:** Reproducible on both Serial and TCP ## 💻 Environment Information - **OS:** Chrome OS / Desktop (Chrome Browser) - **Browser / Version:** Google Chrome - **RemoteTerm Version:** v3.17.0·889bb19 ## 📸 Screenshots / Debug Logs *(Attach screenshot showing the `?` status next to sent messages despite receiving replies)* --- **Additional context** - This issue seems isolated to RemoteTerm. Using official/modded Android apps over Bluetooth, Serial, or TCP works as expected and ACKs are displayed correctly. - The underlying radio transmission and reception work fine; only the RemoteTerm web UI state update/ACK handling seems affected when paired with MeshCoreMod. <!-- github-sync-id:4968208264 -->
adam closed this issue 2026-10-05 02:05:50 +02:00
adam commented 2026-10-05 02:05:51 +02:00
Author
Owner
Copy link
Copy source

more info:
Official meshcore app seems to work properly but other apps like kiekr have the same problem.

more info: Official meshcore app seems to work properly but other apps like kiekr have the same problem. <!-- github-comment-id:5078029444 -->
adam commented 2026-10-05 02:05:52 +02:00
Author
Owner
Copy link
Copy source

We do not officially support firmwares beyond the official stock firmware provided by the main MeshCore site -- too many minute issues in other folks' implementations to go whackamole. Acks not appearing are nearly certainly due to the custom firmware not supporting the same kind of packet hooks and listeners that RemoteTerm uses, which the stock firmware does.

We do not officially support firmwares beyond the official stock firmware provided by the main MeshCore site -- too many minute issues in other folks' implementations to go whackamole. Acks not appearing are nearly certainly due to the custom firmware not supporting the same kind of packet hooks and listeners that RemoteTerm uses, which the stock firmware does. <!-- github-comment-id:5080054864 -->
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/Remote-Terminal-for-MeshCore#247