Core: WARNING (SyncWorker_5) [telegram.vendor.ptb_urllib3.urllib3.connectionpool] Connection pool is full, discarding connection: api.telegram.org

Created on 20 Feb 2018  路  5Comments  路  Source: home-assistant/core

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
hassio version 1.1.2
Home Assistant 0.63.3

Python release (python3 --version):
I use hass.io

Component/platform:
I use hass.io on Raspberry Pi 3 with 32GB SD and ethernet connection

Description of problem:
I just started using the home assistant and from the connected devices there is only one switch and one motion sensor on mqtt. But there is warning In log:
WARNING (SyncWorker_5) [telegram.vendor.ptb_urllib3.urllib3.connectionpool] Connection pool is full, discarding connection: api.telegram.org

Expected:
no warnings in log :)

Problem-relevant configuration.yaml entries and steps to reproduce:




    1. 2.
  1. 3.

Traceback (if applicable):


Additional info:

waiting-for-reply

Most helpful comment

Still an Issue on 0.76.0b0

WARNING (SyncWorker_5) [telegram.vendor.ptb_urllib3.urllib3.connectionpool] Connection pool is full, discarding connection: api.telegram.org

All 5 comments

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

Still an issue on 0.70.0

Still an Issue on 0.76.0b0

WARNING (SyncWorker_5) [telegram.vendor.ptb_urllib3.urllib3.connectionpool] Connection pool is full, discarding connection: api.telegram.org

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 馃憤

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rschaeuble picture rschaeuble  路  230Comments

grantalewis picture grantalewis  路  145Comments

neotrunks picture neotrunks  路  169Comments

balloob picture balloob  路  371Comments

Gio76 picture Gio76  路  223Comments