Free Software Download Center
Software for industrial data collection, monitoring, and analysis.
In a Telegram-based alarm notification system, EOS SCADA communicates with Telegram not directly
through a user account, but through a bot operating via the Telegram Bot API
to communicate with Telegram.
Basic operating flow:
SCADA ALARM → ANS → TELEGRAM BOT API → BOT → TELEGRAM GROUP / USER
Telegram's official bot management tool,
@BotFather, is used to create and manage Telegram bots. Telegram's official documentation
instructs users to interact with BotFather to create a new bot and obtain its authentication token.
The official documentation describes this process.
/start command./newbot command to start creating a new bot.BotFather requests two basic pieces of information when creating a new bot.
This is the name users will see in Telegram. A descriptive name reflecting the plant or system name can be preferred.
Example: EOS Energy Alarm Bot
This is the bot's unique username on Telegram. Bot usernames normally end with the bot suffix.
Example: eos_energy_alarm_bot
After the bot has been created, BotFather generates a token used to access the Telegram Bot API This token is the authentication credential required for ANS to send messages through the Telegram bot .
Format example:
123456789:AAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
This is only a format example; it is not a real Bot Token.
Very important security warning: The Bot Token must be kept secret. According to Telegram's official documentation, anyone who possesses the token can gain full control over the bot. Do not share the token on web pages, in documentation, screenshots, or with unauthorized persons.
For ANS to determine where to send an alarm message, the target Telegram chat's Chat ID is required. The target may be a user, group, or another chat type supported by Telegram.
In this document, the practical method is to use the Bot API's getUpdates method.
The Telegram Bot API returns updates received by the bot in JSON format.
https://api.telegram.org/bot<TOKEN>/getUpdates
message.chat.id value in the JSON output.Example:
{
"message": {
"chat": {
"id": 987654321,
"type": "private"
}
}
}
Chat ID: 987654321
For plant alarm notifications, creating a dedicated Telegram group generally provides a more suitable operational structure. For example:
Group name: EOS_ALARM_IZLEME
Purpose: Delivery of plant alarm notifications to authorized personnel
https://api.telegram.org/bot<TOKEN>/getUpdates
the following call.
message.chat.id value of the relevant chat in the JSON output.
Example group output:
{
"message": {
"chat": {
"id": -1234567890,
"title": "EOS ALARM IZLEME",
"type": "group"
}
}
}
Group Chat ID: -1234567890
Note: In classic Telegram group chats, the Chat ID value may appear as a negative number.
Therefore, when copying the value, make sure that the leading - sign
is not lost.
When Telegram bots are added to groups, Privacy Mode may be enabled by default. In this case, the bot receives not every message in the group, but only specific commands and messages related to it. According to Telegram's official documentation, Privacy Mode should not be disabled unless it is necessary for bot management.
In this ANS scenario, the primary requirement is not for the bot to collect messages from the group, but for ANS to send alarm messages to the group through the bot. Therefore, it may not be necessary to disable Privacy Mode solely for sending alarms.
Security approach: The bot should have only the permissions it needs and access to unnecessary group messages should not be enabled. Bot management settings should be controlled through Telegram's official BotFather options .
After the bot and target chat are ready, the Telegram integration is configured in the ANS panel.
| ANS Parameter | Value to Enter | Description |
|---|---|---|
| Telegram API Address | https://api.telegram.org |
Base address of the Telegram Bot API. |
| Bot Access Key | Bot Token | Secret bot access token provided by BotFather. |
| Chat ID | Target Chat ID | User or Telegram group to which alarm messages will be sent. |
Field names may differ in the current ANS configuration; however, fundamentally, Telegram API adresi + Bot Token + Chat ID information must be correctly configured.
SCADA → ALARM → ANS → TELEGRAM API → BOT → CHAT ID → PERSONEL
Authorized personnel included in the alarm group can receive alarm notifications through mobile or desktop devices where the Telegram application is installed.
Critical alarm note: Telegram is an Internet-based notification channel. Therefore, in critical processes, the notification architecture should not depend solely on a messaging application; network access, Internet connectivity, and alternative alarm channels should be evaluated together.
BOTFATHER
↓
CREATE BOT
↓
OBTAIN BOT TOKEN
↓
CREATE TELEGRAM GROUP
↓
ADD BOT TO GROUP
↓
DETERMINE CHAT ID
↓
ENTER TOKEN + CHAT ID IN ANS
↓
SCADA ALARM → TELEGRAM NOTIFICATION
Once this configuration is completed, EOS SCADA ANS can forward SCADA alarms to target Telegram chats through the Telegram Bot API according to the defined alarm notification policies. This allows plant personnel to monitor alarm events through the Telegram applications on mobile and desktop devices.