Telegram bot error at reboot with the new configuration flow

[de666]

The problem

Once configured telegram bot from the UI, it gives an error at the next reboot both in the UI and the log (see below).
It worked well with the old manual yaml configuration until this release which forced the new configuration flow and should import correctly the old configuration.
The old manual configuration was imported but it gave me the same error so I tried to remove every telegram configuration and try to reconfigure from scratch without success.

What version of Home Assistant Core has the issue?

2025.7.0

What was the last working version of Home Assistant Core?

2025.6.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Telegram bot

Link to integration documentation on our website

https://www.home-assistant.io/integrations/telegram_bot/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Error setting up entry telegram for telegram_bot
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/telegram_bot/__init__.py", line 475, in async_setup_entry
    notify_service = TelegramNotificationService(
        hass, receiver_service, bot, entry, entry.options[ATTR_PARSER]
    )
  File "/usr/src/homeassistant/homeassistant/components/telegram_bot/bot.py", line 243, in __init__
    self.parse_mode = self._parsers[parser]
                      ~~~~~~~~~~~~~^^^^^^^^
KeyError: None

Additional information

[home-assistant]

Hey there @hanwg, mind taking a look at this issue as it has been labeled with an integration (telegram_bot) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of telegram_bot can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign telegram_bot Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

telegram_bot documentation
telegram_bot source
_{^{(message by IssueLinks)}}

[hanwg]

Can you share your telegram bot configuration yaml?

[de666]

Ok, I made some other test and it seems the problem is related to the configuration of the "Parse mode" through the UI.
If I select "simple text" as default parse mode I have the error.
On the other hand, selecting something other than simple text seems to work well.
So it doesn't seem related to the previous telegram configuration.

Anyway, before upgrading to 2025.7 I had:

configuration.yaml

telegram_bot: !include telegram_bot.yaml

telegram_bot.yaml

- platform: polling
  api_key: "11111111:mmm-zzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
  allowed_chat_ids:
    - 1234567890

After the upgrade:

Configuration seems imported well

• Commented telegram bot line in configuration.yaml
• Configured the parse mode as "simple text"

[amarok77]

the same thing happened to me too.
after updating the system to version 2025.7.0, it imported the telegram_bot yaml configuration and I had to reconfigure all the ACTIONS with the new notification instructions.
everything worked until a reboot where the system gave me the same error shown above in the images.
i redid the entire configuration from scratch and it worked until the next reboot where the same error returned.

this is what is written in the log

Registratore: homeassistant.config_entries
Fonte: config_entries.py:749
Prima occorrenza: 10:24:52 (2 occorrenze)
Ultimo accesso: 10:25:26

Error setting up entry caltahouse for telegram_bot
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/telegram_bot/init.py", line 475, in async_setup_entry
notify_service = TelegramNotificationService(
hass, receiver_service, bot, entry, entry.options[ATTR_PARSER]
)
File "/usr/src/homeassistant/homeassistant/components/telegram_bot/bot.py", line 243, in init
self.parse_mode = self._parsers[parser]
~~~~~~~~~~~~~^^^^^^^^
KeyError: None

[Teraskull]

Same, but the config fails to save if I select "MarkdownV2" as the parse mode.

[hanwg]

@Teraskull, what errors are you seeing in the UI / logs?

[Teraskull]

@Teraskull, what errors are you seeing in the UI / logs?

I cannot replicate this anymore, but when trying to use the telegram_bot.send_message in a script with "MarkdownV2" selected, the message did not get sent. But seems like everything works as expected now, might be cache. I'll report the exact error if this happens again, thanks!

[megauzer]

Удалил старую конфигурацию, новая пишет в логах "invalid proxy" при попытке настроить.

[hanwg]

"invalid proxy" error can be due to a number of reasons:

• your proxy url is invalid. Usually it should be in the format http, https or socks
• The integration can't connect to the proxy server
• The proxy server can't connect to Telegram

It will be great if you can post in English to make it easier for everyone to help.

It appears that your issue is not related to this issue. If you still need help, you can either create a separate issue or post in the home assistant forums at: https://community.home-assistant.io/c/configuration/11.