01Create a bot with BotFather
Open the official @BotFather using the link below. Press Start and send /newbot. Choose a display name, then a unique username ending in bot, such as building_alert_bot.
BotFather returns a Bot Token. Copy it privately; it allows software to control this bot.
/newbot02Add the bot in Push
Sign in to nvraim.com/login as an administrator. Open Push → Add push, select Telegram Bot, give it a recognizable name, and paste the Bot Token. Save.
Saving validates the bot token. Expand the saved bot to find “Bind a person or group” and its complete /start command. A successful save does not yet bind a recipient.
03Bind your private chat
Open your own bot in Telegram, not BotFather, and press Start. Send the complete /start command displayed in NVR AI Monitor, including the space and binding code.
Return to Push and click “Check binding message”. Your chat should appear in the recipient list. Each successful binding changes the code; use the latest code for the next person. Sending only /start or hello will not bind your chat.
/start ABCD1234ABCD1234 is an example. Use the code shown in your account.
04Add a group if needed
Add the bot to the intended group and allow it to send messages and photos. In that group, send /start@your_bot_username followed by a space and the current binding code. Return to NVR AI Monitor and check binding again.
Keep Telegram privacy mode enabled; use the addressed command so the bot receives it. Ordinary groups do not need to grant unrelated administrator permissions. Bind each chat separately, then test it.
/start@your_bot_username ABCD123405Send a test
Next to the bound recipient, click “Send test”. Confirm that the correct private chat or group receives the test message.
This checks delivery, not camera detection. If the message arrives but your phone is silent, check Telegram notification permissions and whether the chat is muted.
06Choose recipients in a rule
Open Rules and create or edit a rule. Under message delivery, enable notifications and select the bound recipients under Telegram. You can select more than one. Save the rule and ensure it is enabled.
When a qualifying event is created, its notification can include the evidence image, time, camera and rule information. Test a real condition and check delivery in Events. Configuring a bot alone does not turn on every rule.
Common questions
Why is no binding found?
Send the current full command to your own bot, then check again promptly. The code changes after a successful binding. For groups, address the command to the bot. Another service polling the same bot can consume the message.
Do I need getUpdates or a Chat ID website?
No. NVR AI Monitor reads the matching binding message and stores the chat destination. You do not need to paste a token into a browser address or use a third-party ID bot.
Why does Telegram report a webhook or conflict error?
This integration retrieves binding messages using getUpdates. A webhook or another polling application can conflict with it. Prefer a separate bot; do not remove a webhook belonging to another service without checking with its operator.
The test succeeds, but event alerts do not arrive.
Check that the rule, notification switch, bot and recipient are enabled and that the event actually satisfies the rule. Review delivery status in Events. A test message does not prove that detection is configured.
Telegram · BotFather ↗Telegram · Bot FAQ ↗
Related guide: Set up SMTP email alerts → Browse all guides →