Fixed
Commands silently dropped in multi-bot groups
Closes #21. Reported by @famewolf.
A v1.18.2 regression: registering all commands via setMyCommands triggered Telegram's standard group-multi-bot-disambiguation. In a group with ≥ 2 bots (the v1.17.3 BOT_LABEL multi-host setup), tapping /check in the autocomplete picker actually sent /check@dockmox-bot. Our _handle_message matches by text == "/check" everywhere — the @botname form fell through and got silently dropped.
| Phase | Behaviour |
|---|---|
| Before v1.18.2 | Picker empty → users typed /check manually → matches
|
| v1.18.2 → v1.18.4 | Picker populated → tap → text="/check@bot" → silent drop
|
| v1.18.5 onward | @botname stripped at the entry of _handle_message → all 19 commands route correctly
|
Affected every multi-bot-group user. 1:1 chats were unaffected.
Implementation
5-line normalize at the top of _handle_message. Only touches the first token (the command), so user mentions later in the payload (e.g. /notify @someone hello) are preserved. All 19 commands inherit the fix automatically — no per-command changes. 10-case unit test verified before commit.
docker pull amayer1983/docksentry:latest
docker compose up -d