The Telegram agent is extremely useful!
However if you'd like to have the agent send messages to a telegram group then the agent needs to know the ChatID of that telegram group.

 

Currently you have to use the terminal for that.

cd /boot/config/plugins/dynamix/telegram
nano chatid

Please expose a 'chatid' field in the Configuration of the Telegram Agent to make this process more user friendly.

@limetech

Seconded this is super a super easy fix which would improve the experience for us

BUMP - I just ran into this again on a new install. the Telegram notification section in the configuration is 100% useless without this option.

This is just annoying. Please, almost 2 years later we are in the same position.

Edited January 5, 20242 yr by dgongut

I'm new to Unraid and just had to look this up. Glad this came up, but this really should be a feature. Now I get my Kuma and Unraid notifications in the same chat.

Hello, here to push the same request and add to request adding support for the topic ID within the Unraid telegram agent. I'll explain my need below:

 

I have just one bot managing all the notifications from all my dockers, I've made a group chat with the name of the server and divided it in different topics.

All the notification messages from the agents only supporting the "chatid" field end in the "general" topic of the group chat.

Some other agents from my dockers already support the "topic ID" field so I can drive their messages into a specific conversation (topic) within the same group just by adding the topic ID in addition to the chat ID.

 

That would be a nice feature to add so that we can direct messages from Unraid into a specific topic within a bigger server group chat.

 

EDIT: I've tried to modify the Telegram agent script by myself but unfortunately it gets overwritten by the system and I can't get the modification to stick.

 

Adding this feature should be as easy as modifying this last part of the Dynamix Telegram.sh script from this:

 

CHATID=$(< $TELEGRAM/chatid);
MESSAGE=$(echo -e "$(hostname): $TITLE\n$MESSAGE");
curl -G -s "https://api.telegram.org/bot$BOT_TOKEN/sendMessage" --data-urlencode "chat_id=$CHATID" --data-urlencode "text=$MESSAGE" 2>&1;

 

To this:

CHATID=$(< $TELEGRAM/chatid);
TOPICID=$(< $TELEGRAM/topicid);
MESSAGE=$(echo -e "$(hostname): $TITLE\n$MESSAGE");
curl -G -s "https://api.telegram.org/bot$BOT_TOKEN/sendMessage" --data-urlencode "message_thread_id=$TOPICID" --data-urlencode "chat_id=$CHATID" --data-urlencode "text=$MESSAGE" 2>&1;

 

Where "topicid" is a file similar to "chatid" containig the topic index

 

Does anyone know how could I force these script mods to stick?

 

Thank you

Edited December 18, 20241 yr by J1mm1
Adding information

I've created a custom user script that runs on the array startup:

 

echo "-your group chat id" > /boot/config/plugins/dynamix/telegram/chatid

 

Edited January 11, 20251 yr by Jarek Kr

On 1/11/2025 at 11:45 AM, Jarek Kr said:

I've created a custom user script that runs on the array startup:

 

echo "-your group chat id" > /boot/config/plugins/dynamix/telegram/chatid

 

Don't think you need a script for that, the chatid file is persistent across reboots