Increase pool max size for urllib3 in Fritz integration

[chemelli74]

Proposed change

To avoid exhausting pool, default of 10 should be increased.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes Connection pool is full, discarding connection: 192.168.178.1 #52572
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[probot-home-assistant]

Hey there @mammuth, @AaronDavidSchneider, mind taking a look at this pull request as its been labeled with an integration (fritz) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[AaronDavidSchneider]

30 seems to be fine. I tested with 20 activated switches and had no problem. This seems reasonable (IMO).
However, it seems that we are creating a lot of delay which causes updates to take long times.

2021-07-26 07:32:26 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7530_wi_fi_rosefy is taking over 10 seconds
2021-07-26 07:32:26 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7530_wi_fi_rosefy_5ghz is taking over 10 seconds
2021-07-26 07:32:26 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7530_wi_fi_rosefy_guests is taking over 10 seconds

Therefore, even though this PR fixes the symptom (the error itself), we may need to think more about how we could reduce api calls.

But this would probably involve reworking fritzconnection such that fritz can be local push instead of local polling...

[chemelli74]

However, it seems that we are creating a lot of delay which causes updates to take long times.

2021-07-26 07:32:26 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7530_wi_fi_rosefy is taking over 10 seconds
2021-07-26 07:32:26 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7530_wi_fi_rosefy_5ghz is taking over 10 seconds
2021-07-26 07:32:26 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7530_wi_fi_rosefy_guests is taking over 10 seconds

I never saw those delays on my box, maybe something transient in your network/environment.

Therefore, even though this PR fixes the symptom (the error itself), we may need to think more about how we could reduce api calls.

But this would probably involve reworking fritzconnection such that fritz can be local push instead of local polling...

Not sure Fritz!Box device allows to maintain the connection open for subsequent calls.
Anyway is a huge rework that will involve primarily the author of fritzconnection library.

Simone

[frenck]

Thanks, @chemelli74 👍