Self test

[cw-kid]

@toggledbits

Oh yes sorry 400 not 404.

Chat ID is correct and yes I think it must be a member. Because I am using the same bot ID and the same chat ID in a raw HTTPS command and the notifications work and go to my "Vera Group" aka my chat ID.

This is the type of HTTPS command I've been using previously:

https://api.telegram.org/bot2188872596:BBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN/sendMessage?chat_id=-314603256&text=This is a test

[toggledbits]

The chat ID in your HTTPS fetch has a minus sign at the front, while the chat ID in MSR does not. Check you configuration again.

[cw-kid]

@toggledbits

Well spotted I didn't even notice that.

I added a minus sign also in the notification.yaml file and now its working from MSR.

[wmarcolin]

@toggledbits minus is allowed, and is a message for a group. When it does not have a minus sign, it is for a single user.

[wmarcolin]

@cw-kid this comment about having the letters bot in front is already added by MSR, we have to be careful, because when we copy the ID when it is generated in Telegram it comes with these letters bot in front that has to be removed when configuring. I had the same problem until I identified this in the log appearing twice botbot.

[toggledbits]

Where are you seeing that? I can't screenshot the Android app because it won't let me (security policy--smart!), but the response to /newbot from BotFather does not contain the string "bot" in front of the key. Are you seeing it elsewhere? Maybe iOS?

[cw-kid]

@wmarcolin said in Is Telegram working?:

I had the same problem until I identified this in the log appearing twice botbot.

Yes indeed, that is what I was seeing in the log file also.

[wmarcolin]

Well first I don't remember how to get the ID, I don't remember when the number was generated lol

I think what may have created confusion, was that when using a direct call, as the example below is necessary to put the bot, but when configuring the MSR not, because the application already adds the information.

https://api.telegram.org/bot177_____83:AAER___________________________GTGk/getUpdates

I think the situation is closed, we just have to stay alert to some other user who mentions that Telegram is not working pass this orientation.

[toggledbits]

The key/token in the response from BotFather when creating the bot will not have 'bot' prepended to it, so that makes sense.

[cw-kid]

Yesterday I converted all my rules to use the now inbuilt notify for Telegram, rather than sending Http requests out as I was.

No further problems and everything seems to be working well.

Thanks for adding Telegram support, I had previously requested it, but at that time it sounded like it would not be added.

[Fanan]

Hi!
I've been trying to get Telegram to work, but I think it's something I'm doing wrong in the notification.yaml. It's working from within Home Assistent, but not with MSR. This is from my Notification.yaml:

  Telegram:
    profiles:
      default:
        # description - A friendly description of this profile (for menus)
        description: Telegram
        #
        # api_url - Access URL for Telegram API. Default is https://api.telegram.org
        api_url: https://api.telegram.org
        #
        # bot_token - (required) Bot Token, from Telegram. See: https://core.telegram.org/bots
        bot_token: "2091____________(blanked for security reason)____________wH2Z0"
        #
        # default_chat_id - (required) Default chat ID to use if not specified in message. See
        #                   this link for how to get chat ID:
        #                   https://stackoverflow.com/questions/32423837/telegram-bot-how-to-get-a-group-chat-id
        default_chat_id: "77________07"
        #
        # default_disable_notification - Default notification flag, may be either "true"
        #                                or "false". The system default is "false"
        #                                (false == notification enabled/not disabled).
        default_disable_notification: "false"
        #
        # default_parse_mode - Default message format/parse mode. The system default is
        #                      blank, for plain text. Other options: MarkdownV2, HTML
        #                      See: https://core.telegram.org/bots/api#formatting-options
        #default_parse_mode: ""

I have tried both with and without qoutes " " around chat_id and bot_token. Am I missing something? I'm on MSR ver 21337. Thanks in advance.
/Fanan

[toggledbits]

Telegram is working fine for me. Any chance you've looked at your logs?

[Fanan]

@toggledbits This is my log (I changed my personal info):

