Erreur Telegram bot polling

Bonjour,

Je tente d’intégrer Telegram bot mais lors de la configuration en mode sondage j’ai une erreur
(que je n’ai pas en mode diffuser)
Je n’ai pas trouver d’autres cas sur le forum
Semble lié à Python mais je ne sais pas comment faire une mise à jour. Je suis sur VM sur Synology.

Merci !

voici le log

Enregistreur: homeassistant.components.telegram_bot
Source: components/telegram_bot/__init__.py:549
intégration: Telegram bot (documentation, problèmes)
S'est produit pour la première fois: 07:05:23 (3 occurrences)
Dernier enregistrement: 07:19:26

Error setting up Telegram bot polling
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/telegram_bot/__init__.py", line 549, in async_setup_entry
    receiver_service = await MODULES[p_type].async_setup_platform(hass, bot, entry)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/telegram_bot/polling.py", line 20, in async_setup_platform
    pollbot = PollBot(hass, bot, config)
  File "/usr/src/homeassistant/homeassistant/components/telegram_bot/polling.py", line 59, in __init__
    self.application = ApplicationBuilder().bot(self.bot).build()
                       ~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/telegram/ext/_applicationbuilder.py", line 205, in __init__
    self._job_queue: ODVInput[JobQueue] = DefaultValue(JobQueue())
                                                       ~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/telegram/ext/_jobqueue.py", line 112, in __init__
    self.scheduler: "AsyncIOScheduler" = AsyncIOScheduler(  # noqa: UP037
                                         ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
        **self.scheduler_configuration
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/apscheduler/schedulers/base.py", line 87, in __init__
    self.configure(gconfig, **options)
    ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/apscheduler/schedulers/base.py", line 126, in configure
    self._configure(config)
    ~~~~~~~~~~~~~~~^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/apscheduler/schedulers/asyncio.py", line 48, in _configure
    super(AsyncIOScheduler, self)._configure(config)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/apscheduler/schedulers/base.py", line 697, in _configure
    self.timezone = astimezone(config.pop('timezone', None)) or get_localzone()
                    ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/apscheduler/util.py", line 93, in astimezone
    raise TypeError('Only timezones from the pytz library are supported')
TypeError: Only timezones from the pytz library are supported

Ma configuration


[center]## System Information

version core-2025.12.4
installation_type Home Assistant OS
dev false
hassio true
docker true
container_arch amd64
user root
virtualenv false
python_version 3.13.9
os_name Linux
os_version 6.12.51-haos
arch x86_64
timezone Europe/Paris
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 4989
Installed Version 2.0.5
Stage running
Available Repositories 2502
Downloaded Repositories 9
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 16.3
update_channel stable
supervisor_version supervisor-2025.12.3
agent_version 1.7.2
docker_version 28.3.3
disk_total 30.8 GB
disk_used 7.2 GB
nameservers 192.168.1.254
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized false
virtualization kvm
board ova
supervisor_api ok
version_api ok
installed_addons Matter Server (8.1.1), Get HACS (1.3.1), File editor (5.8.0), Mosquitto broker (6.5.2), Zigbee2MQTT (2.6.3-1), Studio Code Server (5.19.3), Samba Backup (5.2.0), Linky (1.6.1), Z-Wave JS (0.27.0)
Dashboards
dashboards 3
resources 3
views 3
mode storage
Network Configuration
adapters lo (disabled), enp0s3 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth0aa9c8d (disabled), veth1d48f5b (disabled), veth54812cc (disabled), veth31301ba (disabled), veth734ffdf (disabled), veth3c37f5a (disabled), veth8c2e2d7 (disabled), vethf536a43 (disabled), vethb637f47 (disabled), veth3ff4bcb (disabled), veth54b7ea2 (disabled), veth3c9a471 (disabled)
ipv4_addresses lo (127.0.0.1/8), enp0s3 (192.168.68.119/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth0aa9c8d (), veth1d48f5b (), veth54812cc (), veth31301ba (), veth734ffdf (), veth3c37f5a (), veth8c2e2d7 (), vethf536a43 (), vethb637f47 (), veth3ff4bcb (), veth54b7ea2 (), veth3c9a471 ()
ipv6_addresses lo (::1/128), enp0s3 (fe80::5e0b:b7a8:c1e3:7365/64), hassio (fd0c:ac1e:2100::1/48, fe80::ec81:f0ff:fe4d:f3a1/64), docker0 (fe80::e451:4aff:fec4:7a61/64), veth0aa9c8d (fe80::e45c:bff:fe9f:8a5f/64), veth1d48f5b (fe80::10c1:45ff:fecc:154b/64), veth54812cc (fe80::7854:dff:fe22:72d2/64), veth31301ba (fe80::308e:89ff:fe1d:3766/64), veth734ffdf (fe80::9434:26ff:fe3a:d235/64), veth3c37f5a (fe80::b07a:41ff:fe28:e4f5/64), veth8c2e2d7 (fe80::b854:8eff:fe8a:a39c/64), vethf536a43 (fe80::bc1b:cbff:fe43:8daf/64), vethb637f47 (fe80::f82b:51ff:fef1:9c04/64), veth3ff4bcb (fe80::84ba:76ff:fe11:9964/64), veth54b7ea2 (fe80::d421:82ff:fe39:a181/64), veth3c9a471 (fe80::88a4:cff:fe1f:429/64)
announce_addresses 192.168.68.119, fe80::5e0b:b7a8:c1e3:7365
Recorder
oldest_recorder_run 9 décembre 2025 à 04:41
current_recorder_run 20 décembre 2025 à 07:05
estimated_db_size 57.14 MiB
database_engine sqlite
database_version 3.49.2
[/center]

Bonjour, à priori c’est un problème d’environnement.
La librairie reçoit une valeur de timezone qu’elle ne prend pas en charge.

Configures ta timezone parmi l’une d’entre elle :

Tu as quoi dans ton HA : système > général > fuseau horaire

Merci pour ton retour
J’ai Paris de sélectionné (GMT +01:00 Paris)

Ce sujet a été automatiquement fermé après 60 jours. Aucune réponse n’est permise dorénavant.