Telegram bot config entry id | Home Assistant | Page 1

trim galleon Feb 26, 2026, 3:19 PM

#

How do you mean?

#

(Also, only respond when you feel like responding)

loud vale Feb 26, 2026, 3:20 PM

#

The action allows an entity_id parameter which probably most users will use.

#

For that you don't need to specify config entry id.

trim galleon Feb 26, 2026, 3:20 PM

#

Oooh, I see

#

fair

loud vale Feb 26, 2026, 3:21 PM

#

You could say that we should not expose config entry id at all now.

#

But then you can't send a message to an arbitrary chat_id.

#

I'm not sure about the status of that feature, if we allow that already.

#

It was planned for that integration.

trim galleon Feb 26, 2026, 3:30 PM

#

I believe @ornate kelp added notify entities yes

loud vale Feb 26, 2026, 8:29 PM

#

I mean the feature to be able to send messages to chat_ids that aren't pre-approved (as subentries).

trim galleon Feb 26, 2026, 8:30 PM

#

Oooh

loud vale Feb 26, 2026, 8:32 PM

#

Without that feature, the config entry id parameter isn't needed.

ornate kelp Mar 10, 2026, 3:45 AM

#

The legacy Telegram integration is being removed in 2026.5 since it is being replaced by Telegram bot.
Some integrations such as Alert and MFA are still using the legacy notifiers with the legacy Telegram integration.

Just wondering, what's the plan for 2026.5?
Do we update the repair issue message and move back the planned date from 2026.5 to 6 months later?
Or do we still proceed with the removal and break those integrations that use the legacy Telegram notifiers?

loud vale Mar 10, 2026, 6:54 AM

#

There's no way forward for the Alert integration. It's legacy and frozen for development.

#

For the notify auth_mfa_module, I think we should support notify entities.

#

I think we should use an action selector in that config flow that filters on notify domain for the service action.

#Telegram bot config entry id