telegram_bot platform to only send messages

[azogue]

Description:

When the notify.telegramplatform went included in the component telegram_bot (used to send and receive messages), some users using the same Telegram account from multiple devices were abandoned... (See #8183).

This is a dummy telegram_bot platform for these users (and any user who doesn't need to receive any messages). It has the capacity of sending any type of Telegram message, but it cannot receive anything.

Related issue (if applicable): fixes #8183

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.io#2882

Example entry for configuration.yaml (if applicable):

telegram_bot:
  platform: broadcast
  api_key: !secret telegram_bot_api_key
  allowed_chat_ids:
    - !secret telegram_bot_chat_id_admin
    - !secret telegram_bot_group
  
notify:
  - platform: telegram
    chat_id: !secret telegram_bot_chat_id_admin

Checklist:

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.github.io

[MartinHjelmare]

We should change this line to check for False instead of None:
https://github.com/azogue/home-assistant/blob/34d397376ef95fcdb22052739678b6a23885b1b6/homeassistant/components/telegram_bot/__init__.py#L217

[MartinHjelmare]

I think this is ok. I'm a bit hesitant about the platform name, but I don't have a better suggestion either.

[MartinHjelmare]

Needs to be updated.

[azogue]

I don't like the name either, was hoping someone to suggest a better one, lol

Going to update the description and make the doc.

Thanks for reviewing!

[pvizeli]

Yeah the name is a bit strange, but I have also no better sugestion...

[kirichkov]

Some name suggestions: telegram_message_send, send_telegram_message

I don't say they are better :-) The best would be "telegram_notification", but I think that will result in a lot of confusion!

I spoke too soon. Didn't notice it's a platform under the telegram_bot platform. onlysend is indeed the one that makes most sense so far.

[point-4ward]

Suggestion: broadcast

[azogue]

ok, so broadcast it is (I like it more too)

[pvizeli]

I think one of that line is not async safe...

[azogue]

I think they are, but not the next, getting the bot username. Pushed a commit to fix

[nordeep]

After telegram_bot was introduced we, unfortunately, can't use more than one bot for notifications. It may be useful when we use customize notifications for different bots(chats) in the messenger (different type of notifications, for example - info, warn, crit).

[kirichkov]

Yes, you can. This platform allows you to only send messages. Which allows you to use the bot for notification from multiple hass instances, and other software as well. I use a single bot for notifications from 2 hass instances, and 2 other pieces of software. All in all total 4 "inputs" that send messages.

[nordeep]

But, I need two bots on only one hass instance.
Now on old instance I use hass 0.43.2 and two telegram notifications with two api keys.

[kirichkov]

Aha, I see your use case. Maybe you can try adding multiple bots. I see the telegram_bot component's configuration takes a list. Unfortunately I can't be if any more help.

[balloob]

Pull requests should not be used for support.