From c5312ffce9a1294959b86363bde61ec384431125 Mon Sep 17 00:00:00 2001 From: DrDonoso <34934002+DrDonoso@users.noreply.github.com> Date: Thu, 16 Jan 2025 13:03:57 +0100 Subject: [PATCH] Add message_thread_id to telegram_text and telegram_command events (#35785) --- source/_integrations/telegram_bot.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/telegram_bot.markdown b/source/_integrations/telegram_bot.markdown index 3c66303649f..b847a67bbe4 100644 --- a/source/_integrations/telegram_bot.markdown +++ b/source/_integrations/telegram_bot.markdown @@ -314,6 +314,7 @@ user_id: "" chat_id: "" chat: "" date: "" +message_thread_id: "" ``` Any other message not starting with `/` will be processed as simple text, firing a `telegram_text` event on the event bus with the following `event_data`: @@ -326,6 +327,7 @@ user_id: "" chat_id: "" chat: "" date: "" +message_thread_id: "" ``` If the message is sent from a [press from an inline button](https://core.telegram.org/bots#inline-keyboards-and-on-the-fly-updating), for example, a callback query is received, and Home Assistant will fire a `telegram_callback` event with: