Telegram Bot integration fails to load with timeout error in 2026.3
Home Assistant version: 2026.3
Installation type: Home Assistant OS (Intel Mini PC)
Description:
The Telegram Bot integration (polling mode) fails to load with a timeout error. The integration shows “Configuration error, will retry: Timed out” in the Devices & Services page and never loads successfully.
What I tried:
- Fresh token generated via BotFather
- Deleted and re-added the integration via UI
- Removed all Telegram configuration from configuration.yaml
- DNS set to 8.8.8.8
- IPv6 disabled in router and in HA network settings
- Full HA restart
Root cause found:
Despite IPv6 being disabled both in the router and in HA’s network settings, nslookup api.telegram.org returns an IPv6 address (2001:67c:4e8:f004::9) alongside the IPv4 one (149.154.166.110). HA appears to attempt the connection via IPv6, which fails since IPv6 is not available, resulting in a timeout.
Confirmed via terminal:
curl -4 -s https://api.telegram.org/bot[TOKEN]/getMe→ returns{"ok":true,...}
curl -6 -s https://api.telegram.org→ no response
There is no way to force IPv4 permanently at the system level in HA OS due to the read-only filesystem (sysctl returns read-only file system error).
Expected behavior:
When IPv6 is disabled in HA network settings, the Telegram Bot integration should only attempt IPv4 connections.
Workaround needed:
A configuration option to force IPv4 for the Telegram Bot integration, or a fix so that HA respects the IPv6 disabled setting when establishing outbound connections.