Telegram bot changes - Target parameter removed

I’m getting the error message in HA about Telegram Bot and the Target parameter will be removed, see screenshot. I’m searching in my automations and in my configuration file, but I cannot see the Target parameter being used in combination with Telegram. Why do I get this error message? Suggestion on how to debug this

6 Likes

me too, same message but I have no “target” in yaml files

1 Like

I’ve spent the day looking for automations that use “Target” in Telegram notifications, but I have them all well defined, yet I’m still getting the message.
So, maybe this is generic message for everybody

I have had the same issue since upgrading to Home Assistant version 2026.3.0.

I am also looking for a solution.

Same here - can’t find the offending item :slight_smile:

Same here, I hope they don’t stop supporting Telegram.

Do you use the Alarmo integration?

I thought I had changed all my config but the repair re-appeared. Turns out it was in the Alarmo Notifications actions. You can change the target to chat_id in the yaml view in the Alarmo Notifications.

If not Alarmo then check any packages or blueprints.

There’s no chance of that any time soon. The reason these issues are coming up is because the Telegram integration is being actively developed to bring it into line with the way HA now wants notifications to work. And to improve it (e.g. by allowing multiple Telegram bots). There is now a very active code owner and as well as this development he monitors the HA Github feature request section for any suggested improvements to the Telegram bot integration. So if you have a good idea or improvement suggestion that is the place to post it.

No, no Alarmo integration, no blueprint.
I have only packages and yaml files created by myself an noone has Telegram with “target”

Since removing from my config (and alarmo) the repair has not come up again. So it must be still in your config somewhere.

I think it’s a bug.
I checked all the “target” in my yaml files, and I don’t have any related to Telegram.
Then I did a test: I had three repair reports, and I confirmed all three as “done” without having done anything. I restarted Home Assistant and now I only have one.

I tried marking the only one left as “done” and restarting Home Assistant but unfortunately this doesn’t go away.

It’s not a bug. You still have target specified in your notifications somewhere.

I probably don’t understand…

The repair says:

action: send_message
data:
target: # to be updated
- 1234567890
...

I searched for “notify:”, “notify”, “send_message” in all my yaml and jinja files and I found nothing.

I use Telegram like this (I take an example from my yaml):

notify:
- platform: telegram
name: telegram_aaa
chat_id: !secret telegram_chat_id_aaa

and I send messages like this:

action:
service: notify.telegram_aaa
data_template:
title: "Error"
message: >
Error during backup

What’s wrong?

Same issue and confusion here, checked every automation, every script. I cannot find it

I believe the issue stems from the Blueprints Frigate Notification.
Re-import the Blueprints Frigate Notification.
Note the version before and after.
I upgraded from version 0.14.0.2w to 0.14.0.2x.
Do not forget to restart HA.

1 Like

Thanks I had this installed, but did not use it anymore.

But still getting the warning and dont know from where

Same problem, no target in my yaml but still have the error message. No alarmo, no blueprints.

That’s the old soon to be depreciated way of doing it.

It should not generate target repairs. It should generate a repair advising you to update your config.

I use it like this as well

notify:
  - platform: telegram
    name: "myname"
    chat_id: 123456789

I do’nt ghet what needs to be changed? Can you explain?

https://community.home-assistant.io/t/how-to-help-us-help-you-or-how-to-ask-a-good-question/114371#oneone-format-it-properly-16

1 Like