[latest-21342]2021-12-09T18:38:18.936Z <Engine:NOTICE> Resuming reaction Tända hos Khalisi<SET> (rule-kuvhc9mc:S) from step 1
[latest-21342]2021-12-09T18:38:18.939Z <Engine:INFO> Tända hos Khalisi<SET> all actions completed.
[latest-21342]2021-12-09T18:38:19.248Z <NotifyTelegram:ERR> NotifyTelegram failure response from endpoint: 400 Bad Request
[latest-21342]2021-12-09T18:38:19.248Z <NotifyTelegram:INFO> NotifyTelegram request URL: https://api.telegram.org/bot2091333304:AXXpXQDQJ1L19xQoI1Gyc9i5XEH0uIwH2Z0/sendMessage
[latest-21342]2021-12-09T18:38:19.249Z <NotifyTelegram:INFO> NotifyTelegram request body: {"text":"Hello!!","chat_id":"7777777","disable_notification":"false"}
[latest-21342]2021-12-09T18:38:19.249Z <NotifyTelegram:ERR> NotifyTelegram request to https://api.telegram.org/bot2091550404:AXXXXQDQJ1L19xQoI1Gyc9i5XEH0uIwH2Z0/sendMessage failed: Error: NotifyTelegram request failed
[latest-21342]2021-12-09T18:38:19.249Z <Engine:ERR> Engine#1 reaction rule-kuvhc9mc:S step 1 notification (Telegram) failed: Error: NotifyTelegram request failed
[latest-21342]2021-12-09T18:38:19.250Z <NotifyTelegram:ERR> NotifyTelegram failure response text: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}

[toggledbits]

OK, you've found the issue.

[gwp1]

WAIT, WAIT, CAN I TELL HIM??? CAN I, CAN I....??

[Fanan]

I feel like a total fool - but I don't get it... I know it's right in front of me, but I can't see the forest for the trees...

[toggledbits]

No worries. Just trying to teach fishing rather than just handing the fish over...

The last line of your log snippet:

[latest-21342]2021-12-09T18:38:19.250Z <NotifyTelegram:ERR> NotifyTelegram failure response text: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}

It's not happy with the chat ID, it appears. That's a pretty specific message. Where did you get it? Have you verified it?

Getting the chat ID can be a bit of work. Sometimes it's in the message you get when you set up in Bot Father, sometimes not. The config file template's comments give you some instructions and a link for how to get the chat ID.

        #
        # default_chat_id - (required) Default chat ID to use if not specified in message. See
        #                   this link for how to get chat ID:
        #                   https://stackoverflow.com/questions/32423837/telegram-bot-how-to-get-a-group-chat-id
        default_chat_id: "123456789"

At the very least, I'd go through this process and confirm. Watch the case on the ending of the URL that you're asked to fetch. If it's incorrect, the API will give you a bogus empty-ish response rather than an error, which can be frustrating to figure out.

[Fanan]

@toggledbits Thank you for your patience!
After two hours of digging, google searching and some trial and errors, I finally found why it didn't work...

It's easier if the reactor is activated... It do not work even in the editing menu, as long as it's not activated. This is strange, since I can activate a specific entity/step to try it out. But that was not the case with the notify function. All of my tries have been in the editing menu with the reaction not activated. Now it's working perfectly, and so are my other notify services. Have a great weekend!

[toggledbits]

Well, it depends on which "try" button you use. The Entity Action "try" button, on the same row as the entity action itself, will run any time. But the "Try Reaction" button in the reaction's header... no... that requires the rule to be enabled. And that fact is logged (attempting to run a reaction in a disabled rule), by the way, so again, careful review of the logs can be very helpful.

But... that resolution does not reconcile at all with the error message handed back from Telegram that you posted earlier. But if it's working for you now, I guess I won't go down that rabbit hole.

[Fanan]

@toggledbits No, I guess we shouldn't spend any more time trying to understand. It works and I'm delighted. I do appreciate that you try to teach us fishing instead of handing the fish. I always try for hours before I ask for assistence. That's the way to learn and grow. Take care!