-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blocking Call to load_default_certs at Startup #1047
Comments
Thank you for locating the earlier report of this issue. It indicates it was resolved and the fix was merged to the main repository? Is it not in the current main release (3.24.1)? |
I've confirmed I'm running 3.24.1 but seeing the same error.
|
It appears this issue (zabuldon/teslajsonpy#474 ) has been worked and accepted(?) into the main code base. What is the process and possible timeline for an official point release containing this? TIA -Dean |
Someone submits a PR to add it. |
I have the same issue. Running HA version: 2024.10.2 It does not solve the problem as now ssl_context has no value? I hope my output helps in solving this problem. homeassistant | File "/config/custom_components/tesla_custom/config_flow.py", line 96, in async_step_credentials |
Same here: WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_default_certs with args (<ssl.SSLContext object at 0x7f50b76a50>, <Purpose.SERVER_AUTH: _ASN1Object(nid=129, shortname='serverAuth', longname='TLS Web Server Authentication', oid='1.3.6.1.5.5.7.3.1')>) inside the event loop by custom integration 'tesla_custom' at custom_components/tesla_custom/init.py, line 174: controller = TeslaAPI( (offender: /usr/local/lib/python3.12/ssl.py, line 713: context.load_default_certs(purpose)), please create a bug report at https://github.com/alandtse/tesla/issues |
Is there an existing issue for this?
I have read about the Fleet API and understand I may need to use it
Version of the Tesla component
v3.24.1
Version of the Tesla car software
2024.32.3
Model
Model Y
Current Behavior
During startup of Home Assistant, I get a traceback in the logs, generated by the Tesla integration component. I am encountering periodic crashes of my entire HA instance and this is something that has shown up in my diagnosis of that larger problem. I am not asserting that the Tesla component is the cause of my crashes. I have not concluded that analysis yet.
Expected Behavior
Tracebacks are not expected to happen in normal operations.
Debug logs
Anything else?
No response
The text was updated successfully, but these errors were encountered: