Telegram bot by mirkokurt · Pull Request #48 · arduino/app-bricks-py

mirkokurt · 2026-01-12T11:05:13Z

This PR adds the Telegram Bot Brick, a brick designed to create you own Telegram bot.

Copilot

Pull request overview

This PR introduces a new Telegram Bot Brick that enables developers to create and manage Telegram bots through the Arduino app bricks framework. The brick provides methods for registering commands, handling text and photo messages, sending messages, and running the bot's polling loop.

Changes:

Added TelegramBot class with command/message handler registration and message sending capabilities
Added python-telegram-bot dependency (version >=21.1) to pyproject.toml
Created brick configuration file specifying TELEGRAM_BOT_TOKEN environment variable

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
src/arduino/app_bricks/telegram_bot/telegram_bot.py	Core TelegramBot class implementing bot initialization, handler registration, and message sending
src/arduino/app_bricks/telegram_bot/brick_config.yaml	Configuration file defining brick metadata and required environment variables
src/arduino/app_bricks/telegram_bot/init.py	Module initialization exporting TelegramBot and telegram library components
src/arduino/app_bricks/telegram_bot/README.md	Placeholder documentation file (currently only contains title)
pyproject.toml	Dependency configuration adding python-telegram-bot to the telegram_bot optional dependency group

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

src/arduino/app_bricks/telegram_bot/telegram_bot.py

Copilot · 2026-01-12T11:10:09Z

src/arduino/app_bricks/telegram_bot/README.md

@@ -0,0 +1 @@
+# Telegram Bot Brick


The README.md file only contains a title and no actual documentation. Other bricks in this codebase (e.g., MQTT) include comprehensive documentation with usage examples, code snippets, and explanations. This brick should follow the same pattern and include proper documentation on how to use the TelegramBot class, including examples of registering commands, handling messages, and sending messages.

src/arduino/app_bricks/telegram_bot/telegram_bot.py

Copilot · 2026-01-12T11:10:09Z

src/arduino/app_bricks/telegram_bot/telegram_bot.py

+@brick
+class TelegramBot:
+    """A brick to manage Telegram Bot interactions."""
+
+    def __init__(self, token: str = None):
+        """Initialize the bot with a token from arg or environment variable."""
+        self.token = token or os.getenv("TELEGRAM_BOT_TOKEN")
+        if not self.token:
+            raise ValueError("Telegram BOT_TOKEN must be provided or set as environment variable")
+
+        self.application = Application.builder().token(self.token).build()
+
+    def add_command(self, command: str, callback):
+        """Register a slash command (e.g., /start)."""
+        self.application.add_handler(CommandHandler(command, callback))
+
+    def on_text(self, callback):
+        """Register a handler for text messages."""
+        self.application.add_handler(MessageHandler(filters.TEXT & ~filters.COMMAND, callback))
+
+    def on_photo(self, callback):
+        """Register a handler for photo messages."""
+        self.application.add_handler(MessageHandler(filters.PHOTO & ~filters.COMMAND, callback))
+
+    def send_message(self, chat_id: int, message_text: str):
+        """Send a message to a specific chat ID."""
+        logger.info(f"Sending message to chat_id={chat_id if chat_id != 0 else self.chat_id}")
+        url = f"https://api.telegram.org/bot{self.token}/sendMessage"
+        payload = {
+            "chat_id": chat_id,
+            "text": message_text
+        }
+        try:
+            response = requests.post(url, data=payload)
+            response.raise_for_status()   
+            logger.info("Message sent successfully!")
+            return response
+        except requests.exceptions.RequestException as e:
+            logger.error(f"An error occurred: {e}")
+            return None
+
+    def run(self):
+        """Start the Telegram polling loop."""
+        logger.info("Telegram Bot starting...")
+        self.application.run_polling(allowed_updates=Update.ALL_TYPES)


The TelegramBot class lacks test coverage. Other bricks in this repository (such as MQTT, web_ui, wave_generator, etc.) have comprehensive test suites. Tests should be added to cover initialization, command registration, message handlers, send_message functionality, and the run method to maintain consistency with the testing standards of this codebase.

