Open enoch85 opened 2 months ago
Hmm, I can not reproduce this in my installation. Could there be some issue with your libs possibly, since the cause of the exception is inside ssl.py? What version of pysignalr, websockets and asyncio do you have?
Hmm, I can not reproduce this in my installation. Could there be some issue with your libs possibly, since the cause of the exception is inside ssl.py? What version of pysignalr, websockets and asyncio do you have?
Sorry, how do I get version info? I'm on HAOS.
Never mind, I can see it too now.
Same here with me. Not sure if this is now beeing solved?
`Logger: homeassistant.util.loop Bron: util/loop.py:77 Eerst voorgekomen: 13:35:15 (1 gebeurtenissen) Laatst gelogd: 13:35:15
Detected blocking call to load_default_certs with args (<ssl.SSLContext object at 0x7f63f20dd0>, <Purpose.SERVER_AUTH: _ASN1Object(nid=129, shortname='serverAuth', longname='TLS Web Server Authentication', oid='1.3.6.1.5.5.7.3.1')>) in /usr/local/lib/python3.12/ssl.py, line 713: context.load_default_certs(purpose) inside the event loop; This is causing stability issues. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_default_certs Traceback (most recent call last): File "
Not sure how to solve it yet. It does not really stop anything from working correctly, it is just a warning that HA puts in the log when it detects blocking I/O in an integration. In our case it happens in an external library which is out of our control how it is implemented. This happens only once during startup so it is not really a big deal for the performance of HA in general. But still, would be nice to get rid of it.
Well, this is mostly a note to myself, but anyway... The solution to this seems to be to provide an SSL context to the websockets lib instead of relying on it self to create such a context (which it will do with blocking I/O). Problem is that all calls to the websockets lib is handled completely by pysignalr lib, so it will require a change of pysignalr lib to get rid of this problem. It will require a change to pyeasee too since the SSL context must come from HA, but that is of course less problematic since that is our code.
PR created for pysignalr, lets see if that will be accepted. https://github.com/baking-bad/pysignalr/pull/19
The problem
Please see here: https://github.com/home-assistant/core/issues/125949
Version of Easee integration having the issue?
0.9.59
Version of Home Assistant Core having the issue?
2024.09.1
Anything in the logs that might be useful for us?
Additional information
No response