mirror of
https://github.com/Colorado-Mesh/meshcore-bot-firmware.git
synced 2026-08-11 16:20:29 +00:00
b7cc1dc0ca
- BOT_HOP_STEP_MILLIS_DEFAULT 1500 -> 2500 - BOT_HOP_BIAS_MAX_MILLIS 8000 -> 12000 - BOT_RESPONSE_PENDING_TTL_MILLIS 45000 -> 60000 - BOT_PREFS_VERSION 3 -> 4 (forces re-default of hop_step_ms on existing bots that saved the old 1500 value) - writeAckResponse + executeTest: drop the literal "ack " prefix so test responses now start with "@[sender] ..." Field test showed two bots with token-matching `[1865]` responses both firing because the far bot scheduled its reply before the near bot's reply could propagate back through the mesh. New hop step gives ~5-8 s of margin at the 4-hop boundary.
23 lines
798 B
Diff
23 lines
798 B
Diff
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
|
|
From: cj-vana <cj@depth23.online>
|
|
Date: Fri, 15 May 2026 20:09:58 -0600
|
|
Subject: [PATCH 3/9] Allow prefixless firmware bot DMs
|
|
|
|
---
|
|
examples/companion_radio/BotPolicy.cpp | 2 +-
|
|
1 file changed, 1 insertion(+), 1 deletion(-)
|
|
|
|
diff --git a/examples/companion_radio/BotPolicy.cpp b/examples/companion_radio/BotPolicy.cpp
|
|
index 33de45f8..7d0e6029 100644
|
|
--- a/examples/companion_radio/BotPolicy.cpp
|
|
+++ b/examples/companion_radio/BotPolicy.cpp
|
|
@@ -75,7 +75,7 @@ bool isEmergency(BotChannelKind kind) {
|
|
}
|
|
|
|
bool isPrefixlessCommandAllowed(BotChannelKind kind) {
|
|
- return kind == BOT_CHANNEL_BOT || kind == BOT_CHANNEL_TESTING;
|
|
+ return kind == BOT_CHANNEL_DM || kind == BOT_CHANNEL_BOT || kind == BOT_CHANNEL_TESTING;
|
|
}
|
|
|
|
}
|