RogerSelwyn / MS365-Calendar

Microsoft 365 Calendar Integration for Home Assistant
MIT License
13 stars 1 forks source link

Connection Pool is full #5

Closed Snowrisk closed 2 months ago

Snowrisk commented 4 months ago

Hello, The following message appear daily in my Home Assistant log file.

`Logger: urllib3.connectionpool
Quelle: /usr/local/lib/python3.12/site-packages/urllib3/connectionpool.py:323
Erstmals aufgetreten: 24. Juni 2024 um 16:11:33 (5281 Vorkommnisse)
Zuletzt protokolliert: 13:56:35

Connection pool is full, discarding connection: graph.microsoft.com. Connection pool size: 10
Connection pool is full, discarding connection: login.microsoftonline.com. Connection pool size: 10`

Your integration is the only one that communicates with MS365, so I am opening an issue here.

The error did not occur with your other integration O365.

Thanks Jens

RogerSelwyn commented 4 months ago

How many calendars are you retrieving?

Snowrisk commented 4 months ago

14 🙄


Von: RogerSelwyn @.> Gesendet: Dienstag, 25. Juni 2024 14:19 An: RogerSelwyn/MS365-Calendar @.> Cc: Jens @.>; Author @.> Betreff: Re: [RogerSelwyn/MS365-Calendar] Connection Pool is full (Issue #5)

How many calendars are you retrieving?

— Reply to this email directly, view it on GitHubhttps://github.com/RogerSelwyn/MS365-Calendar/issues/5#issuecomment-2188786460, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB46XDDCLWYMCRJHM7HLHF3ZJFN4JAVCNFSM6AAAAABJ3WVUNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYG44DMNBWGA. You are receiving this because you authored the thread.Message ID: @.***>

RogerSelwyn commented 4 months ago

Do you really need 14?

Snowrisk commented 4 months ago

Yes, my problem is that automations with a trigger "calendar event" for all-day appointments unfortunately do not work if I only search for certain terms in the appointment title.

Therefore, I had to create a search device for each term that should trigger a trigger:

This is the only way it works for me. So I just check whether one of the triggers is on or off and that's it. I have not found a way to make a regex query within the "search" parameter.

It was like that before and it didn't work:

trigger:

The trigger was not executed.

Thanks Jens


Von: RogerSelwyn @.> Gesendet: Dienstag, 25. Juni 2024 15:09 An: RogerSelwyn/MS365-Calendar @.> Cc: Jens @.>; Author @.> Betreff: Re: [RogerSelwyn/MS365-Calendar] Connection Pool is full (Issue #5)

Do you really need 14?

— Reply to this email directly, view it on GitHubhttps://github.com/RogerSelwyn/MS365-Calendar/issues/5#issuecomment-2188904964, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB46XDEKYLESJGC64SX2QLDZJFTXJAVCNFSM6AAAAABJ3WVUNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYHEYDIOJWGQ. You are receiving this because you authored the thread.Message ID: @.***>

RogerSelwyn commented 4 months ago

I’ll take a look when I get back from holiday inn a couple of weeks

Snowrisk commented 4 months ago

Thank you and have a nice vacation!


Von: RogerSelwyn @.> Gesendet: Mittwoch, 26. Juni 2024 03:51 An: RogerSelwyn/MS365-Calendar @.> Cc: Jens @.>; Author @.> Betreff: Re: [RogerSelwyn/MS365-Calendar] Connection Pool is full (Issue #5)

I’ll take a look when I get back from holiday inn a couple of weeks

— Reply to this email directly, view it on GitHubhttps://github.com/RogerSelwyn/MS365-Calendar/issues/5#issuecomment-2190381167, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB46XDAMXNTVXWLDQR27XVDZJINCHAVCNFSM6AAAAABJ3WVUNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJQGM4DCMJWG4. You are receiving this because you authored the thread.Message ID: @.***>

RogerSelwyn commented 4 months ago

Yes, my problem is that automations with a trigger "calendar event" for all-day appointments unfortunately do not work if I only search for certain terms in the appointment title.

Back from holiday...

Is this only for all day events? i.e. it will work for non-all-day events. Maybe this is because all-day events by default in MS are marked as "Free" rather than "Busy".

To be honest I don't use the HA Automation platform (it's too obscure for me), I use Node Red. That said I suspect the issue is really in whatever HA core is doing, since if this works for non-all-day events then I'd expect it to work for all-day as well.

To re-work this so that it will handle large numbers of calendars is a major task. A simpler route you can take to get your setup to work (assuming no HA core fix) is to install two instances of the MS-Calendar integration using the same secrets. This would create a second o365 calendars yaml, where you can put half your device_ids.

Snowrisk commented 4 months ago

Thanks, Roger. I will try it with a 2nd configuration.


Von: RogerSelwyn @.> Gesendet: Montag, 8. Juli 2024 12:54 An: RogerSelwyn/MS365-Calendar @.> Cc: Jens @.>; Author @.> Betreff: Re: [RogerSelwyn/MS365-Calendar] Connection Pool is full (Issue #5)

Yes, my problem is that automations with a trigger "calendar event" for all-day appointments unfortunately do not work if I only search for certain terms in the appointment title.

Back from holiday...

Is this only for all day events? i.e. it will work for non-all-day events. Maybe this is because all-day events by default in MS are marked as "Free" rather than "Busy".

To be honest I don't use the HA Automation platform (it's too obscure for me), I use Node Red. That said I suspect the issue is really in whatever HA core is doing, since if this works for non-all-day events then I'd expect it to work for all-day as well.

To re-work this so that it will handle large numbers of calendars is a major task. A simpler route you can take to get your setup to work (assuming no HA core fix) is to duplicate your account in your config with a different account name.

So:

o365: accounts:

This would create a second o365 calendars yaml, where you can put half your device_ids.

— Reply to this email directly, view it on GitHubhttps://github.com/RogerSelwyn/MS365-Calendar/issues/5#issuecomment-2213680929, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB46XDGVHD55NRO5NUWAR6TZLJVURAVCNFSM6AAAAABJ3WVUNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJTGY4DAOJSHE. You are receiving this because you authored the thread.Message ID: @.***>

github-actions[bot] commented 3 months ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 2 months ago

This issue was closed because it has been inactive for 14 days since being marked as stale.