Telegram bot setup error Error from Telegram: httpx.UnsupportedProtocol: Request URL is missing an 'http://' or 'https://' protocol

Dear reader,

Thanks for reading, I try to setup “Telegram Bot” in HA and run into an error.

“Error from Telegram: httpx.UnsupportedProtocol: Request URL is missing an ‘http://’ or ‘https://’ protocol.”

I sniffed my network traffic and I can confirm, nothing has been tried to https://api.telegram.org. It really get stuck at the add on.

My API is not the real one but for lenght considurations etc…
1234567890:ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghi
Please help me.

Kind regards Ouwekaas.

5 Likes

What did you configure under advanced settings?

Just tried doing the same and getting the same error.
advanced settings are default, so its the same as your screenshot @juergenjw

2 Likes

I’m using broadcast instead of polling. And i use send message only.
Perhaps that makes a difference?

Polling or Broadcast give the same error message unfortunately.

3 Likes

Have the same issue on Raspberry PI HA instance
On my second HA instance (on Mini PC) integration works perfect and I can add bot without any issues. But in second instance in Advanced settings “API endpoint” field is not displayed at all. I don’t understand why the same Telegram integration has different settings between my both HA instances

2 Likes

I can reproduce the error on my HAOS 2026.2.0 where i had not installed the telegram_bot integration before.

2 Likes

I have the same issue on 2026.2.0

1 Like

to fix issue you should downgrade to previous version of HA
or recover from backup or using terminal:
ha core downgrade --version 2026.1.3
It helps me to add new telegram bot

2 Likes

Default settings. Like shown in your picture

This seems to be a bug that was introduced with HA 2026.2.0.

i posted an issue to the git hub of home assistant core reporting this Telegram_bot - UnsupportedProtocol · Issue #162342 · home-assistant/core · GitHub

2 Likes

Thank you. I wish developers released every three month instead of monthly.

1 Like

Are both instances on 2026.2 ?

1 Like

i am following this as i am getting the same error as the OP and i have the correct API key

2 Likes

Same problem here. Waiting for the fix…

darn it…waiting for the fix too

1 Like

agree, the only solution for now

Still had this issue on 2026.2.1

I have the same issue on Raspberry PI HA 2026.2.1
No problem with 2026.1.3