If your automations still send Telegram messages through a notify entry with platform: telegram in configuration.yaml, they will stop working after the next Home Assistant update. A pull request by jbouwh, merged into the development branch on 23 October 2026, removes the legacy Telegram notify platform. It is expected in Home Assistant 2026.11. The platform was deprecated in 2025.11, and the version it was scheduled to break in, 2026.8.0, has already passed.

What breaks

The notify.<name> actions created by that YAML platform no longer exist. Any automation, script or dashboard button that calls one of them will fail. The Telegram bot integration itself (telegram_bot) stays, and its tests passed unchanged.

Home Assistant will not silently ignore the old configuration. The telegram integration is replaced with a stub, the same way Microsoft Teams (msteams) was handled earlier. A platform: telegram entry still passes configuration validation, and Home Assistant raises an integration_removed repair issue that points to the Telegram bot notifiers. The Telegram brand entry that grouped the two integrations is gone as well, so Telegram bot is now listed on its own.

How to migrate

The replacement has been available since the deprecation: notify entities provided by the Telegram bot integration, one for each chat ID.

  1. Open the Telegram bot integration under Settings > Devices & services and add each chat ID you send to as a subentry. Each one creates a notify entity.
  2. In automations and scripts, replace calls to notify.<name> with the notify.send_message action targeting the new entity.
  3. For photos, documents, keyboards and other options that plain text notifications do not cover, use the telegram_bot actions.
  4. Delete the platform: telegram entries from the notify section of configuration.yaml and restart. The repair issue goes away once the entries are removed.

Before updating, search your automations, scripts and dashboards for the old action names, because those calls only fail when they run.

Part of a wider change

The pull request describes the removal as part of the effort to move integrations from the legacy notify service to notify entities. It closes issue #183605, opened on 29 September, which noted that the deprecation period, already extended once, had run out.