[Feature request] Add the option to use MTProxy

[avbor]

I've seen previous issues where the authors opposed the simple method of using mtproxy, but now many countries are trying to restrict Telegram.
This includes restricting the availability and functionality of the Telegram Bot API.
However, there are good MTProxy implementations that bypass state DPIs.
Using a local Bot API that connects to the Telegram network through a proxy would solve the Bot API accessibility issue.
Please consider a simple option to enable a proxy for the local Bot API.
I'm not a programmer, just a simple user of Home Assistant who wants to continue using the familiar functionality of Telegram Bots.

[Enzokot]

I completely agree. This kind of option will help overcome the restrictions

[levlam]

MTProto proxy must be set up in a location, from which the Telegram is freely accessible. If you can set up a proxy on such server, then it will be much better to set up the bot on such server. How can the ability of the Bot API server to use a proxy help you with using the Home Assistant?

[avbor]

How can the ability of the Bot API server to use a proxy help you with using the Home Assistant?

Home Assistant is an open source platform for home automation, a smart home.
In my case, I use a huge number of automations using a bot — for notifications, dialogs, sending photos and videos to Telegram and etc.
However, the bot is part of Home Assistant's built-in functionality; I don't have the option to move it to a third-party server.
Moreover, not all users can use their own proxies; many use other people's open proxies, without the ability to manage the servers where they are located.
Therefore, for all HA users facing Telegram access restrictions, it would be extremely useful to have a local API server with a proxy connection to Telegram's data centers.
I have no other ideas on how to bypass Telegram blocks for Home Assistant in this situation.
With all this in mind, the local API server already knows how to work with proxies, so it seems to me it's not a big problem to add an option to the settings for this. Correct me if I'm wrong.

[levlam]

Do you want to host the Bot API server yourself? Where do you want to host it?

[avbor]

Do you want to host the Bot API server yourself? Where do you want to host it?

I'm already using it; it runs on one of my home machines in Docker, alongside Home Assistant VM.
There's also a dedicated app for Home Assistant OS.

[avbor]

Here - https://github.com/Seed680/telegram-bot-api - he added the ability to configure a proxy (he even suggested making a PR here in one of the previous issues).
I tried building a fresh build, and with some minor modifications, it worked.
Now my local API server works through a proxy, and so far it works very well.
Previously, sending a 6-second video took up to 2 minutes; now it takes seconds.

I'll ask again - please add official proxy-client support.
I'm not a programmer and won't be able to support this with future changes.

[Enzokot]

For my part, I will say frankly - we have nowhere else to turn.

[avbor]

I'll leave this here for anyone looking for information about proxies in the future:

Home Assistant App (add-on) with proxy support: https://github.com/avbor/hassio-apps
Docker image with proxy support: https://github.com/avbor/docker-telegram-bot-api

telegram-bot-api in all images build from this repo with additions from Seed680 and Google Gemini =)