Connection pool full

Configuration
1

Anyone know what this is all about?

Logger: urllib3.connectionpool
Source: /usr/local/lib/python3.14/site-packages/urllib3/connectionpool.py:327
First occurred: 12:33:50 (983 occurrences)
Last logged: 15:38:20

Connection pool is full, discarding connection: 192.168.1.141. Connection pool size: 10
Connection pool is full, discarding connection: 192.168.1.141. Connection pool size: 9

Only just appeared since updating to 2026.5.2, but there are inconclusive posts about it going back several years.

2

First of all, Please Check the Raw-Log, 3 dot's to the right of basic-Log-View
What kind of Device(beside an IP) is this ? .141 which integration is it installed in ?

3

Synology NAS. Synology DSM integration. Provides about a dozen entities monitoring CPU, Memory etc.

Errors all seem to relate to a particular card from HACS:

2026-05-17 18:23:00.335 WARNING (SyncWorker_10) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.1.141. Connection pool size: 10
2026-05-17 18:23:00.422 WARNING (SyncWorker_59) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.1.141. Connection pool size: 10
2026-05-17 18:23:00.580 ERROR (MainThread) [frontend.js.modern.202604294] Uncaught error from Chrome 119.0.6045.193 on Android 7.0
TypeError: n is not a function
/hacsfiles/lovelace-home-feed-card/lovelace-home-feed-card.js:203:9473

This is the Home Feed Card, which uses a calendar on the NAS through the CalDAV integration. I notice some issues on GitHub mention CalDAV. Others mention other integrations. They go back to 2024.

Edit: Removed the card, no more errors. Thanks for the pointer.

Another edit: For be benefit of others with a similar problem. Replacing the card with a normal calendar card reduced the number of errors but did not remove them entirely. To do that you have to remove the CalDAV integration, which seems to be the culprit. Pity.

1 Like