Route command replies through respond() — same channel, threaded quote (v0.18.1) #39

Merged
kamilkrzywda merged 1 commits from fix/command-replies-respond into main 2026-09-25 19:32:32 +02:00
Owner

Owner request: "you should use our response function for this pong! we should keep same channel".

CommandService replies now go through MeshService.respond(id, reply) when the trigger has a packet id — the reply rides the original message's channel and is threaded (replyId = messageId). COMMAND_CHANNEL stays as the listen/trigger gate only; legacy sendText on COMMAND_CHANNEL remains solely as the no-id fallback. Failure handling unchanged (warn-only).

  • e2e over fake bridge: ch2 broadcast #ping → broadcast #pong! with replyId set; ch2 DM → DM to sender, same channel, replyId set
  • tests 121 → 124, build + oxlint clean
  • docs updated (AGENTS.md, MESHTASTIC.md), changelog v0.18.1, package.json bump

Commit: 9d4c959

Owner request: "you should use our response function for this pong! we should keep same channel". CommandService replies now go through MeshService.respond(id, reply) when the trigger has a packet id — the reply rides the original message's channel and is threaded (replyId = messageId). COMMAND_CHANNEL stays as the listen/trigger gate only; legacy sendText on COMMAND_CHANNEL remains solely as the no-id fallback. Failure handling unchanged (warn-only). - e2e over fake bridge: ch2 broadcast #ping → broadcast #pong! with replyId set; ch2 DM → DM to sender, same channel, replyId set - tests 121 → 124, build + oxlint clean - docs updated (AGENTS.md, MESHTASTIC.md), changelog v0.18.1, package.json bump Commit: 9d4c959
kamilkrzywda added 1 commit 2026-09-25 19:32:26 +02:00
kamilkrzywda merged commit 55e59d4963 into main 2026-09-25 19:32:32 +02:00
kamilkrzywda deleted branch fix/command-replies-respond 2026-09-25 19:32:32 +02:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: OpenCode/MeshBot#39