Closed 35gh closed 5 months ago
Hi @35gh , thanks your using Additional CA, I can see the same issue with Home Assistant 2024.6. It seems that other custom integrations are facing the same. Issues have been opened at https://github.com/home-assistant/core/issues?q=is%3Aopen+detected+blocking+call I'll wait and see what they say.
I think you are not supposed to do blocking IO from within the event loop. 2024.6.x
simply improved the detection of such issues, so it now pops up for lots of integrations. Here's an article regarding timezone handling, but the principle is probably similar for other types of IO.
The forum also has some advice how to handle the issue in general.
Hi, yes, just thought I'd pop here that I've got the issue too, but lucky (hopefully?) it's just a warning and hasn't affected any functionality for me yet.
Thanks for the work on additional-ca, it's been invaluable to getting stuff to communicate over SSL <3
Just subscribed, I’m affected too, good luck
Hello, I pushed a fix in release 0.2.3, tested with HAOS 12.3 (Home Assistant 2024.6.2) Could you give a feedback ?
I'm not getting the warning anymore with 0.2.3
It works for me as well, no more warning in logs after restart. Thank you!
How do I install the updated version? It hasn't come up in HACS as an update? (Sorry I'm a bit new to hacs and things)
Again thanks for the amazing work on additional-ca, it's made things way less a chore <3
In HACS > Integrations > Additional CA click on the 3 dots on the top right, then Redownload.
Thanks for the tip for the future. Though it came up as an update today. @35gh :) Much obliged.
Describe the issue
Since update to HAOS 12.3 and/or 2024.6, I got those warnings in logs after HA start up:
Detected blocking call to open inside the event loop by custom integration 'additional_ca' at custom_components/
Describe your setup (please complete the following information):
YAML configuration extract
Logs
Additional context
Warnings appear after HA has started, everything works after that.