src/arduino/app_bricks/telegram_bot/telegram_bot.py

rjtokenring · 2026-01-12T15:50:06Z

src/arduino/app_bricks/telegram_bot/telegram_bot.py

+            logger.error(f"An error occurred: {e}")
+            return None
+
+    def run(self):


Why run()?
This is a brick: shouldn't you need to use the start()/stop() functions?

rjtokenring · 2026-01-12T15:50:44Z

src/arduino/app_bricks/telegram_bot/brick_config.yaml

+description: A brick to interact with Telegram Bot API
+variables:
+- name: TELEGRAM_BOT_TOKEN
+  description: Telegram Bot Token


We need to add the mandatory flag

rjtokenring · 2026-01-12T15:51:10Z

src/arduino/app_bricks/telegram_bot/README.md

@@ -0,0 +1 @@
+# Telegram Bot Brick


Please add a simple example in examples/ folder

robgee86 · 2026-01-13T23:37:17Z

src/arduino/app_bricks/telegram_bot/telegram_bot.py

+        """Register a handler for photo messages."""
+        self.application.add_handler(MessageHandler(filters.PHOTO & ~filters.COMMAND, callback))
+
+    async def send_message(self, chat_id: int, message_text: str):


We generally don't expose async APIs to the user, otherwise the user would have to make the application an async one and use asyncio due to an implementation detail on our side.
Could you make send_message a blocking method?

src/arduino/app_bricks/telegram_bot/telegram_bot.py

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

…deo and docs

mirkokurt requested review from Copilot, robgee86 and stefanotorneo January 12, 2026 11:05

Copilot started reviewing on behalf of mirkokurt January 12, 2026 11:06 View session

Copilot AI reviewed Jan 12, 2026

View reviewed changes

rjtokenring reviewed Jan 12, 2026

View reviewed changes

robgee86 reviewed Jan 13, 2026

View reviewed changes

dsammaruga added the applab-0.6 PR toward release-0.6 branch label Feb 2, 2026

dsammaruga changed the base branch from release-1.1 to release-0.6 February 9, 2026 15:37

dsammaruga force-pushed the telegram-bot branch from 9abf082 to 5a127a8 Compare February 9, 2026 16:47

rjtokenring force-pushed the release-0.6 branch from df09cd5 to 6ebc1e2 Compare February 11, 2026 13:30

mirkokurt and others added 16 commits February 12, 2026 20:50

Add a Telegram bot brick

ae740c8

Add ContextTypes

8066a23

Add synchronous send message

8c16202

Use the library async send message

ad8e7c2

Update src/arduino/app_bricks/telegram_bot/telegram_bot.py

fcc9288

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

fmt

340bfc7

remove requests dep

7b35eea

add start stop methods and thread loop

528a85d

add sync handlers support

687ce44

add typings and docstrings

1e3cd01

add tests

9fcd52a

error handling improvements

27e711a

add schedule_message method

1f31099

Add auto-register commands feature

bf52f73

simplify API

c915638

add pytest async dependencies and config for tests

896405f

dsammaruga force-pushed the telegram-bot branch from 5a127a8 to 896405f Compare February 12, 2026 19:55

beanrepo added 2 commits February 12, 2026 21:35

improves semantics, adds reply methods and new handlers for audio, vi…

7b2cd9a

…deo and docs

unify media handling with auto-detection and size limits

01090ca

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Telegram bot#48

Telegram bot#48
mirkokurt wants to merge 18 commits intoarduino:release-0.6from
mirkokurt:telegram-bot

mirkokurt commented Jan 12, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI Jan 12, 2026

Uh oh!

Uh oh!

Copilot AI Jan 12, 2026

Uh oh!

Uh oh!

Uh oh!

rjtokenring Jan 12, 2026

Uh oh!

rjtokenring Jan 12, 2026

Uh oh!

rjtokenring Jan 12, 2026

Uh oh!

robgee86 Jan 13, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

mirkokurt commented Jan 12, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Copilot AI Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

rjtokenring Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

rjtokenring Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

rjtokenring Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

robgee86 Jan 13, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants