Telegram bot deprecation breaks notifications

[PeteRager]

The problem

Telegram bot is migrating to the NotificationEntity from the legacy BaseNotificationService. The deprecation warning instructs the user to remove the notification configuration (as it will be removed in 2025.5.0) but the current implementation does not work in existing configurations.

Specifically this YAML configuration is being depracated:

notify:
  - platform: telegram
    name: sms_telegram_admin
    chat_id: xxxxxxxx

Which worked in a variety of locations in home assistant. One specific incompatibility is with:

alert:
  test:
    name: test
    message: 'An Alert'
    entity_id: input_boolean.test
    state: "on"
    repeat:
      - 60
    notifiers:
      - sms_telegram_admin

Removing the notify configuration and replacing it with the telegram bot service does not work and results in this error:

Failed to call notify.telegram_bot_xxxx_yyyy, retrying at next notification interval`

This occurs because the Notify is not registering a per entity service.

What version of Home Assistant Core has the issue?

core-2026-3-0

What was the last working version of Home Assistant Core?

core-2025-12-0

What type of installation are you running?

Home Assistant Container

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?

Additional information

No response

[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, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@PeteRager Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20telegram_bot%22%20
_{^{(message by IssueContext)}}

---

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

[hanwg]

From my understanding, the feature to add services for each notify entity will be be rejected because that's the legacy approach.
I believe the right approach is to enhance existing integrations/modules to use notify entities instead of the legacy notify service.

alert is probably not the best example since it is a legacy integration.
A better example would MFA; we should enhance those integrations/modules to migrate to notify entities.

[PeteRager]

Agree, you are at the crux of the issue. If we remove the deprecated interface in telegram and all the dependent integrations haven't been migrated - then we have breakage and no viable workarounds. Very few notifications have been migrated to the new interface. The new interface is also limited in that it only accepts Title and Message and does not support the attributes that the notifiers support (like keyboard, etc.) It looks to me there is a little more work to do in core to make sure at the end of the day things work and we minimize the breakages and rework for users.

Regarding alerts; it looks like that integration is being abandoned; so that any users of it will not be able to use it anymore.

[arigit]

I have like a dozen alerts that send email and telegram messages depending on the priority/emergency level and just noticed that telegram alerts have not been working for months apparently.
The alert platform documentation doesn't say anything about it being non-functional or deprecated, this is bad.

[hanwg]

Will be pushing back the removal of the legacy Telegram notifier service until MFA is resolved.
No new date on the removal yet since MFA is quite complex.

#165299

[hanwg]

@arigit
The alert platform isn't broken - it only supports the legacy notify services and not the modern notify entities.
You can still use it with the legacy Telegram integration.

[GancDn]

У меня после обновления core вообще бот перестал работать

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.